UML Weekend Crash Course™ - To Parent Directory

Session 2—UML and Development Methodologies 15
Workflows
Business Modeling
Requirements
Analysis and Design
Implementation
Test
Deployment
Configuration and
Change Mgmt
Project Mgmt
Environment
Phases
Inception Elaboration Construction Transition
Initial
Iter
#1
Iter
#2
Iter
#3
Iter
#4
Iter
#5
Iter
#6
Figure 2-1 The Rational Unified Process, phases and workflows
For example, the case study presented in this book refers to an inventory control system.
The first iteration on this project might focus heavily on requirements and result in a risk
assessment, a glossary of inventory control terms, and some screen and forms layouts for
receiving and shipping to help the users visualize their requirements. The second iteration
might create the Use Case diagram and a set of one or more prototypes from the original
screen layouts. A few iterations later you might take one Use Case and actually build the
application to support a screen to set the standards for the screen look and feel and to test
the basic architecture of the application.
The iterative approach continues until all the requirements have been satisfied and the
system is fully implemented.
Note
You may have the impression that the Rational Unified Process is a standard
like the Unified Modeling Language. The choice of the name might have been
a smart marketing ploy, but that does not make it a standard. There are many
other valuable methodologies to consider.
Strengths of the RUP
The emphasis on iterative development and incremental deliveries is a time-tested
and valuable approach that prevents many common project problems. However, it
must be noted that this approach is common to most of the current methodologies.
The process is well defined and supported by the Rational modeling tool.
The artifacts and the roles of the project participants are also very well defined.
The process combines many of the best practices from many successful methodologies.
The process is comprehensive.