SlideShare a Scribd company logo
Rational Unified Process (RUP)
Gang of 3 - Booch, Rumbaugh, Jacobsen
RUP is an iterative process product framework created by
Rational Software Corporation, acquired by IBM in 2003
Product development process based on Object Oriented
Model
Iterative, Incremental and Architecture centric.
1
RUP ....
• Implementation of Best Practices
• RUP is a configurable process
• It is supported by tool which automate the process and are used to
maintain Artifacts.
• Represent the effective usage of UML
2
Best Practices
1. Iterative Development
 Increasing understanding of requirements with
passage of time and iterations.
 Address highest risk early in the lifecycle.
 Each iteration end with an executable release so
team members stay focused on producing results.
3
2. Manage Requirements.
Describes how to elicit, organize, and document required
functionality and constraints.
Utilize Use Case to capture requirements
Driving force behind design and software test.
They provide coherent and traceable threads through both the
development and the delivered system
4
3. Component-based Architectures
Components represents subsystems which fulfils a clear
function.
Components can be developed and tested isolated
RUP provides a systematic approach to defining an
architecture using new and existing components.
Components can be purchased.
5
Example – Component diagram of UML
6
4. Visually Model Software
RUP use UML to visually model software to capture
the structure and behavior of architectures and
components.
Visual abstraction helps in better understanding the
different components of the software.
It provide blue print for software construction.
7
5. Verify Software Quality
• UML assist in ensuring the software quality by building quality
assessment into the process.
• Deliverable produced at the end of each iteration as per UML
notation ensure objective measurement of quality criteria.
8
6. Change Control Management
The process describes how to control, track and monitor changes
to enable successful iterative development.
Establish secure workspace for developers by isolating it from
change.
Identify build management.
9
7. Tool Support
10
Process Overview
11
Inception Phase
Identify project vision delimiting the project
scope.
Identify actors and develop initial use case.
(20-30% complete)
Credibility of estimates and development
process is established.
Develop Lifecycle objective as milestone.
12
Elaboration Phase
Corresponds to the transition from a low-risk operation
to a high-cost, high-risk operation with substantial
inertia.
Analyze the problem domain and establish solid
architectural foundation.
Establish use case model – 80% complete.
Provide Software Architecture description.
13
Construction Phase
During the construction phase, all remaining components and
application features are developed and integrated into
the product, and all features are thoroughly tested.
User Manuals.
14
Transition Phase
Release the product to limited user community for early
feedback.
Beta-Testing against user expectations.
UAT and deployment after certain level of stableness.
Rollout software to marketing and sales team.
Product release as “Milestone”.
15
Static Structure of the Process
A process describes who is doing what, how,
and when.
Four Elements
Workers, the ‘who’
Activities, the ‘how’
Artifacts, the ‘what’
Workflows, the ‘when’
16
17
Worker
18
Artifact
An artifact is a piece of information that is produced, modified, or used by a
process.
Artifacts are used as input by workers to
perform an activity.
A model, such as the Use-Case Model or the
Design Model
19
Work Flows
A workflow is a sequence of activities that produces a
result of observable value.
In UML terms, a workflow can be expressed as a
sequence diagram, a collaboration diagram, or an
activity diagram.
20
Work Flow Example
21
22
Workflow Name UML Diagram
Business Modelling Business Object Model
Requirement Use Case Model
Analysis and Design Activity and sequential
diagrams, Classes and
Packages
Implementation Classes and Objects
Test Iterative Testing
Deployment Deployment Diagram

More Related Content

PPTX
Rup
PPT
A Comparative study of Rational Unified process( RUP ), Agile & Microsoft Fra...
PPTX
Rational Unified Process by Vincent Prince Mutimbanyoka
PPTX
Software project scheduling
PPT
RUP VS RAD Methodology
PPT
An Overview of RUP methodology
PPT
Use of RUP for Small Projects
Rup
A Comparative study of Rational Unified process( RUP ), Agile & Microsoft Fra...
Rational Unified Process by Vincent Prince Mutimbanyoka
Software project scheduling
RUP VS RAD Methodology
An Overview of RUP methodology
Use of RUP for Small Projects

