Scribd
Upload
52 views15 pages

Week # 2 Lecture # 2: Object-Oriented Analysis and Design

The document provides an overview of the Rational Unified Process (RUP). RUP is a software engineering process developed by Rational Software to guide development using iterative delivery and the Unified Modeling Language. It consists of four phases - inception, elaboration, construction, and transition - and six disciplines: business modeling, requirements, analysis and design, implementation, test, and deployment. The process aims to deliver high quality software that meets customer needs by obtaining early and continual stakeholder feedback.

Uploaded by

Syeda Abrish Fatima
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
52 views15 pages

Week # 2 Lecture # 2: Object-Oriented Analysis and Design

The document provides an overview of the Rational Unified Process (RUP). RUP is a software engineering process developed by Rational Software to guide development using iterative delivery and the Unified Modeling Language. It consists of four phases - inception, elaboration, construction, and transition - and six disciplines: business modeling, requirements, analysis and design, implementation, test, and deployment. The process aims to deliver high quality software that meets customer needs by obtaining early and continual stakeholder feedback.

Uploaded by

Syeda Abrish Fatima
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 15

Week # 2

Lecture # 2
Object-Oriented Analysis and Design

Presented by:
Kanwal Kiani
AN OVERVIEW OF THE
RATIONAL UNIFIED
PROCESS (RUP)

Eric Villagomez
TS5130 - System Development Theory and Practice
What is RUP?
 RUP was originally developed by
Rational Software (now part of IBM).
 It is a Software engineering process It is a
 process product
 It enhances team productivity
 It creates and maintains models
 It is a guide to effectively use the Unified
Modeling Language
 Its goal is to delivery a high quality product
that the customer actually wants.
Why not useWaterfall instead?

 The Waterfall method follows a sequential


approach to software development.
 This limits the ability to react to any change or
correct problems in a timely matter.
Assumptions:
 Requirements never change.
 All information is known upfront.
 The customer will be satisfied with the end
 results. Technology will not change when it
comes time to integrate.
The RUPLifecycle
The Four Phases of RUP

1. The Inception Phase


 The goal is to obtain buy-in from key stakeholders.
2. The Elaboration Phase
 Objective is to specify requirements in greater
detail and define the architecture for the system.
3. The Construction Phase
 The focus here is to develop the application to the
point where it is ready for deployment.
4. The Transition Phase
 We can now delivery the system into production.
The Six Disciplines of RUP
1. Business Modeling
  The goal is to understand the business of the
organization.
2. Requirements
  The goal is to define Scope: What is and is not to
be built.
3. Analysis and Design
  The goal is to analyze the requirements and
design the solution.
4. Implementation
 The goal is to execute the code based on the
design.
The Six Disciplines of RUP(Cont.)
1. Test
 The goal is to verify all aspects of the system
to ensure quality.
2. Deployment
 The goal is plan and deliver a working system
to the customer.
Best Practices of the RUP
 Adapt the process
 Adapt RUP appropriately based on the
development needs.
Balance competing stakeholders
 Take an evolutionary approach by
keeping stakeholders as active
participants.
Collaborating Across Teams
 Keep an open communication process

 Demonstrate Value Iteratively


 Deliver working software early and regularly
Best Practices of the RUP(Cont.)

 Elevate the level of Abstraction


 Adapt modeling tools, reuse existing code, and
focus on architecture
Focus continuously on Quality
 This is done by testing at every major part
of the project.
Disadvantages of RUP
 The process may be too complex to implement
 Development can get out of control
 It is a heavyweight process
 You need an expert to fully adopt this process
Advantages of RUP
 Regular feedback from and to stakeholders
 Efficient use of resources
 You deliver exactly what the customer wants
 Issuesare discovered early in your project
 Improved control
 Improved risk management
UP Vs. RUP
UP RUP
The full form is Unified Process. The full form is Rational Unified
Process.

It is a use-case driven, incremental Here the product is process and


development process framework that marketed by Rational Software
leverages the UML. Corporation.

Used for software systems of large Here the software systems are build
and small scale across different with all the details including templates
organizational cultures. and tools.

It is process framework to execute


projects but not all the details are
required.

13
References
 Rational Unified Process: Best Practices for Software
Development Teams

http://www.ibm.com/developerworks/rational/library/content/03Ju

A Manager’s Introduction to the Rational Unified Process
(RUP)

 http://www.ambysoft.com/downloads/managersIntroToRUP.pdf

The Rational Unified Process



http://www.menloinnovations.com/freestuff/whitepapers/Rational
%
The End

15

You might also like