What is RUP (rational unified process)? 

RUP stands for Rational Unified Process. Its a software development process framework which has been taken forward by Rational(part of IBM corporation)

Its a proper guidelines to be followed so to achieve standardization and improvement of the existing processes. RUP has phases and iterations which have to be followed with the help of templates and guidelines implemented at each stage. The intention of  usage of RUP is to provide standards for all stages of the software development life cycle. RUP is supported by different tools and methodologies among which is Rational's UML(Unified Modeling Language).

In the figure, the Rational Unified Process Model can be diagrammatically viewed. As depicted, RUP has four distinct project life cycle phases:

a) Inception – is the part where the actual exploration of the concept happens with the stakeholders management, definition of the project scope, cost benefit and feasibility analyses. This is the starting phase of the project and actually provides the foundation for each of the ensuing processes.

b) Elaboration – This is the phase where the project starts to take shape. The requirements are more or less frozen and the design of the system gets into its first draft.

c) Construction – This phase is the actual building phase of the project where the software takes shape and it involves the major coding part out of the four phases. Testing is also part of this phase. The first cut release of the software is the objective of the phase

d) Transition – This phase is the wrapping up of the system with the release to the client and the final support phase of the software system starts.

 RUP also has six engineering disciplines and three supporting disciplines. These nine RUP disciplines are part of each iterations required in the project life cycle. The six engineering disciplines are somewhat similar to the waterfall model phases whereas the three supporting disciplines are unique to the RUP framework.

I. RUP Engineering Disciplines

a) Business Modeling – Initial modeling of business with the analysis and scope formation

b) Requirements – gathering and communication of requirements

c) Analysis and design – analysis and formation of the solutions designs

d) Implementation – Implementing the solution

e) Test – testing the system as a whole and in units

f) Deployment – finally deploying the system at client site and going into production level

II RUP Supporting Disciplines

a) Configuration and Change Management – configuration of the versions of documents and code. Management of changes to requirements, solution and codes as required

b) Project Management – Planning, estimation, resourcing and overall managing the team and customers as part of the project

c) Environment -  Ensuring that the project team is aware of all aspects and of the RUP implementation.

Fig A – The Rational Unified Process Model

As per the Fig A , the RUP framework is depicted as a “hump chart” with the matrix showing the RUP phases and the RUP disciplines. Lets say for example, the requirement discipline is peaked at the initiation and elaboration stage after which it flattens bout does not completely disappear. Similarly project management discipline is required to be at a constant peak throughout the project and cannot flatten or lag behind in any phase.

RUP is one of the most complex software development project life cycles and involves proper project planning for the successful implementation of the system