Open In App

RUP and its Phases

Last Updated : 13 Jun, 2022
Like Article

Rational Unified Process (RUP) is a software development process for object-oriented models. It is also known as the Unified Process Model. It is created by Rational corporation and is designed and documented using UML (Unified Modeling Language). This process is included in IBM Rational Method Composer (RMC) product. IBM (International Business Machine Corporation) allows us to customize, design, and personalize the unified process. RUP is proposed by Ivar Jacobson, Grady Bootch, and James Rambaugh. Some characteristics of RUP include use-case driven, Iterative (repetition of the process), and Incremental (increase in value) by nature, delivered online using web technology, can be customized or tailored in modular and electronic form, etc. RUP reduces unexpected development costs and prevents wastage of resources. 

Phases of RUP: There is total of five phases of the life cycle of RUP:

  1. Inception –
    • Communication and planning are the main ones.
    • Identifies the scope of the project using a use-case model allowing managers to estimate costs and time required.
    • Customers’ requirements are identified and then it becomes easy to make a plan for the project.
    • The project plan, Project goal, risks, use-case model, and Project description, are made.
    • The project is checked against the milestone criteria and if it couldn’t pass these criteria then the project can be either canceled or redesigned.
  2. Elaboration –
    • Planning and modeling are the main ones.
    • A detailed evaluation and development plan is carried out and diminishes the risks.
    • Revise or redefine the use-case model (approx. 80%), business case, and risks.
    • Again, checked against milestone criteria and if it couldn’t pass these criteria then again project can be canceled or redesigned.
    • Executable architecture baseline.
  3. Construction –
    • The project is developed and completed.
    • System or source code is created and then testing is done.
    • Coding takes place.
  4. Transition –
    • The final project is released to the public.
    • Transit the project from development into production.
    • Update project documentation.
    • Beta testing is conducted.
    • Defects are removed from the project based on feedback from the public.
  5. Production –
    • The final phase of the model.
    • The project is maintained and updated accordingly.


  1. It provides good documentation, it completes the process in itself.
  2. It provides risk-management support.
  3. It reuses the components, and hence total time duration is less.
  4. Good online support is available in the form of tutorials and training.


  1. Team of expert professional is required, as the process is complex.
  2. Complex and not properly organized process.
  3. More dependency on risk management.
  4. Hard to integrate again and again.

Like Article
Suggest improvement
Share your thoughts in the comments

Similar Reads