What's hot (20)

PPTX
Rational unified process (rup)
PPTX
The ultimate guide to release management process
PPTX
Testing throughout the software life cycle (software development models)
ZIP
Unified Process
PPTX
RUP - Rational Unified Process
PDF
Software lifecycle model report
PPT
Rational Unified Process(Rup)
DOCX
The unified process
PPTX
Testing Throughout The Software Life Cycle
PPTX
Systems Development Lifecycle Walkthrough (Cambridge Technical Level 3 IT)
PPTX
SDLC
PPT
PDF
Traditional Process Models
PPTX
System models of sdlc- v model
PPTX
Software development life cycle Construction phase
PPTX
System Development Life Cycle
PPTX
Software Engineering Methodology
DOCX
Software engineering model
Rational unified process (rup)
The ultimate guide to release management process
Testing throughout the software life cycle (software development models)
Unified Process
RUP - Rational Unified Process
Software lifecycle model report
Rational Unified Process(Rup)
The unified process
Testing Throughout The Software Life Cycle
Systems Development Lifecycle Walkthrough (Cambridge Technical Level 3 IT)
SDLC
Traditional Process Models
System models of sdlc- v model
Software development life cycle Construction phase
System Development Life Cycle
Software Engineering Methodology
Software engineering model
Ad

Similar to Lec_Rational Unified Process (20)

PPTX
CH02_Software_development_life_cycle (1).pptx
PDF
SE18_Lec 03_ RUP
PPTX
vnd.openxmlformats-officedocument.presentationml.presentation&rendition=1.pptx
PPT
Difference Unified Processes
PPTX
Software development models
PPT
Software Development Life Cycle (SDLC)
PDF
Testing Through the Software Development Life Cycle_ A Key to Mobile App Succ...
PPT
ISE_Lecture Week 2-SW Process Models.ppt
PPTX
Materi Testing dan Implementasi System
PPT
Software models
PPTX
Testing Throughout The Software Life Cycle II (Dhea Frizky)
PPTX
Testing Throughout the Software Life Cycle part.2 - Andika Dwi Ary Candra
DOCX
software engineering
PPTX
SDLC and Software Process Models
PPT
Rational unified process lecture-5
PPT
Software Development Life Cycle Part II
PPT
Presentation - Rational Unified Process
PPT
Lecture 1-4.ppt Introduction to Software Engineering: The evolving role of so...
PDF
Testing Through the Software Development Life Cycle_ A Key to Mobile App Succ...
CH02_Software_development_life_cycle (1).pptx
SE18_Lec 03_ RUP
vnd.openxmlformats-officedocument.presentationml.presentation&rendition=1.pptx
Difference Unified Processes
Software development models
Software Development Life Cycle (SDLC)
Testing Through the Software Development Life Cycle_ A Key to Mobile App Succ...
ISE_Lecture Week 2-SW Process Models.ppt
Materi Testing dan Implementasi System
Software models
Testing Throughout The Software Life Cycle II (Dhea Frizky)
Testing Throughout the Software Life Cycle part.2 - Andika Dwi Ary Candra
software engineering
SDLC and Software Process Models
Rational unified process lecture-5
Software Development Life Cycle Part II
Presentation - Rational Unified Process
Lecture 1-4.ppt Introduction to Software Engineering: The evolving role of so...
Testing Through the Software Development Life Cycle_ A Key to Mobile App Succ...
Ad

Recently uploaded (20)

