You are on page 1of 22

Life Cycle Models

Terry Bahill
Systems and Industrial Engineering
University of Arizona
terry@sie.arizona.edu
©, 2002-07, Bahill
This file might be located at
http://www.sie.arizona.edu/sysengr/slides/
Life cycle models
• The following slides show several life cycle
models.
• Each gives a different view of the system
life cycle.
• Each emphasizes a different aspect of the
life cycle.

02/01/10 2
BAE LM 01/00 life cycle phases
• Market Analysis
• Prepare Bid/No Bid Information
• Prepare Proposal
• Contract Submitted, Awarded & Negotiated
• Initial Design
• Design System
• Integration of System
• System Test
• Production, Installation and Commissioning
• In Field Service and Support
• Disposal

02/01/10 3
Problem
Statement
Retirement & Requirements
Replacement Discovery

Operations & The System Alternatives


Maintenance Life Cycle Investigation

Integration
System Design
and Test

Implementation

02/01/10 4
The system life cycle
• The system life cycles for a large office building
and a roll of film will be different.
• An office building will be used continuously and
modified frequently as tenants change through its
life cycle.
• A roll of film will be in storage most of its life,
rarely handled or modified, and used once.
• But their life cycles will go through similar phases.
• Defining the expected system life is an important
design decision.

02/01/10 5
It is a cycle
• You recycle each time commercial software
is upgraded, e.g.,
• after Solaris 8 is upgraded to
• Solaris 9 and again for
• Solaris 10.

02/01/10 6
It is a cycle
• You recycle each time commercial software
is upgraded, e.g.,
• when you upgrade to Windows 95
• when you upgrade to Windows 98
• when you upgrade to Windows 2000
• when you upgrade to Windows XP
• when you upgrade to Vista

02/01/10 7
The Vee Life-Cycle Model

Mission Operation &


Continuous Quality Improvement Plan
Analysis Retirement

Ssystem Final
Validation Plan
Requirements System Test

Functional Verify
Verification Plan
De Decomposition Subsystems
c n
om
a tio
po Physical
Test Plan
Test
gr
si
tio Decomposition Components te
In
n

Build
Components

The design down-stroke and the integration and test upstroke

02/01/10 8
The V-diagram

Project Assets Library


Requirements System
Development Acceptance

Conceptual
Architectural System
Model Model Integration & Test

Sub-system
Design Model
Integration & Test

Configuration Managed
Documentation
Implementation -Requirements
-Design
Unit Test -Test

02/01/10 9
The V/W-diagram
Development progresses by increment, but
how does systems engineering fit in?

Requirements System Requirements System


Development AcceptanceDevelopment Acceptance

ProjectLibrary
ProjectLibrary
ConceptualArchitectural System
ConceptualArchitectural System
Model Model Integration & Test
Model Model Integration & Test

Sub-system
Design Model
Sub-system Integration & Test
Design Model
Integration & Test

Implementation
Implementation Unit Test
Unit Test
Project Schedule
02/01/10 10
The life cycle
The life cycle starts with the initial
identification of need and continues
through system retirement and disposal.
Typical life cycle phases include:
– Conceptual Design
– Preliminary Design
Design
– Detail Design
– Component Development
– Integration and Test
Test
– Qualification Test
Test
– Production
– Systems Operation
– Operation & Maintenance
Maintenance
– Retirement / Disposal
Disposal

02/01/10 11
Commonly used life cycle models
Waterfall Model: Sequential activities completed in order
– Provides feedback loops between the steps to allow refinements to
the design
Spiral Model: Commonly used on SW intensive programs
– Continual and iterative examination of objectives, design
alternatives, validation methods via multiple iterations
Evolutionary Acquisition (DODI 5000.2).
• Encompasses spiral and incremental development.
• Requires stable, useable, intermediate systems.
IBM Rational Unified Process (RUP): iterative incremental
development based on reducing design risk during the
early phases.
– Development process consists of four phases: Inception,
Elaboration, Construction and Transition. Each phase has one or
more iterations.
– An iteration consists of the entire set of SW development including
requirements development, design, code, integration and test.

02/01/10 12
Waterfall model
Requirements
Analysis

Functional
Analysis

Requirements
Allocation

Tradeoff
Studies

Synthesis

Evaluation

Integration

Verification & Validation Feedback Acceptance Test

02/01/10 13
02/01/10 14
02/01/10 15
Spiral Lifecycle Model

02/01/10 16
DoD Evolutionary Acquisition

Money and New


Requirements

02/01/10 17
RUP life cycle

02/01/10 18
Life Cycle Phases
Operation,
Activities Inception Elaboration Construction Transition
Retirement &
Replacement
Requirements
Time

Analysis

Design

Implementation

Verification

Operations
Iter. Iter. Iter. Iter. Iter.
Iterations #1 #2 #3 #n-1 #n
Reviews
MCR SRR PDR CDR TRR TST

02/01/10 19
02/01/10 20
Requirements Development will be different
based on the life cycle model selected.
– The Waterfall Model includes intensive up-front
requirements development.
– The spiral model requires multiple iterations of requirements
development as the spirals develop. It requires that
requirements be prioritized.
– Time boxing* is a special spiral model that defines a specific
number of requirements that need to be addressed in a
short time span. Agile development may be a subset of this.
– With evolutionary acquisition new requirements are added
for each new system or release.
– In the RUP iterative process, the major effort in
requirements development occurs in the first phase
(Inception).
– See RF.Choose Lifecycle Model.doc

02/01/10 21
02/01/10 22

You might also like