Scribd
Upload
86 views

Rup Phan Viec

The Rational Unified Process (RUP) is a software development process originally created by Rational Software. It aims to deliver high quality products that meet customer needs. Unlike the traditional waterfall model, RUP takes an iterative approach through four phases - inception, elaboration, construction, and transition. It also utilizes six core disciplines: business modeling, requirements, analysis and design, implementation, testing, and deployment. RUP advocates best practices like adapting the process based on needs, balancing stakeholder priorities, and demonstrating value iteratively.

Uploaded by

NBKEX
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
86 views

Rup Phan Viec

The Rational Unified Process (RUP) is a software development process originally created by Rational Software. It aims to deliver high quality products that meet customer needs. Unlike the traditional waterfall model, RUP takes an iterative approach through four phases - inception, elaboration, construction, and transition. It also utilizes six core disciplines: business modeling, requirements, analysis and design, implementation, testing, and deployment. RUP advocates best practices like adapting the process based on needs, balancing stakeholder priorities, and demonstrating value iteratively.

Uploaded by

NBKEX
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 12

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 use Waterfall 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 RUP Lifecycle

The Four Phases of RUP


1.

The Inception Phase

The goal is to obtain buy-in from key stakeholders. Objective is to specify requirements in greater detail and define the architecture for the system. The focus here is to develop the application to the point where it is ready for deployment. We can now delivery the system into production.

2.

The Elaboration Phase

3.

The Construction Phase

4.

The Transition Phase

The Six Disciplines of RUP


1.

Business Modeling

The goal is to understand the business of the organization.


The goal is to define Scope: What is and is not to be built. The goal is to analyze the requirements and design the solution. The goal is to execute the code based on the design.

2.

Requirements

3.

Analysis and Design

4.

Implementation

The Six Disciplines of RUP (Cont.)


5.

Test

The goal is to verify all aspects of the system to ensure quality. The goal is plan and deliver a working system to the customer.

6.

Deployment

Best Practices of the RUP

Adapt the process

Adapt RUP appropriately based on the development needs. Take an evolutionary approach by keeping stakeholders as active participants.
Keep an open communication process Deliver working software early and regularly

Balance competing stakeholders

Collaborating Across Teams

Demonstrate Value Iteratively

Best Practices of the RUP (Cont.)

Elevate the level of Abstraction

Adapt modeling tools, reuse existing code, and focus on architecture This is done by testing at every major part of the project.

Focus continuously on Quality

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 Issues are discovered early in your project Improved control Improved risk management

References

Rational Unified Process: Best Practices for Software Development Teams

http://www.ibm.com/developerworks/rational/library/content/03 July/1000/1251/1251_bestpractices_TP026B.pdf

A Managers Introduction to the Rational Unified Process (RUP)

http://www.ambysoft.com/downloads/managersIntroToRUP.pd f http://www.menloinnovations.com/freestuff/whitepapers/Ratio nal%20Unified%20Process.pdf

The Rational Unified Process

You might also like