This work is about to provide some brief and fast review of RUP

1. Brief review of
Rational Unified
Process
Morteza Bandidarian
1

2. Agenda
 Terms and definitions
 What is RUP?
 Key aspect of RUP
 6 Best practices
 RUP Architecture
 Dynamic aspect
 Static Aspect
 Workers
 RUP Workflows
 QA
 References
2

3. Agenda
 Terms and definitions
 What is RUP?
 Key aspect of RUP
 6 Best practices
 RUP Architecture
 Dynamic aspect
 Static Aspect
 Workers
 RUP Workflows
 QA
 References
3

4. RUP Terms And Definitions
 Cycle: it includes all the activities that are
executed during project time.
 Phases: Each cycle in the RUP is broken down
into a sequence of four phases, called Inception,
Elaboration, Construction, and Transition.
4

5. RUP Terms And Definitions
 Iteration: Inside each phase there may be
one or more iterations. Software is developed
in each iteration,
 Milestone: The point at which an iteration
formally ends; corresponds to a release
point.
5

6. RUP Terms And Definitions
6
 Workflow: is a sequence of activities
that produces a result of observable
value.
 Discipline is a collection of activities
that are related to a major "area of
concern" within the overall project

7. Agenda
 Terms and definitions
 What is RUP?
 Key aspect of RUP
 6 Best practices
 RUP Architecture
 Dynamic aspect
 Static Aspect
 Workers
 RUP Workflows
 QA
 References
7

8. What is RUP?
 An approach to assigning and managing tasks and
responsibilities in a development organization
 Focused on high-quality software that meets the needs of its
end users within a predictable schedule and budget
 A process framework that can be tailored to specific organization or
project needs
 RUP is a methodology for delivering projects in a maximum
performance manner.
8

9. Key Aspects of RUP
 Risk-driven process
 Iterations are planned based on high priority risks
 Use-case driven development
 Use cases are used as the basis of the entire
development process
 Architecture-centric design
 Architecture is the primary artifact to
conceptualize, construct, manage, and evolve the
system
9

10. RUP 6 Best practices
 Develop Software Iteratively
 Manage Requirements
 Use Component-Based
Architecture
10

11. RUP 6 Best practices
 Visually Model Software
 Promotes consistency and unambiguous
communication of development information
 Continuously Verify Software
Quality
 Identify defects early
Control Changes to Software
 Create and release a tested baseline at the end of each
iteration
11

12. Agenda
 Terms and definitions
 What is RUP?
 Key aspect of RUP
 6 Best practices
 RUP Architecture
 Dynamic aspect
 Static Aspect
 Workers
 RUP Workflows
 Conclusion
 QA
 References
12

13. RUP Architecture
 Dynamic Structure
 Dynamic aspect deals with the lifecycle or time
dimension of a project.
 Static Structure
 How RUP elements co-work together.
 Expressed in term of core disciplines.
13

14. RUP Architecture
 Each cycle contains 4 phases
 Inception
 Elaboration
 Construction
 Transition
14
Dynamic Structure

15. RUP Architecture
15

16. Inception phase
Objective:
 Understand what to build.
 Identify key system functionality.
 A initial use-case model (10% -20%) complete.
 Determine at least one possible solution.
 One or several prototypes.
 Understand the costs, schedule, and risks of the
project.
 An initial risk assessment.
 Decide what process to follow and what tools to use.
 A project plan
This phase helps you
determine the project
feasibility , what
customer want and how
will you do that
16

17. Lifecycle Objective
Milestone
Milestone:
 Actual expenditures versus planned expenditures.
time
Inception Elaboration Construction Transition
First Major
Milestone
17

18. Elaboration phase
 Deeper Requirement
understanding
 At least 80% complete use-case
model
non functional requirements
 Architect consideration.
 A Software Architecture
Description.
 An executable prototype.
 Risk mitigation and Accurate Cost
A revised risk list and a revised business
case.
 Development Case refinement
 A development plan for the
overall project
Objectives:
The goal of the Elaboration
phase is to define and baseline
the architecture of the system
in order to provide a stable
basis for the design and
implementation effort in the
Construction phase.
18

