The Rational Unified Process (RUP) is a favorite iterative software development process created by the Rational Software Corporation, now a division of IBM. The RUP can be an considerable refinement of the (generic) Unified Process. The RUP is not just a solitary concrete prescriptive process, but an adjustable process platform rather. It is designed to be tailored, in the sense that development organizations and software project teams will select the elements of the process that are appropriate for his or her needs. The Rational Unified Process (RUP) is also a software process product, originally developed by Rational Software, and today available from IBM.
The product carries a hyperlinked knowledge bottom with test artifacts and detailed descriptions for most different kinds of activities. RUP is roofed in the IBM Rational Method Composer (RMC) product that allows customization of the procedure. The roots of the Rational Process go to the original spiral style of Barry Boehm back. Ken Hartman, one of the key RUP contributors, collaborated with Boehm on writing and research. In 1995 Rational Software acquired the Swedish Company Objectory AB.
The Rational Unified Process was the result of the merger of the Rational Approach and the Objectory process produced by Objectory founder Ivar Jacobson. The first results of that merger was the Rational Objectory Process, made to an Objectory-like process, but ideal to wean Objectory users to the Rational Rose tool. When that goal was achieved, the real name was changed. The first version of the Rational Unified Process, version 5.0, premiered in 1998. The principle architect was Philippe Kruchten.
- 2 years back from Louisiana, USA
- There is a precise cause
- Execute the plan
- U. of Michigan: Ross
The designers and programmers of the procedure focused on diagnosing the characteristics of different failed software tasks; by doing so they tried to recognize the root factors behind these failures. They also looked at the existing software engineering processes and their solutions for these symptoms. Project failure is caused by a mixture of several symptoms, though each project fails in a unique way. The results of their research was something of software best practices they named the Rational Unified Process. THE PROCEDURE was designed with the same techniques the team used to design software; it comes with an underlying object-oriented model, using Unified Modeling Language (UML).
Given enough time it takes to develop large sophisticated software systems it is not possible to specify the problem and build the answer in a single step. Requirements will often change within a project’s development, due to architectural constraints, customer’s needs or a greater understanding of the original problem. Iteration allows the project to be successively sophisticated and addresses a project’s highest risk items as the best priority job.
Ideally each iteration ends up with an executable release – this helps reduce a project’s risk profile, allows higher comments from customers and helps designers stay concentrated. Integration is done step by step during the development process, limiting it to fewer elements. Integration is less complex, making it more cost effective.
Parts are individually designed and/or implemented and can be easily identified for later reuse. Requirement changes are noted and can be accommodated. Risks are attacked early in development since the chance is given by each iteration for more risks to be identified. Software architecture is improved by repeated scrutiny. Using iterations, a task will have one overall stage plan, but multiple iteration programs.