Phases of SDLC

SDLC consist of namely phases

1.
2.
3.
4.
5.

Requirement analysis
System and software design
Implementation and unit testing
Integration and system testing
Operation and maintenance

SDLC CAN BE REPRESETED IN

PROCESS MODELS
A s/w process model is abstraction
representation of a process can have defined
in a variety of ways using text, figures.
Presenting the description of s/w is known as
process model. Some process models are:
Waterfall model
Evolutionary development
Spiral development model

Waterfall Model

Requirements defines
needed information,
function, behavior,
performance and interfaces.
Design data structures,
software architecture,
interface representations,
algorithmic details.
Implementation source
code, database, user
documentation, testing.

Usage of Waterfall Model

Requirements are very well known

Product definition is stable
Technology is understood
New version of an existing product
Porting an existing product to a new
platform.

Spiral Process Model

Determine ob jectiv es
alternatives and
constraints

Risk
analys is

Ev aluate altern atives

id en tify, resolve risk s

Risk
analysis
Risk
analysis

REVIEW
Requirements plan
Life-cycle plan

Develop ment
plan

Plan next p hase

Integration
and test p lan

Prototyp e 3
Prototyp e 2

Operational
protoyp e

Risk
analysis Prototy pe 1

Simulations, models, b en ch marks

Concept o f
Operation

S/W
requirements

Requirement
valid ation

Prod uct
design

Detailed
design

Code
Unit tes t
Design
V&V
Integr ation
test
Accep tance
test
Develop, v erify
Serv ice
next-level p rod uct

Usage of Spiral Model

When creation of a prototype is appropriate

When costs and risk evaluation is important
For medium to high-risk projects
Long-term project commitment unwise because of
potential changes to economic priorities
Users are unsure of their needs
Requirements are complex
New product line
Significant changes are expected (research and
exploration)

Evolutionary development
There are 2 types of evolutionary development: Exploratory development is well understood by the
developer, new features are added until a final acceptable
product is built
Throw away prototyping- poorly understood by the
developer. Then exposed to the user to get more refined
requirements. This type of development helps to understand
users requirements clearly which were not properly
understood in beginning.
Specification

Development
Outline
description
Validation

Evolutionary model

Initial version
Intermediate
version

Final version

SDLC can be represented by water fall model

Requirements
analysis and
definition

Following phase
could not start
previous phase
finished
System &
s/w design
Implementation &
unit testing
Integration & sits
testing
Operation &
maintenance