19. Milestone : Lifecycle Architecture
 Is vision Stable?
 Is architecture stable?
This milestone tell help to determine if project plan, vision , architecture
Are good enough to achieve project goals? If not reconsider it very seriously
time
Inception Elaboration Construction Transition
Major
Milestones
19

20. Construction Phase
 Minimize development costs
 The software product integrated on the
adequate platforms.
 The user manuals.
 A description of the current release.
Construction is about cost-efficient development of a
complete product—an operational version of your system—
that can be deployed in the user community
Objectives:
20

21. Milestone : Initial Operational
Capability
 Is this product release stable and mature enough to be
deployed in the user community?
 Are actual resource expenditures versus planned
expenditures still acceptable?
time
Inception Elaboration Construction Transition
Major
Milestones
Is used to determine:
Whether the product is ready to be deployed into a beta test environment
by answering (among others) the following questions
21

22. Transition Phase
Once the product has been given to the end user, issues
usually arise that require you to develop new releases,
correct some problems, or finish the features that were
postponed.
22

23. Milestone: Product Release
 Is the user satisfied?
time
Inception Elaboration Construction Transition
Major
Milestones
23

24. Agenda
 Terms and definitions
 What is RUP?
 Key aspect of RUP
 6 Best practices
 RUP Architecture
 Dynamic aspect
 Static Aspect
 Workers
 RUP Workflows
 Conclusion
 QA
 References
24

25. Static Aspect of RUP
 A process describes who is doing what, how, and when. The
Rational Unified Process is represented using four primary
modeling elements:
 Activity (How)
 Worker (Who)
 Artifact (What)
 Workflows (when)
 Project Management
 Business Modeling
 Requirements
 Analysis and Design
 Implementation
 Test
25

26. Static Process Elements
Roles or workers (who)
Defines the person or a
team that should do
the work
Activity (how)
Describes a piece of
work a worker
performs
Artifact (what)
A piece of information
that is produced,
modified, or used by an
activity
Workflow (when)
Specifies when a set of related
activities is performed, by which
workers, producing some artifact,
which provides some observable value
to the project
26

27. Static Process Elements 27

28. Agenda
 Terms and definitions
 What is RUP?
 Key aspect of RUP
 6 Best practices
 RUP Architecture
 Dynamic aspect
 Static Aspect
 Workers
 RUP Workflows
 Conclusion
 QA
 References
28

29. Workers
29
A roles defines the behavior and
responsibilities of an individual, or a
group of individuals working
together as a team.

30. Workers
30

31. Agenda
 Terms and definitions
 What is RUP?
 Key aspect of RUP
 6 Best practices
 RUP Architecture
 Dynamic aspect
 Static Aspect
 Workers
 RUP Workflows
 Software Architecture
 RUP – The Product
 Conclusion
 QA
 References
31

32. RUP workflow
 A Workflow is a grouping of activities that are often
performed "together" to produce a specific result.
32

33. RUP workflow
 Core workflows:
 1. Business modeling workflow
 2. Requirements workflow
 3. Analysis & Design workflow
 4. Implementation workflow
 5. Test workflow
 6. Deployment workflow
33

34. Agenda
 Terms and definitions
 What is RUP?
 Key aspect of RUP
 6 Best practices
 RUP Architecture
 Dynamic aspect
 Static Aspect
 Workers
 RUP Workflows
 QA
 References
34

35. Questions
Any question?
35

36. Agenda
 Terms and definitions
 What is RUP?
 Key aspect of RUP
 6 Best practices
 RUP Architecture
 Dynamic aspect
 Static Aspect
 Workers
 RUP Workflows
 QA
 References
36

37. Agenda
[1] Iann Sommerville, software engineering
[2] Per Kroll, Philippe Kruchten, The rational unified
process made easy-a practitioner’s guide to the
RUP
[3] Rational software white paper, Rational Unified
Process
[4] http://www.slideshare.net/MasoudKalali/an-
overview-of-rup-methodology?qid=0f0370c5-
ef85-40e1-8329-
983fe9e16243&v=default&b=&from_search=2
37