Iterative Model
System Development Life
Cycle
In Iterative model, iterative process
starts with a simple implementation of a
small set of the software requirements
and iteratively enhances the evolving
versions until the complete system is
implemented and ready to be deployed.
What is the Iterative Model?
Iterative Development
Model
Iterative Model Application
Like other SDLC models, Iterative development has some specifc
applications in the software industry !his model is most often used in
the followin" scenarios#
$e%uirements of the complete system are clearly defned and
understood
Ma&or re%uirements must 'e defned( however, some
functionalities or re%uested enhancements may evolve with time
!here is a time to the market constraint
) new technolo"y is 'ein" used and is 'ein" learnt 'y the
development team while workin" on the pro&ect
$esources with needed skill set are not availa'le and are planned
to 'e used on contract 'asis for specifc iterations
!here are some hi"h risk features and "oals which may chan"e in
the future
Iterative Model *ros and Cons
PROS
Some workin" functionality can 'e developed
%uickly and early in the life cycle
$esults are o'tained early and periodically
*arallel development can 'e planned
*ro"ress can 'e measured
Less costly to chan"e the scope+re%uirements
!estin" and de'u""in" durin" smaller iteration is
easy
$isks are identifed and resolved durin" iteration(
and each iteration is an easily mana"ed milestone
,asier to mana"e risk - .i"h risk part is done frst
With every increment operational product is
delivered
Issues, challen"es / risks identifed from
each increment can 'e utili0ed+applied to the
ne1t increment
$isk analysis is 'etter
It supports chan"in" re%uirements
Initial 2peratin" time is less
3etter suited for lar"e and mission-critical
pro&ects
Durin" life cycle software is produced early
which facilitates customer evaluation and
feed'ack
CONS
More resources may be required.
Although cost o change is lesser but it is not very
suitable or changing requirements.
More management attention is required.
System architecture or design issues may arise
because not all requirements are gathered in the
beginning o the entire lie cycle.
!e"ning increments may require de"nition o the
complete system.
Not suitable or smaller pro#ects.
Management comple$ity is more.
%nd o pro#ect may not be &no'n 'hich is a ris&.
(ighly s&illed resources are required or ris&
analysis.
Pro#ect)s progress is highly dependent upon the ris&
analysis phase.
)"ile Model
Agile SDLC model is a combination of
iterative and incremental process models with
focus on process adaptability and customer
satisfaction by rapid delivery of working
software product.
What is the )"ile Model?
4raphical Illustration )"ile Model
)"ile Methods 'reak the product into
small incremental 'uilds !hese 'uilds
are provided in iterations ,ach
iteration typically lasts from a'out one
to three weeks ,very iteration involves
cross functional teams workin"
simultaneously on various areas like
plannin", re%uirements analysis,
desi"n, codin", unit testin", and
acceptance testin" )t the end of the
iteration a workin" product is displayed
to the customer and important
stakeholders
*$2S
Is a very realistic approach to software development
*romotes teamwork and cross trainin"
5unctionality can 'e developed rapidly and demonstrated
$esource re%uirements are minimum
Suita'le for f1ed or chan"in" re%uirements
Delivers early partial workin" solutions
4ood model for environments that chan"e steadily
Minimal rules, documentation easily employed
,na'les concurrent development and delivery within an
overall planned conte1t
Little or no plannin" re%uired
,asy to mana"e
4ives 6e1i'ility to developers
)"ile Model *ros and Cons
C27S
7ot suita'le for handlin" comple1 dependencies
More risk of sustaina'ility, maintaina'ility and
e1tensi'ility
)n overall plan, an a"ile leader and a"ile *M
practice is a must without which it will not work
Strict delivery mana"ement dictates the scope,
functionality to 'e delivered, and ad&ustments to
meet the deadlines
Depends heavily on customer interaction, so if
customer is not clear, team can 'e driven in the
wron" direction
!here is very hi"h individual dependency, since
there is minimum documentation "enerated
!ransfer of technolo"y to new team mem'ers
may 'e %uite challen"in" due to lack of
documentation
Iterative is more accommodative in terms of
chan"e and are suita'le for pro&ects where the
re%uirements are not so well defned, or the
market re%uirements chan"e %uite fre%uently
)"ile is the most popular model used in the
industry )"ile introduces the concept of fast
delivery to customers usin" prototype approach
)"ile divides the pro&ect into small iterations with
specifc delivera'le features Customer interaction
is the 'ack'one of )"ile methodolo"y, and open
communication with minimum documentation are
the typical features of )"ile development
environment
Conclusion
