The RUP lifecycle is an implementation of spiral development. It was created by assembling the elements in semi-ordered sequences. The life cycle organizes tasks into phases and iterations.

RUP divides the process into four phases, within which few but large and formal iterations are carried out in a variable number depending on the project. The Figure shows how the effort associated with the disciplines varies depending on the phase in which the RUP project is.

The first iterations (in the Initiation and Elaboration phases) focus on understanding the problem and technology, delimiting the scope of the project, eliminating critical risks, and establishing a baseline[2]​ of the architecture.

During the initiation phase, iterations place greater emphasis on business and requirements modeling activities.

In the elaboration phase, the iterations are oriented towards the development of the architecture baseline, they cover more the requirements workflows, business model (refinement), analysis, design and an implementation part oriented to the architecture baseline.

In the construction phase, the construction of the product is carried out through a series of iterations.

For each iteration, some Use Cases are selected, their analysis and design are refined and their implementation and testing proceed. A small cascade is made for each cycle. Iterations are carried out until the implementation of the new version of the product is completed.

In the transition phase, the aim is to guarantee that a product is ready for delivery to the user community.

As can be seen in each phase all disciplines participate, but depending on the phase the effort dedicated to a discipline varies.

• - Iterative development.

• - Requirements management.

• - Use of component-based architecture.

• - Change control.

• - Visual modeling of the software.

• - Software quality verification.

• - Aims to implement the best practices in Software Engineering, so that it adapts to any project.

The RUP is a product of Rational (IBM). It is characterized by being iterative and incremental, focused on architecture and guided by use cases.

It includes artifacts (which are the tangible products of the process such as the use case model, source code, etc.) and roles (role played by a person at a given moment; a person can play different roles throughout the process).

• - Establece oportunidad y alcance.

• - Identifica las entidades externas o actores con las que se trata.

• - Identifica los casos de uso.

RUP comprende dos aspectos importantes por los cuales se establecen las disciplinas:.

• - Proceso. Las etapas de esta sección son: (revisar nuevamente la gráfica)

• Modelado de negocio

• Requisitos

• Análisis y Diseño

• Implementación

• Pruebas

• Despliegue.

• - Soporte. En esta parte nos encontramos con las siguientes etapas:

• Gestión del cambio y configuraciones

• Gestión del proyecto

• Entorno.

La estructura dinámica de RUP es la que permite que éste sea un proceso de desarrollo fundamentalmente iterativo, y en esta parte se ven inmersas las cuatro fases descritas anteriormente:.

1. • Inicio (también llamado Incepción o Concepción).

2. • Elaboración.

3. • Desarrollo (también llamado Implementación, Construcción).

4. • Cierre (también llamado Transición).

Startup Phase

The purpose of this phase is to define and agree on the scope of the project with the sponsors or stakeholders of the project in which we have to identify the risks associated with the project, propose a very general vision of the software architecture and produce the plan for the phases and subsequent iterations.

Preparation Phase

In the elaboration phase, the use cases are selected that allow defining the base architecture of the system and they will be developed in this phase, the specification of the selected use cases is carried out and the first analysis of the problem domain is carried out, the preliminary solution is designed.

Development or Construction Phase

The purpose of this phase is to complete the functionality of the system. To do this, pending requirements must be clarified, changes must be managed according to the evaluations made by users, and improvements for the project must be made.

Transition Phase

The purpose of this phase is to ensure that the software is available to end users, fix bugs and defects found in acceptance testing, train users, and provide necessary technical support. It must be verified that the product meets the specifications delivered by the people involved in the project.

RUP en cada una de sus fases (pertenecientes a la estructura dinámica) realiza una serie de artefactos que sirven para comprender mejor tanto el análisis como el diseño del sistema (entre otros).

Estos artefactos (entre otros) son los siguientes:.

Start

• - Vision document.

• - Use case diagrams.

• - Requirements specification.

• - Requirements diagram").

Elaboration

• - Architecture document that works with the following views:

Logical view

• Class diagram

• Model E-R (If the system requires it)

Deployment view

