Process of Incremental Model

The incremental build model is a method of software development where the model is designed, implemented and tested incrementally (a little more is added each time) until the product is finished. It involves both development and maintenance. The product is defined as finished when it satisfies all of its requirements. The diagram below shows typical incremental models processes/ tasks. 

Incremental model (testingexcellence, 2015)

 

During the design phase of the first increment, the functionality with topmost priority from the project activity list is selected and the design is prepared. In the implementation phase, the design is implemented and tested. In the testing phase, the functional capability of the partially developed product is analysed. The development process is repeated until all the functions of the project are implemented.

In this project the incremental model is used as the same way described in the above process. The development process mainly focuses on most important features with the highest priority and the developed feature is then tested and analysed. This process repeats until the whole implementation is completed. In this project the incremental model also includes feedbacks from the supervisor just as any incremental model includes feedbacks from the product’s customer. This way any misunderstandings or any issues could be overcome.

Advantages of Selecting Incremental Model as Development Methodology 

The following are some of the reasons for the research to follow Incremental Model in his development methodology.

1. The time allocated for the development of the software is limited. The time constraint is considered as an aspect for selecting incremental model over other development methodologies.
2. It is generally easier to test and debug than other methods of software development because relatively smaller changes are made during every iteration. This allows for more targeted and rigorous testing of each element within the overall product.
3. Easier to manage risk because risky pieces are identified and handled during in iteration.
4. This model is more flexible and lower initial delivery cost
5. Generates working software rapidly and early during the product life cycle..
6. Work load is less.
7. Initial product delivery is faster.
8.  Risk of changing requirement is reduced