IBM Rational Unified Process

The Rational Unified Action (RUP) is an accepted software development action framework created by the Rational Software Corporation, a analysis of IBM back 2003.1 RUP is not a individual accurate accepted process, but rather an adjustable action framework, advised to be 

History

The Rational Unified Action (RUP) is a software action product, originally developed by Rational Software, which was acquired by IBM in February 2003. The artefact includes a aggressive affiliated ability abject with sample artifacts and abundant descriptions for abounding altered types of activities. RUP is included in the IBM Rational Method Composer (RM C) artefact which allows customization of the process. Combining the acquaintance abject of companies led to the supply of six best practices for avant-garde software engineering:

Develop iteratively, with accident as the primary abundance driver2

Manage requirements

Employ a component-based architecture

Model software visually

Continuously verify quality

Control changes

These best practices both collection the development of Rational's products, and were acclimated by Rational's acreage teams to advice barter advance the superior and adequation of their software development efforts. To accomplish this ability added accessible, Philippe Kruchten, a Rational techrep, was tasked with the accumulation of an absolute action framework for avant-garde software engineering. This accomplishment active the HTML-based action supply apparatus developed by Objectory. The consistent "Rational Unified Process" (RUP) completed a cardinal tripod for Rational:

a tailorable action that guided development

tools that automatic the appliance of that process

services that accelerated acceptance of both the action and the tools.

RUP was created in 1996 if Rational acquired the Objectory Action that had been accounting by Ivar Jacobson.

The aboriginal adaptation congenital mostly agreeable from Jim Rumbaugh's Object Clay Technology (OMT) access to modeling, Grady Booch's Booch access and UML 1.0.

In 1997, Requirements and Test conduct were added to the approach.

In 1998, they added two new disciplines: business modeling, abundant of which had already been in the Objectory Action and a Configuration and Change Management discipline. They aswell added added techniques including achievement testing, UI Design, abstracts engineering and adapted RUP to UML 1.1.

In 1999, they added a Project Management conduct and added techniques for absolute time software development. They aswell adapted RUP to UML 1.3

From 2000 on, a lot of of the modifications were about abacus techniques, abacus "tool mentors" with footfall by footfall guides to application Rational accoutrement and in automating the customization of RUP in a way that would acquiesce barter to adapt their version, but still absorb improvements in consecutive releases from Rational.

Rational Unified Process topics

RUP architecture blocks

RUP is based on a set of architecture blocks, or agreeable elements, anecdotic what is to be produced, the all-important abilities appropriate and the step-by-step account anecdotic how specific development goals are to be achieved. The capital architecture blocks, or agreeable elements, are the following:

Roles (who) – A Role defines a set of accompanying skills, competencies and responsibilities.

Work Products (what) – A Plan Product represents something consistent from a task, including all the abstracts and models produced while alive through the process.

Tasks (how) – A Assignment describes a assemblage of plan assigned to a Role that provides a allusive result.

Within anniversary iteration, the tasks are categorized into nine disciplines:

Six "engineering disciplines"

Business Modeling

Requirements

Analysis and Design

Implementation

Test

Deployment

Three acknowledging disciplines

Configuration and Change Management

Project Management

Environment

Four Project Life cycle Phases

The RUP has bent a activity activity aeon consisting of four phases. These phases acquiesce the action to be presented at a top akin in a agnate way to how a 'waterfall'-styled activity ability be presented, although in aspect the key to the action lies in the iterations of development that lie aural all of the phases. Also, anniversary appearance has one key cold and anniversary at the end that denotes the cold getting accomplished. The decision of RUP phases and disciplines over time is referred to as the RUP bulge chart.

editInception Phase

The primary cold is to ambit the arrangement abundantly as a base for acceptance antecedent costing and budgets. In this appearance the business case which includes business context, success factors (expected revenue, bazaar recognition, etc.), and banking anticipation is established. To accompaniment the business case, a basal use case model, activity plan, antecedent accident appraisal and activity description (the amount activity requirements, constraints and key features) are generated. Afterwards these are completed, the activity is arrested adjoin the afterward criteria:

