Rational Unified Process (RUP)


Topics:  RUP Definition  RUP Strengths  RUP Weaknesses Addressed by OPF  Major Differences

RUP Definition

According to Rational's webpage describing it, the "Rational Unified ProcessŪ is a software engineering process, delivered through a Web-enabled, searchable knowledge base. The process enhances team productivity and delivers software best practices via guidelines, templates and tool mentors for all critical software life cycle activities." Note that RUP is a tailorable process rather than an extensible and tailorable process framework like OPF. RUP is largely restricted to software development, and is therefore weak when it comes to systems development and business reengineering topics such as digital branding and content management. In general, RUP is less flexible and less complete the the OPF.

RUP Strengths

RUP is widely recognizing as having the following strengths relative to other development processes. Where practical, these strengths have been reused and incorporated into OPF:

RUP Weaknesses Addressed by OPF

RUP is widely contraversial and seen as having the following weaknesses relative to the OPEN Process Framework (OPF):

Major Differences

The following subsections and their associated tables summarize the major differences between RUP and OPF:

Work Products - Major Differences

The following tables summarize the major differences between RUP and OPF work products:

Difference Rational Unified Process (RUP) OPEN Prosess Framework (OPF)
Name and Type
A process named after its for-profit company. A process framework named after its open philosophy and volunteer consortium.

Management Work Products - Major Differences

The following table summarize the major differences between RUP and OPF:

Work Product Sets
(OPF Terminology)
OML
WPs
RUP
WPs
Comparisons
Management 15 11 TBD
Configuration Management 6 3 TBD
Risk Management 2 2 TBD
Disaster Recovery 4 0 Not addressed by RUP!
Training 6 1 TBD
Quality Engineering 5 1 TBD
Process Engineering 100+ 40* TBD
Metrics Engineering 2 2 TBD
Environments Engineering 12 0 TBD
Security Engineering 2 0 Not addressed by RUP!
Digital Branding 6+ 0 Not addressed by RUP!
Requirements 20 18 TBD
Architecture 17 19 Both strong.
Design 7 14 TBD
Implementation 11 1 RUP weak!
Integration 4 2 TBD
Testing 15 8 TBD
Deployment 13 8 TBD
Content Management 2 0 Not addressed by RUP!
Maintenance 0 0 TBD
Operations 1 0 Not addressed by RUP!
User Support 0 0 Not addressed by RUP!
Retirement 0 0 Not addressed by RUP!
Model 4 0 RUP models are spread among requirements, architecture, design, and implementation.
Total/Summary 0 0 TBD
Summary: OPF has more types of work products (RUP artifacts). OPF has work products. OPF is stronger in the areas of digital branding, content management, business engineering.
OPF RUP Rationale
Process Framework Single Process OPF is more flexible.
Systems Software TBD.
E-markets Emphasis General Purpose TBD.
Delivery Cycle Development Cycle Must cover pre/post sales.
Quality Requirements Primarily Use Cases Quality requirements impact architecture.
Covers Roles and Teams Only covers roles OPF is more complete.
Also XP, RDD, DBC Three Amigos OPF is more complete.

Phases

OPF RUP Rationale
Discovery Missing OPF covers entire delivery cycle.
Strategy Missing OPF addresses customer's overall eStrategy.
Inception Inception OPF emphasis on e-market systems.
Elaboration Elaboration OPF emphasis on e-market systems.
Construction Construction OPF emphasis on e-market systems.
Transistion Transistion OPF emphasis on e-market systems.
Usage Missing OPF covers entire delivery cycle.

Work Products

OPF RUP Rationale
Work Products Artefacts More traditional and understandable term
Strategy Document Missing OPF addresses customer's overall eStrategy.
Application Vision Statement Application Vision Statement Roughly similar but OPF AVS is more complete.
System Requirements Specification Use Case Model & Supplimentary Specifications More balanced treatment of operational and quality requirements
Project Glossary Project Glossary OPF differentiates domain and technical definitions
Domain Model Document TBD OPF emphasis on e-market systems.
System Architecture Document Missing OPF emphasizes systems development
Software Architecture Document Software Architecture Document Very similar.

Terminology

OPF RUP Rationale
Work Product Artefact Work product is the traditional term. Artefacts are what you have left after everyone dies.
Role Worker Role is more descriptive. Not every role is a worker.