• Sequence diagram

• State diagram

• Collaboration diagram

Conceptual view

• Domain model

Physical view

• Behavior map at the hardware level.

• - Design and development of use cases, or architectural use case flows.

• - Tests of the developed use cases, which demonstrate that the documented architecture adequately responds to functional and non-functional requirements.

Construction

• - Specification of missing requirements.

• - Design and development of use cases and/or flows according to iterative planning.

• - Testing of the developed use cases, and regression tests as appropriate.

• - if I am and if I went.

Transition

• - Final acceptance tests.

• - Put into production.

• - Stabilization.

The origins of RUP can be traced back to Barry Boehm's original spiral model. Ken Hartman, one of RUP's key contributors, collaborated with Boehm on the research. In 1995, Rational Software bought a Swedish company called Objectory AB, founded by Ivar Jacobson, famous for incorporating use cases into object-oriented development methods.

The Rational Unified Process was the result of a convergence of Rational Approach and Objectory (the process of the company Objectory AB). The first result of this merger was the Rational Objectory Process, the first version of RUP, which was put on the market in 1998, with Philippe Kruchten being the chief architect.

The first book to describe the process was titled The Unified Software Development Process[3]​.

In 2006, IBM created a subset of RUP tuned for agile development projects - published as a free method, called OpenUP through the Eclipse site "Eclipse (software)").[4]​.

On the other hand, when it comes to the methodology, it comprises three key principles: Driven by use cases, focused on architecture, iterative and incremental.

Regarding "use case driven", it means that the requirements are focused on providing value to the customer and that the process must guarantee that all development, testing, planning, documentation, etc., is aimed at meeting these customer expectations and ensuring that the value requirements are put into production.

When it comes to "architecture-centered," it means that there is an emphasis on designing quality architecture, and it is the architecture that also guides how development should be planned and done.

When it comes to "iterative and incremental", it means that the project is divided into several life cycles (called iterations) that must result in an executable. For each of the iterations, requirements are added and, above all, value to the client; For this reason it is incremental.

The RUP lifecycle is an implementation of spiral development. It was created by assembling the elements in semi-ordered sequences. The life cycle organizes tasks into phases and iterations.

RUP divides the process into four phases, within which few but large and formal iterations are carried out in a variable number depending on the project. The Figure shows how the effort associated with the disciplines varies depending on the phase in which the RUP project is.

The first iterations (in the Initiation and Elaboration phases) focus on understanding the problem and technology, delimiting the scope of the project, eliminating critical risks, and establishing a baseline[2]​ of the architecture.

During the initiation phase, iterations place greater emphasis on business and requirements modeling activities.

In the elaboration phase, the iterations are oriented towards the development of the architecture baseline, they cover more the requirements workflows, business model (refinement), analysis, design and an implementation part oriented to the architecture baseline.

In the construction phase, the construction of the product is carried out through a series of iterations.

For each iteration, some Use Cases are selected, their analysis and design are refined and their implementation and testing proceed. A small cascade is made for each cycle. Iterations are carried out until the implementation of the new version of the product is completed.

In the transition phase, the aim is to guarantee that a product is ready for delivery to the user community.

As can be seen in each phase all disciplines participate, but depending on the phase the effort dedicated to a discipline varies.

• - Iterative development.

• - Requirements management.

• - Use of component-based architecture.

• - Change control.

• - Visual modeling of the software.

• - Software quality verification.

• - Aims to implement the best practices in Software Engineering, so that it adapts to any project.

The RUP is a product of Rational (IBM). It is characterized by being iterative and incremental, focused on architecture and guided by use cases.

It includes artifacts (which are the tangible products of the process such as the use case model, source code, etc.) and roles (role played by a person at a given moment; a person can play different roles throughout the process).

• - Establece oportunidad y alcance.

• - Identifica las entidades externas o actores con las que se trata.

• - Identifica los casos de uso.

RUP comprende dos aspectos importantes por los cuales se establecen las disciplinas:.

• - Proceso. Las etapas de esta sección son: (revisar nuevamente la gráfica)

