Iterative Model

An iterative lifecycle model does not attempt to start with a full specification of requirements. Instead, development begins by specifying and implementing just part of the software, which can then be reviewed in order to identify further requirements. This process is then repeated, producing a new version of the software for each cycle of the model. Consider an iterative lifecycle model which consists of repeating the following four phases in sequence:

A Requirements phase, in which the requirements for the software are gathered and analyzed. Iteration should eventually result in a requirements phase that produces a complete and final specification of requirements. - A Design phase, in which a software solution to meet the requirements is designed. This may be a new design, or an extension of an earlier An Implementation design.

and

Test phase,

when

the

software

is

coded,

integrated

and

tested.

- A Review phase, in which the software is evaluated, the current requirements are reviewed, and changes and additions to requirements proposed.

For each cycle of the model, a decision has to be made as to whether the software produced by the cycle will be discarded, or kept as a starting point for the next cycle (sometimes referred to as incremental prototyping). Eventually a point will be reached where the requirements are complete and the software can be delivered, or it becomes impossible to enhance the software as required, and a fresh start has to be made.

The iterative lifecycle model can be likened to producing software by successiveapproximation. Drawing an analogy with mathematical methods that use successiveapproximation to arrive at a final solution, the benefit of such methods depends on how rapidly they converge on a solution. The key to successful use of an iterative software development lifecycle is rigorousvalidation of requirements, and verification (including testing) of each version of the software against those requirements within each cycle of the model. The first three phases of the example iterative model is in fact an abbreviated form of a sequential V or waterfall lifecycle

model. Each cycle of the model produces software that requires testing at the unit level, for software integration, for system integration and for acceptance. As the software evolves through successive cycles, tests have to be repeated and extended to verify each version of the software.

Shorter cycle time System delivered in pieces enables customers to have some functionality while the rest is being developed the production system (release n): currently being used the development system (release n+1): the next version Allows two systems functioning in parallel

Incremental development: starts with small functional subsystem and adds functionality with each new release Iterative development: starts with full system, then changes functionality of each subsystem with each new release

 Phased development is desirable for several reasons Training can begin early, even though some functions are missing Markets can be created early for functionality that has never before been offered Frequent releases allow developers to fix unanticipated problems globaly and quickly The development team can focus on different areas of expertise with different releases

Key idea: on each iteration identify and solve the sub-problems with the highest risk. These sound similar, and sometimes are equated. Subtle difference: Incremental: add to the product at each phase Iterative: re-do the product at each phase

 Some of the models could be used either way Example: Building a House l Incremental: Start with a modest house, keep adding rooms and upgrades to it. l Iterative: On each iteration, the house is re-designed and built anew. l Big Difference: One can live in the incremental house the entire time! One has to move to a new iterative house.