Unified Process

Object oriented software development process framework

The unified software development process or unified process is an iterative and incremental software development process framework. The best known and extensively documented refinement of the unified process is the rational unified process (RUP). Other examples are OpenUP and agile unified process.

The unified process is not simply a process, but rather an extensible framework which should be customized for specific organizations or projects. The rational unified process is, similarly, a customizable framework. As a result, it is often impossible to say whether a refinement of the process was derived from UP or from RUP, and so the names tend to be used interchangeably. The name unified process as opposed to rational unified process is generally used to describe the generic process, including those elements which are common to most refinements. The unified process name is also used to avoid potential issues of trademark infringement since Rational Unified Process and RUP are trademarks of IBM. The first book to describe the process was titled The Unified Software Development Process and published in 1999 by Ivar Jacobson, Grady Booch and James Rumbaugh. Since then various authors unaffiliated with Rational Software have published books and articles using the name Unified Process, whereas authors affiliated with Rational Software have favored the name Rational Unified Process. In 2012 the disciplined agile delivery framework was released, a hybrid framework that adopts and extends strategies from unified process, scrum, extreme programming, and other methods.

The unified process is an iterative and incremental development process. The elaboration, construction and transition phases are divided into a series of timeboxed iterations. (The inception phase may also be divided into iterations for a large project.) Each iteration results in an increment, which is a release of the system that contains added or improved functionality compared with the previous release. Although most iterations will include work in most of the process disciplines (e. g. requirements, design, implementation, testing) the relative effort and emphasis will change over the course of the project.

The unified process insists that architecture sits at the heart of the project team's efforts to shape the system. Since no single model is sufficient to cover all aspects of a system, the unified process supports multiple architectural models and views. One of the most important deliverables of the process is the executable architecture baseline which is created during the elaboration phase. This partial implementation of the system serves to validate the architecture and act as a foundation for remaining development.

The unified process requires the project team to focus on addressing the most critical risks early in the project life cycle. The deliverables of each iteration, especially in the elaboration phase, must be selected in order to ensure that the greatest risks are addressed first.

Use cases are the primary modeling tools to define the system functionalities. It also acts as straightforward communication means for technical and non technical team members.

Inception is the smallest phase in the project, and ideally, it should be quite short. If the inception phase is long then it may be an indication of excessive up front specification, which is contrary to the spirit of the unified process. Develop an approximate vision of the system, make the business case, define the scope, and produce a rough cost estimate and project schedule.

During the elaboration phase, the project team is expected to capture a healthy majority of the system requirements. However, the primary goals of Elaboration are to address known risk factors and to establish and validate the system architecture. Common processes undertaken in this phase include the creation of use case diagrams, conceptual diagrams (class diagrams with only basic notation) and package diagrams (architectural diagrams). The architecture is validated primarily through the implementation of an executable architecture baseline. This is a partial implementation of the system which includes the core most architecturally significant components. It is built in a series of small time boxed iterations. By the end of the elaboration phase, the system architecture must have stabilized and the executable architecture baseline must demonstrate that the architecture will support the key system functionality and exhibit the right behavior in terms of performance, scalability, and cost. The final elaboration phase deliverable is a plan (including cost and schedule estimates) for the construction phase. At this point the plan should be accurate and credible since it should be based on the elaboration phase experience and since significant risk factors should have been addressed during the elaboration phase.

Construction is the largest phase of the project. In this phase, the remainder of the system is built on the foundation laid in elaboration. System features are implemented in a series of short, time boxed iterations. Each iteration results in an executable release of the software. It is customary to write full text use cases during the construction phase and each one becomes the start of a new iteration. Common Unified Modeling Language (UML) diagrams used during this phase include activity diagrams, sequence diagrams, collaboration diagrams, state transition diagrams and interaction overview diagrams. Iterative implementation for the lower risks and easier elements are done. The final construction phase deliverable is software ready to be deployed in the transition phase.

The final project phase is transition. In this phase the system is deployed to the target users. Feedback received from an initial release (or initial releases) may result in further refinements to be incorporated over the course of several transition phase iterations. The transition phase also includes system conversions and user training.