Iterative Model Used In Software Development

Introduction

Software Process Model Articles Series,

1. What is Software Development Life Cycle
2. Waterfall Model Used In Software Development

The iterative model starts the process with a simple implementation of a small set of requirements and iteratively enhances the evolving versions of the system that is complete and ready to be deployed. The iterative model does not attempt to start the development after the complete specification of the system; instead, development starts with just part of the software product.

Iterative Model Design

The iterative process starts with a small representation of the software product. In this model, we start working on a project with a small chunk of requirements. In this model, we repeat certain steps like design and development testing and implementation in each iteration. Iterative enhance the evolving versions of the system is complete and ready to be deployed.

The following picture illustrates the Iterative Model.

Applications

The iterative model is widely and extensively used in the software industry. Some given below point explains the usage of the iterative model.

• • The requirement of the complete system is clearly defined.
  • Major requirements must be defined; however, some requirements and functional may need modification and upgrade with time.
  • There are some high-level risks, features, and goals involved that may be changed in the future.

Advantages of the Iterative Model

• Some working functionality can be developed quickly at the early stages of the Iterative project.
• Clearly defined stages
• Easy to arrange tasks
• Progress can be measured
• Results are obtained at the early stages
• Easy to manage due to the rigidity of the model
• Less costly to change the requirements at any stage
• Easier to manage high risks
• Parallel development can be planed

Disadvantages of the Iterative Model

• More resources may be required
• More Management attention is required
• The cost of change is less, but it is not suitable for changing requirements repeatedly.
• Not suitable for smaller projects
• Management Complexity is more
• A highly skilled resource is required
• Project progress is highly dependent on the risk analysis phase.