1

IBM Software Group

®

PRJ270: Essentials of Rational Unified ProcessModule 3: RUP Structure and Navigation

2

Module 3 ObjectivesBe familiar with the structure and navigation

facilities of RUP by looking at: The RUP browser Core RUP elements

Role Activity Tool Mentor Artifact Discipline Workflow Detail Phase

Supporting RUP elements Other major sections of RUP Overview of RUP meta-model

3

RUP Browser

4. Tree path

6. Control buttons

1. Views

5. Control buttons

2. Tree browser

3. MyRUP control buttons

4

Navigation During This Module You may navigate to the indicated locations in

RUP according to your Instructor’s directions. All locations indicated are from the Team view. RUP locations are shown as tree paths

Example: The following tree path indicates that you should go to the Roles and Activities tree node and expand it to find the Analysts node.

=

5

Core and Supporting RUP Elements

The elements of RUP can be divided into: Core elements which relate to each other to

form the nucleus of the process. Supporting elements which attach to core

elements to provide additional process guidance.

Core SupportingRoleActivityArtifact

Tool MentorDisciplineWorkflow DetailPhase

Guideline

ConceptTemplateReport

CheckpointWhite PaperRoadmapExample

6

Core RUP Elements: Roles, Activities, Artifacts

Roles perform activities which have input and output artifacts.

Risk List

Project Manager

Identify and Assess Risks

Vision

Example: The Project Manager role performs the Identify and Assess Risks activity, which uses the Vision artifact as input and produces the Risk List artifact as output.

7

Core RUP Element: Role

A role defines the behavior and responsibilities of an individual, or a set of individuals working together as a team.

Team members can “wear different hats”: each member can play more than one role one role can be played by more than one

member

8

Role Description Page

Provides:

General description of role

Artifacts and activities for which the role is responsible

Staffing suggestions

Example:

Navigate to

9

Roles Are Used for Resource Planning

Each individual in the project is assigned to one or several roles.

Resource

Paul

Mary

Joe

Sylvia

Stefan

Role

Designer

Requirements Specifier

System Analyst

Implementer

Architect

Activities

Define Operations

Detail a Use Case

Find Actors and Use Cases

Perform Unit Tests

Identify Design Mechanisms

10

Core RUP Element: Activity

A piece of work a role performs Granularity of a few hours to a few days Repeated as necessary in each iteration

11

Activity Description PageDescribes:

Purpose: The purpose of the activity

Steps: The steps required to fulfill the activity

Input Artifacts:The artifact(s) needed as input

Resulting Artifacts:The artifact(s) produced as output

Frequency: How many times per iteration the activity needs to be performed

Role: The role responsible for the activity

Tool Mentors: Guidance to help the role to perform the activity using a specific tool

More Information: Any Guidelines or Concepts relevant to the performance of the activity

Workflow Details: The workflow details in which this activity appears

Example:

Navigate to

12

Core RUP Element: Tool Mentor

A means of providing guidance by showing how to perform an activity using a specific software tool.

Organized by tool name.

13

A document, model, or model element produced, modified, or used by a process

The responsibility of roles

Likely to be subject to configuration control

May contain other artifacts

Core RUP Element: Artifact

Iteration Plan

Developer Test

Tools

Storyboard

Project Measurements

Workspace

Business Use Case Model

Business Goal

Iteration Assessment

Analysis Model

Architectural Proof-of-ConceptUse Case Model

Test Environment Configuration

User-Interface Prototype

14

Artifact Description PageDescribes:

Name Description of artifactRole Role responsible for artifactTemplates Templates to be used for the

artifactOther Relationships Other artifacts which:

-may contain this artifact-this artifact may contain

Examples Examples to guide you in creating the artifact

More Information Guidelines and Concepts relevant to production of this artifact

Input to ActivitiesActivities for which this artifact is required as input

Output from ActivitiesActivities from which this artifact is produced

Example:Navigate to

15

Economy of Artifacts

Produce only the artifacts that get used. Keep the artifact in the most appropriate

tool, in electronic form (Rose, Excel, RequisitePro, and so on).

Use reports to extract snapshots of information out of models in tools, for review (SoDA, scripts, and so on).

Put effort into artifacts that are part of the product (e.g. models).

16

Summary of Major Artifacts

17

Ways to Find Roles, Activities and Artifacts

1. Navigate through Discipline node.

3. Navigate through Artifacts node.

2. Navigate through Roles and Activities node.

18

Activity Overview and Artifact Overview Diagrams

Activity Overview shows roles, and the activities they perform.

Activity Overview shows roles, and the activities they perform.

