The Rational Unified Process

1
The Rational Unified Process

• CS4320
• Fall 2005

2
Fundamental Guidelines

• Use-Case Driven
• Architecture-Centric
• Iterative
• Incremental

3
Use-Case Driven

• Fundamental Expression of Requirements is through
  Use Cases

UC1 WITHDRAW MONEY 1. BankCustomer identifies
themselves 2. System verifies identity 3.
BankCustomer chooses account and amount to
withdraw. 4. System deducts amount from
account 5. System dispenses money 2a.
BankCustomer cannot be identified . 4a.
BankCustomer has insufficient funds
BankCustomer
4
Architecture-Centric

• Expression of system design top-down via UML

Tested by
Distributed by
Implemented by
Specified by
Realized by
ok
ok
Test Model
Implementation Model
Deployment Model
Design Model
5
Incremental

• We follow four phase life cycle
• Inception (Scope, Objectives, Business Case) 10
• Elaboration (Analysis, Design, Detail Cases) 30
• Construction (Build, Testing) 50
• Transition (Fielding, Beta Tests, Training)10

6
Iterative

• Small mini-projects, overlapped stages
• Every iteration cycle delivers product

7
RUP Division of Effort
8
Process Description

• Workers (Who)
• Activities (How)
• Artifacts (What)
• Workflows (When)
• UPEDUhttp//www.upedu.org/upedu

9
RUP Process Definition
10
Artifacts ( Inception)

• Vision and Business Case
• Use Case Model
• Supplementary Specification
• Glossary
• Risk Management
• Prototypes
• Iteration Plan
• SDP
• Tailored Process Description

11
Artifacts (Elaboration)

• Domain Model / Analysis Model
• Design Model (class, interaction, state)
• Software Architecture Description
• Data Model
• Test Model
• Implementation Model
• Use Case Storyboards/UI Prototypes

12
Artifacts (Construction)

• Source Code
• Build Scripts
• Unit Tests
• Test Cases

13
Workers, Actors, Roles

• Project Manager
• Architect
• Tester
• Designer
• Use Case Specifier, Designer, Engineer
• Analyst (System Analyst)
• Component Engineer
• System Integrator

14
Were not doing RUP if (Larman)

• We try to define all use cases and requirements
  up front
• We try to draw detailed designs of all components
  before we code
• We think that inceptionrequirements,
  elaborationdesign, constructionimplementation.
• We use elaboration to fully define models which
  are translated into code.
• Our iterations are 3 months instead of 3 weeks
• We think RUP is just creating a bunch of
  documents or UML drawings
• We try to write a big project plan up front that
  details everything from start to finish of the
  project.

15
UPEDU

• Tailored RUP for education
• Full description of artifacts, formats and roles
  and workflows are on web site
• www.upedu.org

16
Final Project RUP

• http//www.cc.gatech.edu/classes/AY2006/cs4320_fal
  l/Project/project_main.html
• You may want to read about the following items
  before we do business cases
• WebCT (webct.com)
• Webwork (webwork.cc.gatech.edu)
• Moodle (moodle.org)