ISDS 406 QUESTIONS AND ANSWERS 100%
VERIFIED
Definition of System Development Life Cycle (SDLC) - Correct Answer-SDLC is the process of
determining how an information system (IS) can support business needs, designing the
systems, building it and delivering it to the users.
Systems Analyst - Correct Answer-Who analyzes the business situation, identifies the
opportunities for improvements, and designs an information systems to implements the
improvements.
Systems Analyst will work as a team with s variety of people including business and technical
experts.
Systems Analyst Skills - Correct Answer-Technical (understand the organization's existing
technical environment, the new system's technology foundation, and the way in which both can
be fit into an integrated technical solution), Business (understand how IT can be applied to
business situations and to ensure that the IT delivers real business value), Analytical,
Interpersonal (need to communicate effectively, one-on-one with users and business managers
and with programmers, management and ethical.
Waterfall Development - Correct Answer-Strengths:
*** System requirements identified long before construction begins.
*** Requirements are "frozen" as project proceeds - no moving targets allowed.
Weaknesses:
*** Must wait a long time before there is "visible" evidence of the new system.
*** Takes a long time from start to finish.
Parallel Methodology Assessment - Correct Answer-Strengths:
*** Reduces overall project time (compared to Waterfall).
*** Reduces the need for rework; with shorter time frame, less chance of requirements
changing.
Weaknesses:
*** Creating subprojects requires careful design decisions.
*** Integrating subprojects at the end can be complex and difficult.
, V-model - Correct Answer-Strengths:
*** Simple and straightforward.
*** Quality improves through the emphasis on testing.
*** Including Quality Assurance expertise early in the project strengthens system quality.
Weaknesses:
*** Rigid.
*** Difficult to use in a dynamic business environment.
RAD Approach: Iterative Development (A series of versions developed sequentially) - Correct
Answer-Strengths:
*** Users get a system to use quickly.
*** Users identify additional needs for later versions based on real experiences with current
version.
Weaknesses:
*** Users faced with using an incomplete system for a time.
*** Users must be patient and wait for fully-functional system.
RAD Approach: System Prototyping (Create prototype (model) of system and "grow" it into the
final system). - Correct Answer-Strengths:
*** Users get to work with prototype very quickly.
*** Feedback cycles let users identify changes and refine real requirements.
Weaknesses:
*** Superficial analysis may cause problems.
Initial design decisions may be poor.
Overlooked features may be hard to add later.
RAD Approach: Throw-away Prototyping (Prototype alternative designs in an experimental
way, build system following prototype design bu discard the actual prototype). - Correct
Answer-Strengths:
*** Uncertainty is minimized.
Important issues are understood before building the final system.
Weaknesses:
*** May take longer (compared to system prototyping).
Agile Development (Several iterations of full "mini-SDLCs" over a period of time. Developed to
overcome limitations of traditional and even RAD methodologies formal modeling and
documentation are eliminated in favor of face-to-face communication). - Correct Answer-
Strengths:
*** Fast delivery of results.
VERIFIED
Definition of System Development Life Cycle (SDLC) - Correct Answer-SDLC is the process of
determining how an information system (IS) can support business needs, designing the
systems, building it and delivering it to the users.
Systems Analyst - Correct Answer-Who analyzes the business situation, identifies the
opportunities for improvements, and designs an information systems to implements the
improvements.
Systems Analyst will work as a team with s variety of people including business and technical
experts.
Systems Analyst Skills - Correct Answer-Technical (understand the organization's existing
technical environment, the new system's technology foundation, and the way in which both can
be fit into an integrated technical solution), Business (understand how IT can be applied to
business situations and to ensure that the IT delivers real business value), Analytical,
Interpersonal (need to communicate effectively, one-on-one with users and business managers
and with programmers, management and ethical.
Waterfall Development - Correct Answer-Strengths:
*** System requirements identified long before construction begins.
*** Requirements are "frozen" as project proceeds - no moving targets allowed.
Weaknesses:
*** Must wait a long time before there is "visible" evidence of the new system.
*** Takes a long time from start to finish.
Parallel Methodology Assessment - Correct Answer-Strengths:
*** Reduces overall project time (compared to Waterfall).
*** Reduces the need for rework; with shorter time frame, less chance of requirements
changing.
Weaknesses:
*** Creating subprojects requires careful design decisions.
*** Integrating subprojects at the end can be complex and difficult.
, V-model - Correct Answer-Strengths:
*** Simple and straightforward.
*** Quality improves through the emphasis on testing.
*** Including Quality Assurance expertise early in the project strengthens system quality.
Weaknesses:
*** Rigid.
*** Difficult to use in a dynamic business environment.
RAD Approach: Iterative Development (A series of versions developed sequentially) - Correct
Answer-Strengths:
*** Users get a system to use quickly.
*** Users identify additional needs for later versions based on real experiences with current
version.
Weaknesses:
*** Users faced with using an incomplete system for a time.
*** Users must be patient and wait for fully-functional system.
RAD Approach: System Prototyping (Create prototype (model) of system and "grow" it into the
final system). - Correct Answer-Strengths:
*** Users get to work with prototype very quickly.
*** Feedback cycles let users identify changes and refine real requirements.
Weaknesses:
*** Superficial analysis may cause problems.
Initial design decisions may be poor.
Overlooked features may be hard to add later.
RAD Approach: Throw-away Prototyping (Prototype alternative designs in an experimental
way, build system following prototype design bu discard the actual prototype). - Correct
Answer-Strengths:
*** Uncertainty is minimized.
Important issues are understood before building the final system.
Weaknesses:
*** May take longer (compared to system prototyping).
Agile Development (Several iterations of full "mini-SDLCs" over a period of time. Developed to
overcome limitations of traditional and even RAD methodologies formal modeling and
documentation are eliminated in favor of face-to-face communication). - Correct Answer-
Strengths:
*** Fast delivery of results.
