The Rational Unified Process

1
The Rational Unified Process

• CS4320
• Fall 2003

2
Administrative Note

• Note Taker Announcement
• A student note taker is needed in this course
  to take notes for a student with a disability. 
  The note taker will be paid a stipend for this
  assignment.  Skills needed are the ability to
  take accurate, legible, and organized notes and a
  commitment to attend every lecture.  If
  interested, please contact Reena Shah, office
  phone at 404-894-2561 or via email at
  reena.shah_at_vpss.gatech.edu as soon as possible. 
  Be sure to indicate the Professor's name, time,
  day and course number in the subject line of the
  announcement.

3
Fundamental Guidelines

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

4
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
5
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
6
Incremental

• We follow four phase life cycle
• Inception
• Elaboration
• Construction
• Transition

7
Iterative

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

8
RUP Division of Effort
9
RUP Workflow and Activities
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
UPEDU

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

15
Final Project RUP

• TSP Support Tool
• Begin after we complete TSP project
• Two iterations
• Target Java Open-Source DBMS
• Shrink-wrap market with potential customers
• USAF/DoD
• Education Institutions
• NASA