Artifact Overview shows roles, and the artifacts for which they are responsible.

Artifact Overview shows roles, and the artifacts for which they are responsible.

19

Content Organization by DisciplinesC

onte

nt

Time

Work from different disciplines is attributed throughout the lifecycle.

20

Core RUP Element: DisciplineTwo ways of navigating the content of RUP

disciplines:

Navigation bar located at the top of the main window.

Navigation bar located at the top of the main window.

Navigation tree located at left of main window.

Navigation tree located at left of main window.

Example: Navigate to

21

Each discipline in RUP contains one workflow. A workflow is the conditional flow of high-level tasks (Workflow Details) that produce a result of observable value.

RUP Workflows

Workflow Details

22

A Workflow Path Is Adapted to:

Position in Lifecycle Phase

Artifacts being produced

Technology Iteration goals

Example:Requirements Workflow

23

Core RUP Element: Workflow DetailExample: Requirements Workflow Example Workflow Detail diagram:

Analyze the Problem

Workflow Details show roles, activities they perform, input artifacts they need, and output artifacts they produce.

Workflow Details show roles, activities they perform, input artifacts they need, and output artifacts they produce.

24

Core RUP Element: PhaseFor each Phase: Main Phase node shows:

An example Iteration Workflow diagram for that phase

Objectives of that phase Essential Activities in that phase

Milestone node shows: Evaluation Criteria for that milestone Artifacts and artifact states necessary to reach that

milestone Sample Iteration Plan node shows:

Relationship of discipline workflows in an early iteration of that phase

Example: Navigate to

25

Supporting Elements

Guideline

Concept Template Report Checkpoint Example White Paper

26

Supporting Element: Guidelines

Provide practical explanations of: How to work with a particular artifact,

including how to create and revise the artifact How to perform an activity or set of activities

Reachable through: Relevant artifact or activity description page Guidelines Overview node or Guidelines

button within a disciplineComplete list available under Overview node.

27

Supporting Element: Concepts

Provide explanations of key ideas related to disciplines and their contents.

Reachable through: Relevant role, artifact or activity description

page Concepts node or Concepts button within a

discipline Complete list available under Overview

node.

28

Supporting Element: Templates

Attached to artifacts which are documents Provide predefined outlines with guidance on

development section contents tailored for RUP For use with:

Microsoft® Word® Microsoft® Project®

Adobe® Framemaker®

Rational SoDA®

Reachable through: Relevant artifact description page

Complete list available under Overview node.

29

Supporting Element: Reports

Attached to artifacts which are non-document type

Extract information about one or more artifacts from a tool

Reachable through: Relevant artifact description page

30

Supporting Element: Checkpoints

Attached to artifacts

Provide a quick reference to help you assess the quality of the artifact

Reachable through: Relevant artifact description page

31

Supporting Element: Examples and White Papers

Examples with various levels of detail are provided in RUP under Overview node.

Examples are also reachable through relevant artifact description page.

Several White Papers are provided in RUP under Overview node.

White Papers are also reachable through relevant role or workflow detail description pages.

32

Other Major Sections of Team View

Overview provides Getting Started information as well as reference lists of supporting RUP elements.

Overview provides Getting Started information as well as reference lists of supporting RUP elements.

About Rational Unified Process describes the Classic RUP product and plug-ins contained in the Classic RUP configuration.

About Rational Unified Process describes the Classic RUP product and plug-ins contained in the Classic RUP configuration.

Additional Resources describes other RUP-related sources of information.

Additional Resources describes other RUP-related sources of information.

33

The Basic Elements of RUP

34

Getting Started ViewContains introductory

material such as: RUP interface and

navigation Use of RUP Web site

facilities such as MyRUP, Extended Help, Keyword Index, Search Engine, and so on.

Essentials of the process. Roadmaps through the

process.

35

Other RUP Views

Other RUP views show subsets of the process that are important to a particular role.

36

Review

Main content of RUP is in Team and Getting Started views. Information in RUP can be found through different routes. Some core elements that make up RUP are:

Roles, Activities, Tool Mentors, Artifacts, Disciplines, Workflow Details, Phases

Disciplines contain one Workflow made up of Workflow Details

Workflow Details show the work that a role does, including activities and artifacts for which the role is responsible.

In addition, there are supporting elements for guidance and help, such as Guidelines, Concepts, Templates, Reports, Checkpoints, Examples, White Papers

37

Exercises

Complete Module 3 Exercise 1: Tracing Dependencies in the Exercises section of your student manual.

This exercise will allow you to apply the RUP navigation skills you have acquired.

Complete the Discussion Points associated with Exercise 1.

38