• Modelado de negocio

• Requisitos

• Análisis y Diseño

• Implementación

• Pruebas

• Despliegue.

• - Soporte. En esta parte nos encontramos con las siguientes etapas:

• Gestión del cambio y configuraciones

• Gestión del proyecto

• Entorno.

La estructura dinámica de RUP es la que permite que éste sea un proceso de desarrollo fundamentalmente iterativo, y en esta parte se ven inmersas las cuatro fases descritas anteriormente:.

1. • Inicio (también llamado Incepción o Concepción).

2. • Elaboración.

3. • Desarrollo (también llamado Implementación, Construcción).

4. • Cierre (también llamado Transición).

Startup Phase

The purpose of this phase is to define and agree on the scope of the project with the sponsors or stakeholders of the project in which we have to identify the risks associated with the project, propose a very general vision of the software architecture and produce the plan for the phases and subsequent iterations.

Preparation Phase

In the elaboration phase, the use cases are selected that allow defining the base architecture of the system and they will be developed in this phase, the specification of the selected use cases is carried out and the first analysis of the problem domain is carried out, the preliminary solution is designed.

Development or Construction Phase

The purpose of this phase is to complete the functionality of the system. To do this, pending requirements must be clarified, changes must be managed according to the evaluations made by users, and improvements for the project must be made.

Transition Phase

The purpose of this phase is to ensure that the software is available to end users, fix bugs and defects found in acceptance testing, train users, and provide necessary technical support. It must be verified that the product meets the specifications delivered by the people involved in the project.

RUP en cada una de sus fases (pertenecientes a la estructura dinámica) realiza una serie de artefactos que sirven para comprender mejor tanto el análisis como el diseño del sistema (entre otros).

Estos artefactos (entre otros) son los siguientes:.

Start

• - Vision document.

• - Use case diagrams.

• - Requirements specification.

• - Requirements diagram").

Elaboration

• - Architecture document that works with the following views:

Logical view

• Class diagram

• Model E-R (If the system requires it)

Deployment view

• Sequence diagram

• State diagram

• Collaboration diagram

Conceptual view

• Domain model

Physical view

• Behavior map at the hardware level.

• - Design and development of use cases, or architectural use case flows.

• - Tests of the developed use cases, which demonstrate that the documented architecture adequately responds to functional and non-functional requirements.

Construction

• - Specification of missing requirements.

• - Design and development of use cases and/or flows according to iterative planning.

• - Testing of the developed use cases, and regression tests as appropriate.

• - if I am and if I went.

Transition

• - Final acceptance tests.

• - Put into production.

• - Stabilization.

The origins of RUP can be traced back to Barry Boehm's original spiral model. Ken Hartman, one of RUP's key contributors, collaborated with Boehm on the research. In 1995, Rational Software bought a Swedish company called Objectory AB, founded by Ivar Jacobson, famous for incorporating use cases into object-oriented development methods.

The Rational Unified Process was the result of a convergence of Rational Approach and Objectory (the process of the company Objectory AB). The first result of this merger was the Rational Objectory Process, the first version of RUP, which was put on the market in 1998, with Philippe Kruchten being the chief architect.

The first book to describe the process was titled The Unified Software Development Process[3]​.

In 2006, IBM created a subset of RUP tuned for agile development projects - published as a free method, called OpenUP through the Eclipse site "Eclipse (software)").[4]​.

On the other hand, when it comes to the methodology, it comprises three key principles: Driven by use cases, focused on architecture, iterative and incremental.

Regarding "use case driven", it means that the requirements are focused on providing value to the customer and that the process must guarantee that all development, testing, planning, documentation, etc., is aimed at meeting these customer expectations and ensuring that the value requirements are put into production.

When it comes to "architecture-centered," it means that there is an emphasis on designing quality architecture, and it is the architecture that also guides how development should be planned and done.

When it comes to "iterative and incremental", it means that the project is divided into several life cycles (called iterations) that must result in an executable. For each of the iterations, requirements are added and, above all, value to the client; For this reason it is incremental.