Rational Unified Process (RUP) Model

is an iterative software development process framework created by the Rational Software Corporation, a division of IBM since 2003.

RUP is not a single concrete prescriptive process, but rather an adaptable process framework, intended to be tailored by the development organizations and software project teams that will select the elements of the process that are appropriate for their needs.
The Rational Unified Process is also a software process product, originally developed by Rational Software, and now available from IBM. The product includes a hyperlinked knowledge base with sample artifacts and detailed descriptions for many different types of activities. RUP is included in the IBM Rational Method Composer (RMC) product which allows customization of the process.

The Unified Process was designed from the start to include both a generic, public domain process (known as the Unified Process), and a more detailed specification known as the Rational Unified Process which could be marketed as a commercial product.

four phases:
-Inception
-Elaboration
-Construction
-Transition

Done By lisui

Limitation

If the users of RUP do not understand that RUP is a process framework, they may perceive it as a weighty and expensive process. It was not intended, not envisioned and not promoted to be used straight “out of the box”. As the RUP must be customized for each project by a RUP process expert, the project’s overall success is highly dependent on the abilities of this one person.

Benefits

Rational Unified Process captures many of modern software development’ best practices to suit a wide range of project and organizations:

Develop software iteratively: Plan increments of the system based on customer priorities and develop and deliver the highest priority system features early in the development process.

Manage requirements: Explicitly document the customer’s requirements and keep track of changes to these requirements.Analyse the impact of changes on the system before accepting them.

Use component-based architecture: Structure the system architecture into components

Visually model software: Use graphical UML models to present static and dynamic views of the software.


Verify software quality: Ensure that the software meets the organizational quality standards

Control changes to software: Manage changes to the software using a change management system and configuration management procedures and tools.

Done By YiTian