Incremental Model

 Topic Outline

• Incremental Model
• When we use incremental model
• Phases
• Requirements
• Design
• Coding
• Testing
• Implementation
• Advantages/ Disadvantages

Incremental Model

It is a software development life cycle model. In the incremental model, requirements are divided into different modules and submodules of the software. So each module and submodule goes through the requirements, design, coding, testing, and implementation phases. Every module adds a function to the previous release module and this process continues till the final system is achieved. This model is implemented and tested till the project is finished.

When we use incremental model

• When the requirements of the system are clearly defined.
• This model is used when new technology is used
• When the development team is not very well trained.

Phases of Incremental Model

 

Requirements

This phase is very important in system development. In this phase, the project developer arranges a meeting with their client to get requirements and he knows the expectations of the client. After getting the requirements, the project analyst converts the requirements into technical requirements. To develop the system through the incremental model, the requirement phase performs an important role.

Design

In this phase, gathered requirements are converted into the design. Development takes the requirements and creates a rough design of a system. The purpose of creating the design is to specify how the system works and what the design looks like.

Coding

In this phase, the developer starts the coding by following organization standard codes. When coding is complete, the programmer uses the programming tool to identify whether the code is working or not.

Testing

In this phase, the code gets to identify whether the system working is acceptable or not. The developer performs the unit testing and integration testing in this phase. The testing team performs different testing such as system testing, approval testing, etc.

Implementation

When the system is tested and it has no error then the test result may go for review by the client.

Advantages

• This model is very flexible.
• This model is easier to test and debug.
• We can manage risk easily.
• It reduces delivery costs.

Disadvantages

• In this model we need good planning and design.
• In this model, the total cost is higher than the waterfall model.
• We need a complete understanding of the system.
• Modules and submodules should be defined clearly.