Rational Unified Process

Jed Kao-Tung Chang

 What is the Rational Unified
Process?
 A software engineering process
 Process framework
 Outline
 Static Structure: Process Description
 Dynamic Structure: Iterative Development
 An Architecture-Centric Process
 A Use-Case-Driven Process
 Deployment Workflow
 Iteration Plans
 Implementing the Rational Unified Process
 Static Structure
 The Rational Unified Process model is built
on three entities: roles, activities, and
artifacts.
 Workflows relate activities, artifacts, and
roles in sequences that produce valuable
results.
Example of the Workflow
 Dynamic Structure: Iterative
Development
 The sequential, or waterfall, process is fine
for small projects.
 An iterative process breaks a development
cycle into a succession of iterations.
 A development cycle is divided into a
sequence of four phases that partition the
sequence of iterations. The phases are
inception, elaboration, construction, and
transition.
From sequential to an iterative
cycle
Activities across one development
cycle
 Benefits of an iteration approach
 The iterative approach accommodates
changes in requirements and in
implementation strategy. It confronts and
mitigates risks as early as possible. It
allows the development organization to
grow, to learn, and to improve. It focuses
on real, tangible objectives.
 Architecture View
 System architecture is used in the Rational
Unified Process as a primary artifact for
conceptualizing, constructing, managing, and
evolving the system under development.
 Architecture is a complex concept that is best
represented by multiple, coordinated
architectural views.
 An architectural view is an abstraction of a
model that focuses on its structure and its
essential elements.
 Use-Case-Driven Process
 Use cases drive numerous activities in the
Rational Unified Process:
 Creation and validation of the design model
 Definition of the test cases and test
procedures in the test model
 Planning of iterations
 Creation of user manuals
 Deployment of the system
 The Deployment Workflow
 The purpose
 Timing of Deployment
 The Deployment discipline takes care of all
artifacts delivered to the end users as well
as supporting organizations.
Workflow
 Typical Iteration Plans
 An iteration in the inception phase to
define the project vision and the business
case
 An iteration early in the elaboration phase
to build an architectural prototype
 An iteration late in the construction phase
to implement the system
Defining the Product Vision and the
Business Case
Building an Architectural Prototype
Implementing the system
Implementing the Rational Unified
Process
 Step 1: Assess the
Current State
 Step 2: Set (or Revise)
Goals
 Step 3: Identify Risks
 Step 4: Plan the Process
Implementation
 Step 5: Execute the
Process Implementation
 Step 6: Evaluate the
Process Implementation
Implementing the Rational Unified
Process
 Summary
 Rational Unified Process, or RUP, is a
configurable software development
process platform that delivers practices
and a configurable architecture.

 Enables the developer to select and

deploy only the process components they
need for each stage of their project.
 Reference
 Boehm, Barry W. 1996. "Anchoring the Software Process." IEEE Software, July, pp.
73–82.
 Boehm, Barry W. 1998. "A Spiral Model of Software Development and Enhancement."
IEEE Computer, May, pp. 61–72.
 Jacobson, Ivar, Grady Booch, and James Rumbaugh. 1999. The Unified Software
Development Process. Reading, MA: Addison-Wesley.

 Philippe Kruchten, 2003. The Rational Unified Process, An Introduction. Addison

Wesley.
 Craig Larman, 2003. Applying UML and Patterns : An Introduction to Object-Oriented
Analysis and Design and Iterative Development (3rd Edition)
 Booch, Grady. 1994. Object-Oriented Analysis and Design with Applications, Second
Edition. Reading, MA: Addison-Wesley.
 www-306.ibm.com/software/awdtools/rup/
Questions?