Professional Documents
Culture Documents
14/12/2006
IBM Confidential
To overcome the above criteria we need systematic approach which are nothing but
software Life Cycle Models.
IBM Confidential
General Model
Water fall model/ Linear Sequential/ Classic Life Cycle Model
V-Model
Rapid Application Development (RAD) model
Incremental Model
Spiral Model
Proto type model
Fourth Generation (4GT) Techniques
IBM Confidential
Requirements
Analysis
System
Design
Coding
Testing
Delivery
System/information
Engineering
IBM Confidential
The "waterfall model", documented in 1970 by Royce was the first publicly documented
life cycle model. The model was developed to help with the increasing complexity of
aerospace products.
This is the most common and classic of life cycle models, also referred to as a linearsequential life cycle model. It is very simple to understand and use. In a waterfall
model, each phase must be completed in its entirety before the next phase can begin.
At the end of each phase, a review takes place to determine if the project is on the
right path and whether or not to continue or discard the project. Unlike what I
mentioned in the general model, phases do not overlap in a waterfall model.
The least flexible and most obsolete of the life cycle models. Well suited to projects
that has low risk in the areas of user interface and performance requirements, but high
risk in budget and schedule predictability and control.
IBM Confidential
Requirements
Specification
System
design
Coding
Testing
Delivery
IBM Confidential
Advantages
Simple and easy to use.
Easy to manage due to the rigidity of the model each phase has specific
deliverables and a review process.
Phases are processed and completed one at a time.
Works well for smaller projects where requirements are very well understood/stable.
Disadvantages
Its difficult to respond to changing customer requirements.
Adjusting scope during the life cycle can kill a project
No working software is produced until late during the life cycle.
High amounts of risk and uncertainty.
Poor model for complex and object-oriented projects.
Poor model for long run and ongoing projects.
7
IBM Confidential
V - model
Another variant of the waterfall model the V-model associates each development
activity with a test or validation at the same level of abstraction. Each development
activity builds a more detailed model of the system than the one before it, and each
validation tests a higher abstraction than its predecessor.
The least flexible and most obsolete of the life cycle models. Well suited to projects that
has low risk in the areas of user interface and performance requirements, but high risk
in budget and schedule predictability and control.
IBM Confidential
V - model (contd.)
High Level
Design
or)
n(
t io
g
ca
tin
rifi
es
Ve
cT
ati
St
Low level
Design
System
Test Plan
Integration
Test Plan
Module Level
Test Plan
System
Testing
Integration
Testing
Module Level
Testing
Va
l
Dy ida
tio
na
n
m
(o
ic
Te r)
st
in
g
Requirements
Code &
Unit test
IBM Confidential
V - model (contd.)
Advantages
Higher chance of success over the waterfall model due to the development of test
plans early on during the life cycle.
Works well for small projects where requirements are easily understood.
Disadvantages
Model doesnt provide a clear path for problems found during testing phases.
10
IBM Confidential
Incremental/Iterative model
This model does not attempt to start with full specification of requirements. Multiple
development cycles take place here, making the life cycle a multi-waterfall cycle.
Cycles are divided up into smaller, more easily managed iterations. Each iteration
passes through the requirements, design, implementation and testing phases.
A working version of software is produced during the first iteration, so you have working
software early on during the software life cycle. Subsequent iterations build on the
initial software produced during the first iteration.
Key Points
Requirements are prioritised and the highest priority requirements are included in early
increments
11
IBM Confidential
Increment 1
No. of increments
Analysis
Increment 2
System
Design
Coding
Analysis
System
Design
Coding
Analysis
System
Design
Increment 3
Testing
Delivery of 1st
Increment
Testing
Coding
Delivery of 2nd
Increment
Testing
Delivery of 3rd
Increment
Time
12
IBM Confidential
Advantages
System functionality is available earlier and customer does not have to wait as long.
Early increments act as a prototype to help elicit requirements for later increments.
Easier to manage risk because risky pieces are identified and handled during its
iteration.
Disadvantages
Problems may arise pertaining to system architecture because not all requirements are
gathered up front for the entire software life cycle.
13
IBM Confidential
Prototype model
In this model, a prototype (an early approximation of a final system or product) is built,
tested, and then reworked as necessary until an acceptable prototype is finally achieved
from which the complete system or product can now be developed.
Prototype paradigm begins with requirements gathering. Developer and customer meet
and define the overall objectives for the software, identify whatever requirements are
known, and outline areas where further definition is mandatory.
A quick design occurs which leads to the construction of prototype.
The prototype is evaluated by the customer/user and used to refine the requirements for
the software to be developed.
Iteration occurs as the prototype is tuned to satisfy the user requirements, while at the
same time enabling developer to better understand what needs to be done.
14
IBM Confidential
Prototype model
Begin
Begin
Listen
Listentoto
Client/user
Client/user
Build
Build
Prototype
Prototype
Client
Client
evaluates
evaluatesthe
the
prototype
prototype
Prototype used for
Understanding the requirements for the user interface
Examining feasibility of a proposed design approach
Disadvantages
Users treat the prototype as the solution
A prototype is only a partial solution
15
IBM Confidential
Spiral - model
Presented by Boehm in 1985. The spiral model is focused on risk management.
This model of development combines the features of the prototyping model and the
waterfall model. The spiral model is favored for large, expensive, and complicated
projects.
The spiral model is similar to the incremental model, with more emphases placed on risk
analysis. The spiral model has four phases: Planning, Risk Analysis, Engineering and
Evaluation. A software project repeatedly passes through these phases in iterations
(called Spirals in this model). The baseline spiral, starting in the planning phase,
requirements is gathered and risk is assessed. Each subsequent spiral builds on the
baseline spiral.
Requirements are gathered during the planning phase. In the risk analysis phase, a
process is undertaken to identify risk and alternate solutions. A prototype is produced at
the end of the risk analysis phase.
Software is produced in the engineering phase, along with testing at the end of the
phase. The evaluation phase allows the customer to evaluate the output of the project to
date before the project continues to the next spiral.
In the spiral model, the angular component represents progress, and the radius of the
spiral represents cost.
16
IBM Confidential
Planning
Planning
Risk
Risk
Analysis
Analysis
Go/No-Go
Decision
Evaluation
Evaluation
17
IBM Confidential
Development
Development
18
IBM Confidential
19
IBM Confidential
20
IBM Confidential
14/12/2006
IBM Confidential