PPTX
history of c programming in notes for students .pptx
PPTX
L1 - Introduction to python Backend.pptx
PDF
Nekopoi APK 2025 free lastest update
PDF
Design an Analysis of Algorithms I-SECS-1021-03
PDF
Upgrade and Innovation Strategies for SAP ERP Customers
PDF
Odoo Companies in India – Driving Business Transformation.pdf
PPTX
ManageIQ - Sprint 268 Review - Slide Deck
PDF
System and Network Administration Chapter 2
PPTX
Agentic AI Use Case- Contract Lifecycle Management (CLM).pptx
PDF
Why TechBuilder is the Future of Pickup and Delivery App Development (1).pdf
PPTX
CHAPTER 12 - CYBER SECURITY AND FUTURE SKILLS (1) (1).pptx
PDF
How to Migrate SBCGlobal Email to Yahoo Easily
PPTX
Operating system designcfffgfgggggggvggggggggg
PDF
How to Choose the Right IT Partner for Your Business in Malaysia
PPTX
Introduction to Artificial Intelligence
PDF
Internet Downloader Manager (IDM) Crack 6.42 Build 42 Updates Latest 2025
PDF
Claude Code: Everyone is a 10x Developer - A Comprehensive AI-Powered CLI Tool
PPTX
ISO 45001 Occupational Health and Safety Management System
PDF
Which alternative to Crystal Reports is best for small or large businesses.pdf
PDF
top salesforce developer skills in 2025.pdf
history of c programming in notes for students .pptx
L1 - Introduction to python Backend.pptx
Nekopoi APK 2025 free lastest update
Design an Analysis of Algorithms I-SECS-1021-03
Upgrade and Innovation Strategies for SAP ERP Customers
Odoo Companies in India – Driving Business Transformation.pdf
ManageIQ - Sprint 268 Review - Slide Deck
System and Network Administration Chapter 2
Agentic AI Use Case- Contract Lifecycle Management (CLM).pptx
Why TechBuilder is the Future of Pickup and Delivery App Development (1).pdf
CHAPTER 12 - CYBER SECURITY AND FUTURE SKILLS (1) (1).pptx
How to Migrate SBCGlobal Email to Yahoo Easily
Operating system designcfffgfgggggggvggggggggg
How to Choose the Right IT Partner for Your Business in Malaysia
Introduction to Artificial Intelligence
Internet Downloader Manager (IDM) Crack 6.42 Build 42 Updates Latest 2025
Claude Code: Everyone is a 10x Developer - A Comprehensive AI-Powered CLI Tool
ISO 45001 Occupational Health and Safety Management System
Which alternative to Crystal Reports is best for small or large businesses.pdf
top salesforce developer skills in 2025.pdf

