Iterative model does not start with a full specification of requirements. Instead development begins by specifying and implementing just part of the software,which can be reviewed in order to meet the requirements. This process is repeated,which results in producing new version of the software for each cycle of the model. We have the following phases in Iterative Model.
Requirements: During this phase, the requirements of the software to be developed is gathered and analyzed.Iteration eventually result in this phase produce a complete and final requirement specifications.
Design: During this phase the architecture of the software to be developed is designed in order to reflect the the document produced during the requirement phase based on the iteration.
Implementation & Test: During this phase the software is coded, integrated and tested thoroughly.
Review phase: During this phase, the developed software is validated against the revised requirement specifications.
The key to successful use of an iterative software development life cycle is rigorous validation 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 life cycle 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.
Requirements: During this phase, the requirements of the software to be developed is gathered and analyzed.Iteration eventually result in this phase produce a complete and final requirement specifications.
Design: During this phase the architecture of the software to be developed is designed in order to reflect the the document produced during the requirement phase based on the iteration.
Implementation & Test: During this phase the software is coded, integrated and tested thoroughly.
Review phase: During this phase, the developed software is validated against the revised requirement specifications.
The key to successful use of an iterative software development life cycle is rigorous validation 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 life cycle 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.
0 comments:
Post a Comment