IBM Rational Unified Process (RUP)

Proven best practices for software and systems delivery and implementation and for effective project management IBM

The Rational Unified Process (RUP) What is it?

The Rational Unified Process is a software engineering process and a product. It provides a disciplined approach to assigning tasks and responsibilities within a development organization. Its goal is to ensure the production of high-quality software that meets the needs of its end users within a predictable schedule and budget.

Rational Method Composer RMC (RUP Tool) Features

Online Repository of Process Information and Description in HTML

format Templates for all major artifacts, including: RequisitePro templates (requirements tracking) Word Templates for Use Cases Project Templates for Project Management Process Manuals describing key processes

Rational Method Composer RMC (RUP Tool) Features

RUP Tool Rational Method Composer Video Tutorial http://blog.haumer.net/rational-method-composer/25 Rational Method Composer User Guide http://publib.boulder.ibm.com/infocenter/rmc/v7r5m0/index.jsp?topic=%2Fcom.ibm.rmc .tutorials.doc%2Fexplore_ui%2Fexplore_ui.html\

The Rational Unified Process (RUP)Overall Architecture The Hump Chart

Diagram 1.1
7

The Rational Unified Process (RUP)

Diagram 1.1 shows the overall architecture of the RUP, which has two dimensions: the horizontal axis represents time and shows the lifecycle aspects of the process as it unfolds the vertical axis represents disciplines, which group activities logically by nature. The first dimension represents the dynamic aspect of the process as it is enacted, and it is expressed in terms of phases, iterations, and milestones. The second dimension represents the static aspect of the process: how it is described in terms of process components, disciplines, activities, workflows, artifacts, and roles
8

RUP Architecture

RUP Components
Six best practices Four phases Static & Dynamic Architecture Nine workflows
Core process workflows Core supporting workflows

10

Phases and Iterations

The software lifecycle is broken into cycles, each cycle working on

a new generation of the product. RUP divides one development cycle in four consecutive phases: Inception phase Elaboration phase Construction phase Transition phase
Each phase is concluded with a well-defined milestone - a point in

time at which certain critical decisions must be made, and therefore key goals must have been achieved.
Each phase in RUP can be further broken down into iterations. An

iteration is a complete development loop resulting in release (internal or external) of an executable product, a subset of the final product under development, which grows incrementally from iteration to become the final system.

11

Phase 1: Inception
Overriding goal is obtaining buy-in from all interested

parties Initial requirements capture Project Metrics Analysis Initial Risk Analysis Project Scope definition Initial Use Case Model (10% - 20% complete)

12

Inception Phase: Artifacts(Documents)

13

Inception Phase Workflow

14

Phase 2: Elaboration

The primary objective is to mitigate the key risk items identified by analysis up to the end of this phase. The elaboration phase is where the project starts to take shape. In this phase the problem domain analysis is made and the architecture of the project gets its basic form.

15

Phase 2: Elaboration Artifacts/Documents

A use-case model in which the use-cases and the actors have been identified and most of the use-case descriptions are developed. The use-case model should be 80% complete. A description of the software architecture in a software system development process.
Scenarios
Sequence and Collaboration Diagrams Class, Activity, Component, State Diagrams

Business case and risk list which are revised. A development plan for the overall project. A preliminary user manual (optional) Glossary (so users and developers can speak common vocabulary)

16

Elaboration Phase

17

Phase 3: Construction

18

Construction Phase Artifacts/Documents

19

Construction Phase

20

Phase 4: Transition
The transition phase consists of the transfer of the system

to the user community It includes manufacturing, shipping, installation, training, technical support and maintenance Development team begins to shrink Control is moved to maintenance team Alpha, Beta, and final releases Software updates Integration with existing systems (legacy, existing versions, etc.)

21

Phase 4: Transition

22

Transition Phase

23

24

Business Modeling

25

Requirements

26

Requirements Workflow Detail

27

Requirements Workflow Details

28

Analysis and Design

29

Implementation

30

Test

31

Deployment

32

Configuration and Change Management

33

Project Management

34

Environment

CF:Slides courtesy Island Training.

35

Static Structure of RUP

36

Static Process Elements

37

Static Process Elements

38

Static Process Elements

39

Static Process Elements

40

Dynamic Structure of RUP

The first (horizontal) dimension represents the dynamic aspect

of the RUP process expressed in terms of cycles, phases, iterations, and milestones. In the RUP, a software product is designed and built in a succession of incremental iterations. This allows testing and validation of design ideas, as well as risk mitigation, to occur earlier in the lifecycle. An iterative process breaks the 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.

41

From sequential to an iterative cycle

42

Activities across one development cycle

43

RUP Recap

44

RUP Reading List

What is RUP? TOOL http://www-01.ibm.com/software/awdtools/rup/ RUP Phases http://www.hytechpro.com/our-approach/rup RUP Workflows & Artifacts http://www.fincher.org/tips/General/SoftwareEngineering/RationalUnifiedProcess.shtml RUP Workflows & Disciplines http://en.wikipedia.org/wiki/IBM_Rational_Unified_Process http://www.ambysoft.com/unifiedprocess/rupIntroduction.html

45

Thank You

46