Lec_Rational Unified Process

  • 1. Rational Unified Process (RUP) Gang of 3 - Booch, Rumbaugh, Jacobsen RUP is an iterative process product framework created by Rational Software Corporation, acquired by IBM in 2003 Product development process based on Object Oriented Model Iterative, Incremental and Architecture centric. 1
  • 2. RUP .... • Implementation of Best Practices • RUP is a configurable process • It is supported by tool which automate the process and are used to maintain Artifacts. • Represent the effective usage of UML 2
  • 3. Best Practices 1. Iterative Development  Increasing understanding of requirements with passage of time and iterations.  Address highest risk early in the lifecycle.  Each iteration end with an executable release so team members stay focused on producing results. 3
  • 4. 2. Manage Requirements. Describes how to elicit, organize, and document required functionality and constraints. Utilize Use Case to capture requirements Driving force behind design and software test. They provide coherent and traceable threads through both the development and the delivered system 4
  • 5. 3. Component-based Architectures Components represents subsystems which fulfils a clear function. Components can be developed and tested isolated RUP provides a systematic approach to defining an architecture using new and existing components. Components can be purchased. 5
  • 6. Example – Component diagram of UML 6
  • 7. 4. Visually Model Software RUP use UML to visually model software to capture the structure and behavior of architectures and components. Visual abstraction helps in better understanding the different components of the software. It provide blue print for software construction. 7
  • 8. 5. Verify Software Quality • UML assist in ensuring the software quality by building quality assessment into the process. • Deliverable produced at the end of each iteration as per UML notation ensure objective measurement of quality criteria. 8
  • 9. 6. Change Control Management The process describes how to control, track and monitor changes to enable successful iterative development. Establish secure workspace for developers by isolating it from change. Identify build management. 9
  • 12. Inception Phase Identify project vision delimiting the project scope. Identify actors and develop initial use case. (20-30% complete) Credibility of estimates and development process is established. Develop Lifecycle objective as milestone. 12
  • 13. Elaboration Phase Corresponds to the transition from a low-risk operation to a high-cost, high-risk operation with substantial inertia. Analyze the problem domain and establish solid architectural foundation. Establish use case model – 80% complete. Provide Software Architecture description. 13
  • 14. Construction Phase During the construction phase, all remaining components and application features are developed and integrated into the product, and all features are thoroughly tested. User Manuals. 14
  • 15. Transition Phase Release the product to limited user community for early feedback. Beta-Testing against user expectations. UAT and deployment after certain level of stableness. Rollout software to marketing and sales team. Product release as “Milestone”. 15
  • 16. Static Structure of the Process A process describes who is doing what, how, and when. Four Elements Workers, the ‘who’ Activities, the ‘how’ Artifacts, the ‘what’ Workflows, the ‘when’ 16
  • 17. 17
  • 19. Artifact An artifact is a piece of information that is produced, modified, or used by a process. Artifacts are used as input by workers to perform an activity. A model, such as the Use-Case Model or the Design Model 19
  • 20. Work Flows A workflow is a sequence of activities that produces a result of observable value. In UML terms, a workflow can be expressed as a sequence diagram, a collaboration diagram, or an activity diagram. 20
  • 22. 22 Workflow Name UML Diagram Business Modelling Business Object Model Requirement Use Case Model Analysis and Design Activity and sequential diagrams, Classes and Packages Implementation Classes and Objects Test Iterative Testing Deployment Deployment Diagram

Editor's Notes

  • #2: 01.14-01.19,01.19-01.45,02.29-02.33,02.50-02.57
  • #3: 03.22-03.26,05.42-05.47,06.34-06.54,07.10-07.20
  • #4: 07.50-07.54,08.00-08.08,08.12-08.18,08.40-08.54
  • #5: 09.24-09.30,09.34-09.39,09.42,10.32-10.38,10.46-11.12
  • #6: 11.48-12.12,12.50-12.57,15.32-15.48 Example of microsoft 13.07
  • #7: 15.52-16,30
  • #8: 16.32-16.39,16.43-16.56,17.10-17.19,17.25-17.36
  • #9: 17.40-17.45,17.49-17.56,18.44-18.57
  • #10: 19.07-19.16,19.16-19.31,20.19-20.33,21.08-21.22
  • #11: 22.33-23.19
  • #12: 23.33-23.56,24.21-24.29,25.19-25.35,25.53-25.58,26.22-26.34,26.42-26.56
  • #13: 27.09-27.21,27.49-28.01,28.09-28.18,28.24-28.36
  • #14: 28.57-29.05,29.35-29.51
  • #15: 31.26-31.42,31.45-31.52
  • #16: 32.21-32.32,32.54-33.00,33.16-33.22,34.42-34.50,36.58-37.04
  • #17: 37.32-37.45,38.09-38.13,38.17-38.21,38.55-38.58,39.22-39.26
  • #18: 39.56-40.25,40.34-41.03
  • #19: 41.55- 42.10,42.35-43.45
  • #20: 44.29-44.45,45.08-45.13,45.19-45.23,
  • #21: 46.02-46.10,47.48-47.57
  • #22: 48.02-48.48
  • #23: 1.52.58-1.53.12,1.53.26-1.53.34,1.54.12,1.54.36-1.54.58,1.55.28-1.55.27,1.56.05-1.56.15