The document discusses software development processes and how iterative development compares to waterfall development. It notes that iterative development involves planning iterations, capturing requirements, analysis and design, implementation, testing, and preparing releases for each iteration. This allows developers to mitigate risks at each stage and produce working software more frequently than waterfall development, where risks aren't addressed until late in the process.

1. Software Development process : A walk through Inception Elaboration Construction Transition Iteration 1 Iteration 2 Iteration 3 Iteration Planning Rqmts Capture Analysis & Design Implementation Test Prepare Release “ Mini-Waterfall” Process

2. Develop Iteratively Each iteration results in an executable release.

3. Developing Iteratively

6. All projects have a set of risks involved: An initial design will likely be flawed with respect to its key requirements. Late discovery of design defects results in costly over-runs and in some cases even project cancellation. You will never be able to predict all risks regardless of how experienced the development team is

7. Risk Profile of an Iterative Development & water fall method: Risk Preliminary Iteration Architect. Iteration Architect. Iteration Devel. Iteration Devel. Iteration Devel. Iteration Transition Iteration Transition Iteration Post- deployment Time In a waterfall lifecycle, you cannot verify whether you have stayed clear of a risk until late in the lifecycle. In an iterative lifecycle, you will select what increment to develop in an iteration based on a list of key risks. Since the iteration produces a tested executable, you will be able to verify whether you have mitigated the targeted risks or not. Transition Inception Elaboration Construction Waterfall