Information System Development Life Cycle Models - High Level Models and Methodologies for Information Systems - page 24

Fig. 2.2 An example of the incremental life cycle model (adapted from Tilloo 2013 )

fraction at a time, in successive stages, so that with each stage (or increment), there
can be at least some feedback from the client. This feedback will provide valuable
assistance in the next increment of the process and so forth. With each ongoing
increment, the product is extensively tested and improved, according to objectives
and expectations from the client, which facilitates its eventual success (Massey and
Satao 2012 ) (Fig. 2.2 ).
With this SDLC model, the process of software development is made by
increments, through a series of different releases. When the product is launched,
when it has its

first increment, it is ready for consumer use. Then, according to the

clients response to the software, new increments are made to improve the product.

The increments will continue to be added, until the completion of the

'

final product

(Massey and Satao 2012 ).
Each stage is scheduled and structured to allow the development of parts of the
system at varied rates and times and to incorporate them into the global project
when they are finished. Thus, this model highlights the sequential process of the

different phases of development while also trying to maximize the bene ts of

allowing changes, improvements, and additions to be made between each incre-
ment. Development is broken into smaller efforts. These are consistently monitored,
so that progress can be accompanied and measured (Texas Project Delivery
Framework 2008 ).
This model fundamentally outlines a progressive development process through
the gradual addition of more features, until the completion of the system. It is a
more

flexible method, because it allows for the incorporation of needs that might
not have been obvious at the start of the process, and it facilitates the changes that
come with later assessment of different requirements. Additionally, since it builds
on each of the phases, it allows for wider amplitude of improvement in the fol-
lowing stages (Executive Brief 2008 ). Thus, product delivery is not only faster, but
it is also easier to test and eventually correct.
However, the downside to this approach is that it can be more costly to develop
and release multiple versions of the product. On the other hand, when a later
increment is developed due to a new found problem or necessity, it can have
compatibility issues with earlier versions of the product (Tilloo 2013 ).