$100 $200 $300 $400 $500 $100 $200 $300 $400 $500 $100 $200 $300 $400 $500 $100 $200 $300 $400 $500 $100 $200 $300 $400 $500 $100 $200 $300 $400 $500

1-100 This is a simplification of reality that completely describes a system from a particular perspective.

1-100A

1-200 This encompasses the set of significant decisions about the structure and behavior of a system.

1-200A

1-300 This best practice helps cope with multiple developers working on multiple iterations and releases in parallel.

1-300A

1-400 This best practice involves creating tests for each of a system’s key desired behaviors.

1-400A

1-500 This best practice involves eliciting, organizing, and documenting the system’s required functionality.

1-500A

These are what the iterative approach identifies early in the lifecycle, when it’s possible to attack and react to them in an efficient manner.

2-100A

2-200 Each one of these results in a software generation.

2-200A

2-300 Each one of these is a mini- waterfall.

2-300A

2-400 This process creates an initial version of a software product.

2-400A

2-500 This process evolves a software product into its next generation.

2-500A

This element of the RUP model is also known as role.

3-100A

3-200 These may decompose into steps.

3-200A

3-300 These are tangible products the project uses or produces on its way toward the final product.

3-300A

3-400 These represent a partitioning of workers and activities into logical groupings.

3-400A

3-500 These show how to use a specific tool to perform a step.

3-500A

This guru is famous for his description of the spiral model.

4-100A

4-200 He is one of Rational’s “3 amigos” and wrote Chapter 1 of Kruchten’s book.

4-200A

4-300 He wrote the seminal paper on waterfall life cycle models in 1970.

4-300A

4-400 This member of Rational’s 3 amigos introduced use cases in his 1992 book Object-Oriented Software Engineering.

4-400A

4-500 This guru said, “If you do not actively attack the risks in your project, they will actively attack you.”

4-500A

This phase concludes with the lifecycle architecture milestone.

5-100A

5-200 This phase includes manufacturing, delivering, training, and maintaining the product.

5-200A

5-300 This phase creates a project plan, which shows the phases and iterations.

5-300A

5-400 This phase consumes 50% of the schedule and 65% of the effort on a typical project.

5-400A

5-500 This is the phase where most of your risks should be mitigated.

5-500A

The elaboration phase results in this model being 80% complete.

6-100A

6-200 This artifact includes an estimate of ROI for the project.

6-200A

6-300 RUP discourages the use of these types of artifacts.

6-300A

6-400 Source code and executables are considered part of this RUP information set.

6-400A

6-500 This artifact includes the development case, which is the process used for the project.

6-500A

This is the main driver to determine the scope and objectives of an iteration.

Daily Double Round 1