General

Iterative Waterfall Model

You can start with some software specifications and construct the initial version of the software using this Model. If the software needs to be changed after the first version, a new version of the software is developed with a new iteration. Every iteration of the Iterative Model is completed in a precise and definite time frame. 

The Iterative Model allows you to go back to prior phases and see how the changes were made. At the end of the Software Development Life Cycle (SDLC) procedure, the project’s final result was renewed.

The following are the phases of the Iterative Model 

1. Gathering and analysing requirements 

In this phase, requirements are acquired from customers and an analyst determines whether or not they will be met. The analyst determines whether or not the requirement will be met within budget. After that, the software team moves on to the next stage. 

2. Design 

During the design phase, the team uses several diagrams such as a Data Flow Diagram, an Activity Diagram, a Class Diagram, a State Transition Diagram, and so on to create the software.

3. Implementation 

During the implementation phase, requirements are defined in a coding language and converted into software programmes. 

4. Testing 

After the development step is completed, software testing begins utilising various test methods. There are other test techniques, but the white box, black box, and grey box test methods are the most frequent. 

5. Deployment 

After all of the processes have been completed, the software is deployed to its working environment.

6. Review

Following the deployment of the product, a review phase is conducted to assess the behaviour and validity of the generated product. If any errors are discovered, the process is restarted from the requirement gathering stage. 

7. Maintenance 

Following the deployment of software in the working environment, there may be some bugs, errors, or new upgrades that require maintenance. Debugging and new addition options are included in maintenance.

When should the Iterative Model be used? 

  • When requirements are defined in a clear and understandable manner. 
  • When there is a massive software programme. 
  • When there is a demand for future modifications.

The Iterative Model’s Advantage(s) 

  • It is simple to test and troubleshoot during lesser iterations. 
  • Parallel development is possible to plan. 
  • It is easily adaptable to the project’s ever-changing requirements. 
  • During iteration, risks are discovered and resolved. 
  • There was a lot of time spent on documentation and a lot of time spent on designing.

The Iterative Model’s Disadvantage(s) 

  • It isn’t appropriate for minor projects. 
  • It’s possible that more resources will be necessary. 
  • Because of unsatisfactory needs, the design can be altered multiple times. 
  • Changes in requirements might lead to budget overruns. 
  • Due to changing needs, the project’s completion date has yet to be determined.

Explanation of the Iterative Waterfall Life Cycle Model in Detail 

The iterative waterfall model is similar to the classical waterfall model, but there are feedback paths that make the model more realistic, as opposed to the classical model, which completes one phase before moving on to the next. We assume that a problem will be discovered during testing and that we will need to return to the design phase or possibly the requirement analysis phase to remedy the defect or series of defects in the lower phases.

It is critical to detect error propagation when developers make mistakes in order to reduce error propagation. The concept is that problems should be recognised and remedied within the most cost-effective phase. The longer it takes to uncover the flaw, the more expensive it will be.

If a design fault is discovered during the design process, it is just necessary to alter the design document; however, if it is discovered during the testing phase, not only must the design document be changed, but the code must also be rewritten, which is far more costly. As a result, this is referred to as the phase of error containment. It is a crucial notion that whenever a mistake or error happens, it must be contained in the same phase; this is known as phase containment of errors.

RECOMMENDED ARTICLES





Leave a Reply

Your email address will not be published.