Essentials of Systems Analysis and Design, 6e (Valacich)
Appendix B Agile Methodologies
1) The developer-as-artist systems development era was marked by a lack of documentation and
development tools and by a high degree of dependence on the developer for the continued
ongoing operation of the system he/she had created.
Classification: Concept
2) During the developer–as-artist systems development era, principles from engineering were
frequently applied to the systems development process.
Classification: Concept
3) During the developer–as-engineer systems development era, documentation, rigorous testing,
structured tools and techniques, and computer–based tools became standard parts of analysis and
design.
Classification: Concept
4) The convergence of the object-oriented approach and the Internet economy set the stage for
the Agile Methodologies.
Classification: Concept
1
5) Scrum is an Agile Methodology.
Classification: Concept
6) eXtreme Programming is a traditional methodology.
Classification: Concept
7) Agile Methodologies are more predictive than the more traditional approaches to systems
development.
Classification: Concept
8) Agile Methodologies are more planning-based than the traditional approaches to systems
development.
Classification: Concept
9) The three key principles of Agile Methodologies include a focus on adaptive rather than
predictive methodologies, a focus on people rather than roles, and a focus on a self-adaptive
process.
Classification: Concept
10) Agile software development values individuals and interactions over processes and tools.
Classification: Concept
2
11) Agile software development values working software over documentation.
Classification: Concept
12) Agile software development values contract negotiations over customer collaboration.
Classification: Concept
13) Agile software development values responding to change over following a plan.
Classification: Concept
14) According to the Agile Software Development Manifesto, customer satisfaction is the
primary measure of progress.
Classification: Concept
15) According to the Agile Software Development Manifesto, the seventeen anarchists agreed
that their highest priority is to satisfy the customer through early and continuous delivery of
valuable software.
Classification: Concept
16) According to the Agile Software Development Manifesto, the seventeen anarchists agreed to
deliver working software only after it had been thoroughly tested, even if it means waiting for
several months to deliver the software.
Classification: Concept
3
17) According to the Agile Software Development Manifesto, the seventeen anarchists agreed
that business people and developers should work together daily throughout the project.
Classification: Concept
18) According to the Agile Software Development Manifesto, the seventeen anarchists agreed
that projects should be built around motivated individuals.
Classification: Concept
19) According to the Agile Software Development Manifesto, the most efficient and effective
method of conveying information to and within a development team is face-to-face conversation.
Classification: Concept
20) According to the Agile Software Development Manifesto, the best architectures,
requirements, and designs emerge from self-organizing teams.
Classification: Concept
21) According to the Agile Software Development Manifesto, simplicity is the art of maximizing
the amount of work not done.
Classification: Concept
4
22) According to the Agile Software Development Manifesto, working software is the primary
measure of progress.
Classification: Concept
23) According to the Agile Software Development Manifesto, continuous attention to technical
excellence and good design enhances agility.
Classification: Concept
24) Structured analysis focuses on the frequent production of working versions of a system that
have a subset of the total number of required features.
Classification: Concept
25) Agile Methodologies focus on the roles that people perform.
Classification: Concept
26) Agile Methodologies are recommended if you have responsible and motivated developers.
Classification: Concept
27) If you have a fixed-price or fixed-scope contract, an agile methodology is often
recommended.
Classification: Concept
5
28) In general, Agile Methodologies view people as interchangeable units.
Classification: Concept
29) Agile Methodologies promote a self-adaptive software development process.
Classification: Concept
30) An Agile Methodology is recommended if your project involves unpredictable or dynamic
requirements.
Classification: Concept
31) An Agile Methodology is recommended if your project has a development team of 100 or
more people.
Classification: Concept
32) Traditional approaches work best when the target system will operate in a volatile and fluid
environment.
Classification: Concept
33) Agile approaches work best when the system being developed operates in a stable
environment.
Classification: Concept
6
34) eXtreme Programming is distinguished by its long development cycles and predictive
planning approach.
Classification: Concept
35) eXtreme Programming uses two-person programming teams and has a customer on-site
during the development process.
Classification: Concept
36) During eXtreme Programming, all phases of the life cycle converge together into a series of
activities based on the basic processes of coding, testing, listening, and designing.
Classification: Concept
37) At the end of eXtreme Programming’s coding phase, all code written to that point is tested.
Classification: Concept
38) When using the eXtreme Programming approach, code is tested very soon after it is written.
Classification: Concept
39) The overall philosophy behind eXtreme Programming is that code will be integrated into the
system it is being developed for and tested within a few hours after it has been written.
Classification: Concept
7
40) eXtreme Programming advantages include more communication among developers, higher
levels of productivity, higher-quality code, and reinforcement of the other eXtreme Programming
practices.
Classification: Concept
41) Limited user participation is a major criticism of the Agile Methodologies.
Classification: Concept
42) The extensive involvement of users in the analysis and design process is a key part of many
Agile Methodologies.
Classification: Concept
43) The two most effective aspects of the Agile Usage-Centered Design are the coding and the
design rework sessions.
Classification: Concept
44) During eXtreme Programming, the nominal group technique is the primary method used for
requirements determination.
Classification: Concept
45) During eXtreme Programming, programmers are the only participants in the Planning Game.
Classification: Concept
8
46) eXtreme Programming uses simple design and refactoring to continually improve the quality
of the design as developers continue to iterate through the analysis-design-code-test cycle.
Classification: Concept
47) Module refinement is the process of making a program simpler after adding a new feature.
Classification: Concept
48) Simple design refers to the creation of uncomplicated software and software components that
work to solve the current problem rather than creating complicated software designed for a future
that may not come.
Classification: Concept
49) With Agile Methodologies, code is tested soon after it is written.
Classification: Concept
50) Which of the following is the systems development era that spawned the structured analysis
and structured design approaches to systems development?
A) Developer-as-artist
B) Developer–as-integrator
C) Facilitator–as-developer
D) User-as-developer
E) Developer-as-engineer
Classification: Concept
9
51) Which of the following is the systems development era marked by a lack of documentation
and development tools and by a high degree of dependence on the developer for the continued
ongoing operation of the system he/she had created?
A) Developer-as-artist
B) Developer–as-integrator
C) Facilitator–as-developer
D) User-as-developer
E) Developer-as-engineer
Classification: Concept
52) Which of the following is a true statement?
A) The developer–as-scam-artists systems development era was marked by a lack of
documentation and development tools and by a high degree of dependence on the developer for
the continued ongoing operation of the system he or she had created.
B) During the developer–as-artists systems development era, principles from engineering were
applied to development.
C) The Agile Methodologies era favors close cooperation between developers and clients.
D) Agile Development formally started in 1972.
E) Agile Development formally started in 1970.
Classification: Concept
53) Which of the following set the current major phase in systems development?
A) The object-oriented approach and the Internet economy
B) The process-oriented approach
C) The planning-based approach
D) The software engineering approach
E) The prototyping approach
Classification: Concept
10