Incremental build model

Software development process
Core activities
Paradigms and models
Methodologies and frameworks
Supporting disciplines
Standards and BOKs

The incremental build model is a method of software development where the product 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. This model combines the elements of the waterfall model with the iterative philosophy of prototyping.

The product is decomposed into a number of components, each of which is designed and built separately (termed as builds). Each component is delivered to the client when it is complete. This allows partial utilization of the product and avoids a long development time. It also avoids a large initial capital outlay and subsequent long waiting period. This model of development also helps ease the traumatic effect of introducing a completely new system all at once. There are, however, several problems with this model.

Incremental model

The incremental model applies the waterfall model incrementally.[1]

The series of releases is referred to as “increments”, with each increment providing more functionality to the customers. After the first increment, a core product is delivered, which can already be used by the customer. Based on customer feedback, a plan is developed for the next increments, and modifications are made accordingly. This process continues, with increments being delivered until the complete product is delivered. The incremental philosophy is also used in the agile process model (see agile modeling).[1]

The Incremental model can be applied to DevOps. In DevOps it centers around the idea of minimizing risk and cost of a DevOps adoption whilst building the necessary in-house skillset and momentum.[2]


  1. After each iteration, regression testing should be conducted. During this testing, faulty elements of the software can be quickly identified because few changes are made within any single iteration.
  2. It is generally easier to test and debug than other methods of software development because relatively smaller changes are made during each iteration. This allows for more targeted and rigorous testing of each element within the overall product.
  3. Customer can respond to features and review the product for any needed or useful changes.
  4. Initial product delivery is faster and costs less.


  1. Resulting cost may exceed the cost of the organization.
  2. As additional functionality is added to the product, problems may arise related to system architecture which were not evident in earlier prototypes.

Tasks involved

Tasks In Incremental Model

These tasks are common to all the models[1]

  1. Communication: helps to understand the objective.
  2. Planning: required as many people (software teams) work on the same project but different function at same time.
  3. Modeling: involves business modeling, data modeling, and process modeling.
  4. Construction: this involves the reuse software components and automatic code.
  5. Deployment: integration of all the increments.


  1. 1 2 3 Pressman, Roger (2010). Software Engineering: A Practitioner's Approach. Boston: McGraw Hill. pp. 41–42. ISBN 9780073375977.
  2. Kim, Gene (22 January 2013). "DevOps distilled, Part 1: The three underlying principles" (PDF). IBM DeveloperWorks.
  3. Incremental- lifecycle.asp
  4. What is Incremental model - advantages, disadvantages and when to use it
  5. Methodology:: Development Methods

See also

Methodology::Development Models
Incremental lifecycle What is Incremental model - advantages, disadvantages and when to use it Incremental Model in Software Engineering

This article is issued from Wikipedia - version of the 11/6/2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.