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

alternatives to accomplish the established goals, as well as risk assessment for each
idea (Bhalerao et al. 2009 ).
The second step is project initiation. After the establishment of a coherent
project with respective goals and scope, a working team is built, with the appro-
priate environment and tools, as well as the working architecture in which the
system will be based. This too is discussed among all stakeholders. At this point, it
is also adequate to establish working time frames and schedules (Ambler 2009 ).
The third step is construction iterations, with each iteration consisting of both
planning and building. Developers release working software in successive incre-
ments that will accommodate the evolution of requirements as outlined by the
various stakeholders. Close collaboration is therefore a fundamental aspect of this
process, as the most effective method to ensure quality and to keep the project ' s

priorities well de ned. Extensive testing of each iteration is also paramount at this

point (Ambler 2009 ).
The fourth and final step is product release. This stage encompasses two stages:

First, nal

reworks and documentations. Next, the product is released, at which point training
is provided to the users in order to maximize operational integration. The working
team might maintain the project so as to allow for product improvement as well as
user support (Bhalerao et al. 2009 ) (Fig. 2.6 ).
The Agile SDLC emerged from the ever-increasing need to match the speed at
which IT evolves. What sets it apart is its dexterity in developing products at a great
speed, with products being deliverable in the course of weeks instead of months.
This is possible due to the model

final testing of the entire system is done, as well as any necessary

' is emphasis on collaborative efforts and docu-

mentation (Executive Brief 2008 ).
Another advantage of the Agile model is that it is very

flexible. It has been
occasionally combined with other existing models. It has the capacity to deliver
systems whose requirements go through constant changes while, at the same time,
demanding strict time limits.

Fig. 2.6 An example of an Agile development life cycle