A. Capability Patterns
B. Content Packages
C. Delivery Processes
D. Custom Category
A. More precise planning
B. Better product quality
C. Better lifecycle efficiency
D. More accurate early estimates
A. The level of automation used to manage code, distribute information and perform testing
B. The priority set by the customer on particular features
C. The size of the project
D. The requirement for a minimum of six iterations in a project
A. Demonstrate value iteratively
B. Collaborate across teams
C. Focus continuously on quality
D. Adapt the artifacts
A. Team Application
B. Description
C. Work-Breakdown-Structure
D. Work Product Usage
A. Implementing independent quality tests of the system or subsystem
B. Defining the organization of the code in terms of implementation subsystems
C. Implementing classes and objects
D. Testing implementation elements
E. Integration the results produced by individual implementers (or teams) into an executable system
A. Use component architectures
B. Develop iteratively
C. Freeze requirements at project inception
D. Maximize reuse
E. Manage change
A. Iterative development exposes flaws and enables resolution earlier in the lifecycle
B. With iterative development, customer satisfaction is maintained by early, incremental deliveries of capability
C. In iterative development, the software architecture can be revised in any iteration to support new features and overcome performance problems
D. Iterative development allows key, non-functional requirements (i.e performance, fault tolerance and maintainability) to be addressed early in development
A. Rectangle containing the object's name
B. Oval
C. Arrow
D. Stick figure
E. Rectangle with three compartments
A. Inception 5%, Elaboration 20%, Construction 65% Transition 10%
B. Inception 5% , Elaboration 20%, Construction 45%, Transition 30%
C. Inception 20% Elaboration 50% Construction 20% Transition 10%
D. Inception 10%, Elaboration 10% Construction 70%, Transition 10%
