Back to Jackson-Reed, Inc. home page

Rational Unified Process (RUP): An Introduction and Implementation Perspective

Seminar Description

Rational Unified Process (RUP): An Introduction and Implementation Perspective explores what is necessary to effectively understand and implement the Unified Process from Rational Software. The Rational Unified Process (RUP) has become the de facto process for managing, monitoring and controlling projects implementing software intensive systems. Based on its iterative and incremental approach, risk is reduced while organizations can assimilate new requirements from the ever-changing business environment.

This seminar will introduce the project manager, user, and analyst to the comprehensive set of workflows and artifacts provided by RUP. In addition, the role of the Unified Modeling Language (UML) within RUP will be explained. 

RUP, out of the box, can be overwhelming: 103 artifacts, 9 workflows, 8 project plan templates, 4 phases, 136 activities, 14 work guidelines, 43 Word and HTML templates. Learn from professionals who not only teach RUP but who actually use it and implement it, what the "15 RUP Essentials" are and how to leverage them to your benefit. Also learn how to setup your "company process" and prepare it for your first "project web".

Various Visual Modeling tools will be discussed to reinforce their importance in RUP. Although they aren’t required for the success of RUP or for the delivery of the course, they have a profound effect on the success of the process in the organization.

Who Should Attend

Project managers, project analysts, methodology architects, business users,  and technology architects. 


This course has no prerequisites. 

Jackson-Reed's Requirements Gathering with Use Cases course would be a natural follow-on or precursor to this course.

Seminar Length

2 days 

Seminar Outline 

1.     Introduction

  1. Course Objectives

  2. Symptoms of Projects that Fail

  3. Cost of Requirements Errors

  4. How Should Projects Work

  5. What is a Systems Development Lifecycle (SDLC)?

  6. What is a Software Process Model?

  7. Waterfall Process Model

  8. Spiral Process Model

  9. What Does the Dictionary Say?

  10. What is a Methodology?

  11. Information Engineering

  12. Object-Oriented

  13. RUP Process Model

  14. RUP Principles

  15. Knowledge Base Content

  16. Weaknesses in RUP

2.     Rational Unified Process (RUP): Defined

  1. RUP Process Model

  2. RUP: Best Practices

  3. Iterative Development

  4. Manage Your Requirements

  5. Verify Software Quality

  6. Manage Change

  7. RUP: The Lifecycle Process

  8. Disciplines and Models

  9. Phases and Milestones

  10. Phases and Effort

  11. Disciplines: Two Levels

  12. Coarse and Fine-grained Project Plans

  13. Inception Phase

  14. Importance of the Facilitated Workshops

  15. After the Facilitated Session

  16. Inception Phase: Exit Criteria

  17. Inception Phase Milestone: Lifecycle Objective

  18. Elaboration Phase

  19. The Architectural Prototype

  20. Elaboration Phase: Exit Criteria

  21. Elaboration Phase Milestone: Lifecycle Architecture

  22. Construction Phase

  23. Who is Doing What?

  24. Construction Phase: Exit Criteria

  25. Construction Phase Milestone: Initial Operational Capability

  26. Transition Phase

  27. Who is Doing What?

  28. Transition Phase: Exit Criteria

  29. Transition Phase Milestone: Production Release

  30. Artifact

  31. Activity

  32. Using the 80/20 Rule

  33. Irrational Disjointed Chaos

3.     Rational Unified Process (RUP): Artifacts

  1. Nine Core Disciplines

  2. Discipline: Business-Modeling

  3. Discipline: Requirements

  4. Discipline: Analysis and Design

  5. Discipline: Implementation

  6. Discipline: Test

  7. Discipline: Deployment

  8. Discipline: Configuration and Change Management

  9. Discipline: Project Management

  10. Discipline: Environment

  11. Overall Strategy

  12. Key Issues and Risks

  13. Caveats

  14. 15 “Essential” Artifacts

  15. Finding Architecturally Significant Requirements

  16. Finding Architecturally Significant Requirements

4.     Customizing RUP and Support for Legacy and Packaged Products

  1. RUP = Lots of Stuff!!!

  2. RUP: Tailorable

  3. Two Ways to Modify RUP

  4. Legacy and RUP

  5. Greenfield Development

  6. Acquisitions: Lifecycle for First Increment

  7. Progression Acquisition Program Lifecycle

  8. Contractual Lifecycle

  9. Plan Solicitation

  10. Final Closure and Acceptance

  11. RUP and RFPs/RFTs

5.     RUP Summary

  1. Iterative: Not a Free Ride 5-2

  2. Traps of the Iterative Lifecycle.. 5-4

  3. Some Dos 5-6

  4. And Some Don’ts.... 5-7

  5. Cultural Changes to Make This a Success 5-12

  6. RUP: Next Steps 5-14

For Jackson-Reed, Inc. Consulting Information, e-mail
For Jackson-Reed, Inc. Training Information, e-mail
Phone: (888) 598-8615 (toll free within US and Canada) or (832) 248-8531
Fax: (866) 804-0387 (toll free within US and Canada) or (832) 442-5996                           
6700 Woodlands Parkway, Suite 230-303
The Woodlands, Texas 77382  (Houston, Texas)

[Home] [Next]