SOFTWARE ENGINEERING SOFTWARE LIFECYCLE MODELS

THE BASIC WATERFALL MODEL

These slides contain a few different software

lifecycle models.

Requirement
specification
Analysis &
Design
Implementation

Testing

Maintenance
27.9.2004

Software Engineering 2004

Jyrki Nummenmaa

27.9.2004

Software Engineering 2004

Jyrki Nummenmaa

PROTOTYPING FOR
REQUIREMENT ANALYSIS

A MODIFIED WATERFALL MODEL

Requirement
spec. - V&V

Requirement
spec. - V&V

Analysis &
Design - V&V

Quick Analysis
& Design - V&V

Implementation

Analysis &
Design - V&V
Implementation

- V&V

Quick Implementation - V&V

- V&V

Testing V&V

V&V = Verification and Validation

Testing V&V

V&V = Verification and Validation

Maintenance
- V&V

27.9.2004

Software Engineering 2004

Jyrki Nummenmaa

- V&V
3

27.9.2004

B2
B1

A1
A0

D1

D3

C1

C3

Client evaluation
and input

27.9.2004

B0

C2

D2

It is useful to divide the development so that the

subsequent releases are based on the previous
releases.
Here it is important to choose the increments in
such a way, that the feedback from the previous
increments shows if the development is going
right.
Also, the previous releases should be independent
of the following ones.

Risk analysis
Prototyping

A2

Software Engineering 2004

Jyrki Nummenmaa

INCREMENTAL SOFTWARE
DEVELOPMENT

THE SPIRAL (ITERATIVE) MODEL

Planning

Maintenance

Model simulation
Operational prototype
Verification for next level

Software Engineering 2004

Jyrki Nummenmaa

27.9.2004

Software Engineering 2004

Jyrki Nummenmaa

EVOLUTIONARY SOFTWARE
DEVELOPMENT

THE MANAGEMENT VIEW

In evolutionary software development different

activities (design, implementation, testing, and even
requirements specification) may all progress at the
same time.
In this type of a situation controlling the project can
be very difficult.
Evolutionary software development may take place
because it is not really known what is needed or how
it can be achieved.
Evolutionary software development may also be a
sign of lack of control over the development process.
27.9.2004

Software Engineering 2004

Jyrki Nummenmaa

Do a feasibility study to find out

whether it is feasible to implement a
new system.
Build new system: requirement specification,
analysis & design, implementation, testing
Installation

Maintenance
and audit
27.9.2004

Software Engineering 2004

Jyrki Nummenmaa

NEW DEVELOPMENTS
Special considerations for distributed software and
web-based software
Availability of Commercial Off-The-Shelf (COTS)
components.
Many companies now work as integrators they
use COTS and subcontractors and maybe only
write a minor part of the software themselves.
Lightweight process models to get more
flexibility and to aknowledge the fact that it is so
hard to get the requirements right.

27.9.2004

Software Engineering 2004

Jyrki Nummenmaa