Unlock document.
This document is partially blurred.
Unlock all pages and 1 million more documents.
Get Access
54) The key principles of the Agile Methodologies does not include:
A) a focus on adaptive rather than predictive methodologies.
B) a focus on people rather than roles.
C) a self-adaptive process.
D) a focus on talented people
E) a focus on documentation
Classification: Concept
55) Principles identified in the Agile Manifesto include:
A) having as its highest priority customer satisfaction through the early and continuous delivery
of valuable software.
B) only testing late in development.
C) a one-time delivery of working software.
D) having customer satisfaction as its lowest priority.
E) avoiding changing requirements, even late in development.
Classification: Concept
56) According to the Agile Software Development Manifesto, the seventeen anarchists came to
value:
A) roles over individuals.
B) comprehensive documentation.
C) contract negotiation.
D) following a plan.
E) individuals and interactions over processes and tools.
Classification: Concept
11
57) The Agile Software Development anarchists value:
A) contract negotiation over customer collaboration.
B) processes and tools over individuals and interactions.
C) following a plan over responding to change.
D) working software over comprehensive documentation.
E) joint application development over rapid application design.
Classification: Concept
58) Which of the following would the Agile Software Development anarchists place more value
on?
A) Individuals and interactions
B) Contract negotiations
C) Following a plan
D) Comprehensive documentation
E) Team member roles
Classification: Concept
59) An Agile process is not recommended when your project involves:
A) unpredictable requirements.
B) responsible and motivated developers.
C) customers who understand the process and will get involved.
D) customers who refuse to get involved.
E) dynamic requirements.
Classification: Concept
12
60) An Agile Methodology is recommended for each of the following EXCEPT:
A) unpredictable or dynamic requirements.
B) responsible and motivated developers.
C) customers who understand and will get involved.
D) a large development team, exceeding 100 or more people.
E) small development projects.
Classification: Concept
61) Traditional methods for software development are preferred for each of the following
EXCEPT:
A) when the project is operating under a fixed-price or fixed-scope contract.
B) unpredictable or dynamic requirements.
C) a large development team, exceeding 100 or more people.
D) projects dealing with safety-critical systems.
E) the system being developed will operate in a stable environment.
Classification: Concept
62) When dealing with a lack of predictability, Agile Methodologies employ:
A) use-case modeling.
B) structured analysis.
C) iterative development.
D) structured programming.
E) logic modeling.
Classification: Concept
13
63) Which of the following focuses on the frequent production of working versions of a system
that have a subset of the total number of required features?
A) Use-case modeling
B) Structured analysis
C) Iterative development
D) Structured programming
E) Limited production
Classification: Concept
64) Which of the following is a critical factor for distinguishing agile and traditional approaches
to systems development?
A) State
B) Criticality
C) Static
D) CRM
E) ERD
Classification: Concept
65) Which of the following describes Agile Methodologies?
A) Methods evolved to handle highly critical products.
B) Methods evolved to handle large products and teams.
C) Needs a critical mass of scarce experts during project definition but can work with fewer later
in the project, unless the environment is highly dynamic.
D) Thrives in a culture where people feel comfortable and empowered by having their roles
defined by clear practices and procedures.
E) Simple design and continuous refactoring are excellent for highly dynamic environments but
are a source of potentially expensive rework for highly stable environments.
Classification: Concept
14
66) Each of the following describes engineering-based methods EXCEPT:
A) methods evolved to handle highly critical products.
B) methods evolved to handle large products and teams.
C) needs a critical mass of scarce experts during project definition but can work with fewer later
in the project, unless the environment is highly dynamic.
D) thrives in a culture where people feel comfortable and empowered by having their roles
defined by clear practices and procedures.
E) simple design and continuous refactoring are excellent for highly dynamic environments but
are a source of potentially expensive rework for highly stable environments.
Classification: Concept
67) Which of the following are descriptive of engineering-based methods?
A) Thrives in a culture where people feel comfortable and empowered by many degrees of
freedom
B) Potential difficulties with simple design and lack of documentation
C) Simple design and continuous refactoring are excellent for highly dynamic environments but
are a source of potentially expensive rework for highly stable environments
D) Needs a critical mass of scarce experts during project definition but can work with fewer later
in the project, unless the environment is highly dynamic
E) Well-matched to small products and teams
Classification: Concept
68) Each of the following are descriptive of Agile Methodologies EXCEPT:
A) detailed plans and Big Design Up Front are excellent for highly stable environments but are a
source of expensive rework for highly dynamic environments.
B) thrives in a culture where people feel comfortable and empowered by having many degrees of
freedom.
C) well-matched to small products and teams.
D) simple design and continuous refactoring are excellent for highly dynamic environments but
are a source of potentially expensive rework for highly stable environments.
E) requires a continuous presence of a critical mass of scarce experts.
Classification: Concept
15
69) Which of the following is distinguished by its short development cycles, its incremental
planning approach, its focus on automated tests written by programmers and customers to
monitor the process of development, and its reliance on an evolutionary approach to
development that lasts throughout the lifetime of the system?
A) JAD
B) OCP
C) DRM
D) eXtreme Programming
E) Nominal group technique
Classification: Concept
70) eXtreme Programming:
A) relies on predictive planning.
B) thrives on order.
C) is best used in the development of critical systems.
D) has as a key emphasis the use of two-person teams.
E) focuses on fixed contract systems.
Classification: Concept
71) eXtreme Programming:
A) is distinguished by its short development cycles.
B) focuses on automated tests written by programmers and customers to monitor the process of
development.
C) uses two-person programming teams.
D) has a customer on-site during the development process.
E) does all of the above.
Classification: Concept
16
72) Which of the following is a true statement about eXtreme Programming?
A) After a programmer has written the code, it is immediately given to a tester for testing.
B) Code is tested at the end of the coding phase.
C) Pair programming requires one person to type in the code and another person to watch as the
code is entered.
D) 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.
E) eXtreme is a traditional design approach.
Classification: Concept
73) Which of the following is NOT an eXtreme Programming advantage?
A) More communication among developers
B) Higher levels of productivity
C) Very useful for large development teams
D) Reinforcement of the other practices in eXtreme Programming
E) Higher-quality code
Classification: Concept
74) Which of the following is NOT an eXtreme Programming advantage?
A) More communication among developers
B) Higher levels of productivity
C) Higher-quality code
D) Reinforcement of the other practices in eXtreme Programming
E) Little testing required
Classification: Concept
17
75) During eXtreme Programming:
A) system requirements are produced during the systems analysis phase.
B) system specifications are created during the design phase.
C) coding and testing are done at the beginning of the implementation phase.
D) system requirements, system specifications, and coding and testing activities are combined
into a single analysis-design-code-test process.
E) none of the above are correct.
Classification: Concept
76) During eXtreme Programming, the techniques used for requirements determination are
captured in the:
A) Iteration Planning Game.
B) venting session.
C) walkthrough session.
D) Product Determination Game.
E) Planning Game.
Classification: Concept
77) Which of the following is a stylized approach to development used during eXtreme
Programming that seeks to maximize fruitful interaction between those who need a new system
and those who build it?
A) Iteration Planning Game
B) Venting session
C) Walkthrough session
D) Product Determination Game
E) Planning Game
Classification: Concept
18
