Incremental build model

<p>The incremental build model is a method of <a href="/facts/Software_development/UUfsAaYY">software development</a> where the product is <a href="/facts/Software_design/61rGr5Ej">designed</a>, implemented, and <a href="/facts/Software_testing/VoXzG9Tb">tested</a> 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 <a href="/facts/Waterfall_model/uQGzoBKH">waterfall model</a> with the iterative philosophy of <a href="/facts/Software_prototyping/cLqGURoM">prototyping</a>.
According to the <a href="/facts/Project_Management_Institute/8AygTItl">Project Management Institute</a>, an incremental approach is an "adaptive development approach in which the deliverable is produced successively, adding
functionality until the deliverable contains the necessary and
sufficient capability to be considered complete.": Section 3. Definitions 
</p><p>The product is decomposed into several components, each of which is designed and built separately (termed as builds).: Section 3.5 
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 periods. This model of development also helps ease the traumatic effect of introducing a completely new system all at once.
</p>

Incremental build model open-in-new

Incremental build model