The Rational Unified Process

A Commercially Available Spiral Model

Implementation
Walker Royce

Overview
How does RUP relate to the spiral model?
Commercial process framework

How have software processes evolved?

Resource expenditure profiles across workflows

The State of the RUP

Lessons learned

The RUP Iterative Life Cycle

Engineering Stage

Production Stage

Inception

Elaboration

Construction

Transition

Idea

Architecture

Beta Releases

Products

Evolving Levels of Detail

Get the architecture right first (the stuff that counts),
then worry about completeness and precision.
The ability to balance life-cycle accuracy and
precision is a discriminating management skill.
Engineering Stage

Implementation
Management

Deployment

Design
Requirements

Implementation
Management

Deployment

Transition

Design
Requirements

Implementation
Management

Deployment

Construction

Design
Requirements

Implementation

Requirements
Management

Deployment

Elaboration

Design

Inception

Production Stage

Iterative Life-Cycle Activities

Inception

Management
Requirements
Design
Implementation
Assessment
Deployment
Environment

Elaboration

Construction

Trans

i tion

One View of Software Process Evolution

Conventional
RUP Workflow
Process
(Waterfall)
Management
5%
Requirements
5%
Design
10%
Implementation
30%
Test &Assessment
40%
Deployment
5%
Environment
5%
100%

Modern
Process
(Iterative)
10%
10%
15%
25%
25%
5%
10%
100%

Future
Process
12%
12%
20%
14%
18%
12%
12%
100%

More balance; less waste during integration and test

Environment

Deployment

Assessment

Implementation

Design

Requirements

Management

Resource Allocation Trends

Next generation
Modern
Conventional

The State of the RUP

1000s of project users, 100s of projects/organizations
Used across a broad range of spiral-oriented projects
Re-architecting or upgrading of legacy systems
New system/product developments
Component based system development
Business modeling-system engineering

Current situation:
Strong process framework (still requires tailoring)
Biggest strength: unifies the project team and stakeholders
Homogeneous process language and web-based online e-coach

Biggest weakness: too easy to interpret as cookbook

Still requires domain tailoring, common sense to be added

Current RUP Improvement Thrusts

e-business guidelines (Web oriented applications)
Analysis and design patterns and frameworks
Improved testing emphasis across the life cycle
Expanded business modeling workflow
Improved deployment workflow
Explicit "build" as an artifact
Designing for usability guidance
UML based metrics and project dashboard
These thrusts reflect experience from field applications

Future RUP Improvement Thrusts

Support for process variants

Configurability and navigation improvements
Localizations (Japanese, Chinese, etc.)
Rational Process Workbench
Process authoring and compilation support

UPM (Unified Process Meta-Model) and OMG submittal

Integration to a project portal
Web-based project artifact repository