Different SDLC models Commonly used of IS Project Management ~ [ Iterative Model ]

Different SDLC models Commonly used of IS Project Management

 

    Iterative Model

The iterative model is a particular implementation of a software development life cycle (SDLC) that focuses on an initial, simplified implementation, which then progressively gains more complexity and a broader feature set until the final system is complete.

 A subset of the final product under development, which grows from iteration to iteration to become the final product or software.

In the iterative model there are total four process. They are describe below:-

1)      Requirement: - In this iterative model first start with requirement process. Iterative process starts with a simple implementation of a subset of the software requirements and iteratively enhances the evolving versions until the full system is implemented.

2)      Design & Development: - At each iteration, design modifications are made and new functional capabilities are added. The basic idea behind this method is to develop a system through repeated cycles (iterative) and in smaller portions at a time (incremental).

3)      Testing: - It is an important steps/process where the project are evaluating by following rules. That means testing the project and if there is need any changes than it is implemented and ensure the quality of project/product.

4)      Implementation: - It is the final steps and here the final project or product is found. When all the requirement is fulfilled then the product need to be implementation. So it is from iteration to iteration to become the final product or software.

 

The advantages of the Iterative Model: −

·        Some working functionality can be developed quickly and early in the life cycle.

·        Results are obtained early and periodically.

·        Parallel development can be planned.

·        Progress can be measured.

·        Less costly to change the scope/requirements.

·        Testing and debugging during smaller iteration is easy.

·    Risks are identified and resolved during iteration; and each iteration is an easily managed milestone.

·        Risk analysis is better.

·        Better suited for large and mission-critical projects.

·    During the life cycle, software is produced early which facilitates customer evaluation and feedback.

 

The disadvantages of the Iterative Model are: −

·        More resources may be required.

·        System architecture or design issues may arise because not all requirements are gathered in the beginning of the entire life cycle.

·        Defining increments may require definition of the complete system.

·        Not suitable for smaller projects.

·        Management complexity is more.

·        End of project may not be known which is a risk.

·        Highly skilled resources are required for risk analysis.

·        Projects progress is highly dependent upon the risk analysis phase.

 

When to use the Iterative Model:-

ü      Requirements of the complete system are clearly defined and understood.

ü      When the project is big.

ü      Major requirements must be defined; however, some details can evolve with time.

ü      When there is a requirement of changes in future.