Rational unified process
1 / 17

Rational Unified Process - PowerPoint PPT Presentation

  • Uploaded on

Rational Unified Process. What is Ration Unified Process?. The Rational Unified Process is a Software Engineering Process. Provides a disciplined approach to assigning tasks and responsibilities within a development organization.

I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
Download Presentation

PowerPoint Slideshow about ' Rational Unified Process' - hada

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.

- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

What is ration unified process
What is Ration Unified Process?

  • The Rational Unified Process is a Software Engineering Process.

  • Provides a disciplined approach to assigning tasks and responsibilities within a development organization.

  • Is the production of high-quality software that meets the needs of its users.

How it was formed
How it was formed

  • Updated version of a process called Rational Objectory Process

  • Rational Objectory process combined the rational approach and objectory process.

  • First process to use the Unified Modeling Language (UML)

Rational unified process phases
Rational Unified Process Phases

  • Inception Phase

  • Elaboration Phase

  • Construction Phase

  • Transition Phase

Inception phase
Inception Phase

This phase is where you establish the business case for the system and delimit the project scope.

Elaboration Phase

  • This phase is where you analyse the problem domain, establish a sound architectural foundation, develop the project plan and eliminate the highest risk elements of the project.

Construction phase
Construction Phase

This phase involves all remaining components and application features are developed and integrated in the product, and all features are thoroughly tested.

Transition Phase

This phase is the transition of the developed product to the user community. This phase is only entered when a usable subset of the system is completed to an acceptable quality level.


  • Each phase can be broken down into iterations.

  • An iteration is a complete development loop resulting in a release of and executable Product.

  • Project can grow from iteration to iteration to become the final product.

6 best practices
6 Best Practices

  • Develop Software Iteratively

    Allows an increased understanding of the problem through successive refinements.

  • Manage Requirements

    Being well organised and making sure the requirement of the system meet the end- users needs.

  • Use Component-Based Architectures

    This is early development and baselining of an executable architecture.

  • Visually Model Software

    Uses a visual model of the software to capture the structure and behaviour of architectures and components.

  • Verify Software Quality

    Built-in to the rational unified process to review quality in different elements of the system, i.e. Reliability.

  • Control Changes to Software

    Establishing secure workspaces for each developer by isolating the changes made in other workspaces, and controlling changes of all software artifacts.


  • Emphasis on accurate documentation.

  • Able to resolve the project risks associated with the client's evolving requirements requiring careful change request management.

  • Less time is required for integration as the process of integration goes on throughout the software development life cycle.

  • The development time required is less due to reuse of components.


  • Team members need to be expert in their field.

  • The development process can be too complex and disorganized.

  • Cutting edge projects which utilise new technology, the reuse of components will not be possible.

  • Integration throughout the process of software development, in theory sounds a good thing. But on big projects with multiple development streams it will only add to the confusion and cause more issues during the stages of testing.

Suitable for system administration
Suitable for system administration?

This process is highly suited to a system administration project because, no matter how big or small the project is, this process helps ensure a high quality product.

Suitable for network administration
Suitable for Network Administration

  • This process would not be good for a Network administration project. This is because these types of projects usually don’t require software to be made.


  • http://www.wittmannclan.de/ptr/cs/rup_model.jpg

  • http://www.devarticles.com/images/thetenessofrup_1.jpg

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

  • http://www.my-project-management-expert.com/the-advantages-and-disadvantages-of-rup-software-development.html