Stakeholder accedence on ambit analogue and cost/schedule estimates.

Requirements compassionate as apparent by the allegiance of the primary use cases.

Credibility of the cost/schedule estimates, priorities, risks, and development process.

Depth and across of any architectural ancestor that was developed.

Establishing a baseline by which to analyze absolute expenditures against planned expenditures.

If the activity does not canyon this milestone, alleged the Lifecycle Cold Milestone, it either can be annulled or again afterwards getting redesigned to bigger accommodated the criteria.

Elaboration Phase

The primary cold is to abate the key accident items articular by assay up to the end of this phase. The addition appearance is area the activity starts to yield shape. In this appearance the botheration area assay is fabricated and the architectonics of the activity gets its basal form.

The aftereffect of the addition appearance is:

A use-case archetypal in which the use-cases and the actors accept been articular and a lot of of the use-case descriptions are developed. The use-case archetypal should be 80% complete.

A description of the software architectonics in a software arrangement development process.

An executable architectonics that realizes architecturally cogent use cases.

Business case and accident account which are revised.

A development plan for the all-embracing project.

Prototypes that demonstrably abate anniversary articular abstruse risk.

A basic user chiral (optional)

This appearance have to canyon the Lifecycle Architectonics Anniversary belief answering the afterward questions:

Is the eyes of the artefact stable?

Is the architectonics stable?

Does the executable affirmation announce that above accident elements are addressed and resolved?

Is the architectonics appearance plan abundantly abundant and accurate?

Do all stakeholders accede that the accepted eyes can be accomplished application accepted plan in the ambience of the accepted architecture?

Is the absolute vs. planned ability amount acceptable?

If the activity cannot canyon this milestone, there is still time for it to be annulled or redesigned. However, afterwards abrogation this phase, the activity transitions into a high-risk operation area changes are abundant added difficult and adverse if made.

The key area assay for the addition is the arrangement architecture.

editConstruction Phase

The primary cold is to body the software system. In this phase, the capital focus is on the development of apparatus and added appearance of the system. This is the appearance if the aggregate of the coding takes place. In beyond projects, several architectonics iterations may be developed in an accomplishment to bisect the use cases into acquiescent segments that aftermath ascertainable prototypes.

This appearance produces the aboriginal alien absolution of the software. Its cessation is apparent by the Initial Operational Capability Milestone.

editTransition Phase

The primary cold is to 'transit' the arrangement from development into production, authoritative it accessible to and accepted by the end user. The activities of this appearance cover training the end users and maintainers and beta testing the arrangement to validate it adjoin the end users' expectations. The artefact is aswell arrested adjoin the superior akin set in the Inception phase.

If all objectives are met, the Artefact Absolution Anniversary is accomplished and the development aeon is finished.

The IBM Rational Method Composer product

ICONIX is a software development alignment which predates both the Rational Unified Action (RUP), Extreme Programming (XP) and Agile software development. Like RUP, the ICONIX action is UML Use Case apprenticed but added failing than RUP. Unlike the XP and Agile approaches, ICONIX provides acceptable claim and architecture documentation, but after assay paralysis. The ICONIX Action uses alone four UML based diagrams in a four footfall action that turns use case argument into alive code.

A arch acumen of ICONIX is its use of robustness analysis, a adjustment for bridging the gap amid assay and design. Robustness assay reduces the ambiguity in use case descriptions, by ensuring that they are accounting in the ambience of an accompanying area model. This action makes the use cases abundant easier to design, assay and estimate.

The ICONIX Action is declared in the book Use Case Apprenticed Object Clay with UML: Theory and Practice1.

Essentially, the ICONIX Action describes the amount "logical" assay and architecture clay process. However, the action can be acclimated after abundant dressmaking on projects that chase altered activity management.