Unified Process

Seite 1

The Unlfled Process (UP)The Unlfled Process (UP)

What Is lt?

is an ¡terative and incremental software development framework

The most popular variations include the Rational Unified Process (RUP)

Characteristics

architecture-centríc with major work

¡s an iterative and incremental development framework

design for most coding is done

It is risk-focused

the Unified Process is built around the idea of incorporating six specific "best practice

Seite 2

Those best practices are:

Develop Software Iteratively

Manage Requirements

Use Component-based Architectures

Visually Model Software

Verify Software Quality

Control Changes to Software

History

Jacobson worked at

Rational and teamed up with Grady Booch and Jim Rumbaugh and together they spent the next

several years further developing the Objectory Process (now known as the Rational Objectory

Process) and the Unified Method (which later became UML).

IBM acquired Rational Software in 2003, and in 2005 donated the core of the Rational Process to

the Eclipse Foundation open-source community

Components of the Unlfied Process:

Cycles

Phases

Operations

Disciplines

Activlties

Artifacts

Workers

Seite 3

The disciplines are:

Business Modeling

Requirements

Analysis and Design

Implementation

Testing

Deponent

Configuration and Change Management

Project Management

Environment

The four phases are:

Inception phase

Elaboration phase

Construction phase

Translation phase

Each phase is concluded when a measurable milestone has been reached and is followed by a "go/

no-go” decision by the project team on whether to move forward with the next phase.

Seite 4

Business Modeling

focuses on efforts to understand the organlzatlon, Its processes

Analysis and Design

are highly focused in the form of UML models and Use Cases (both diagrams and descriptions).

Analysis and Design

named the Solution Analysis and Design discipline

Implementation

The Implementation discipline consists of coding, unit testing, and integration of the software.

Testing

is focused on quality assurance of the software being released in that cycle or

Iteration

Deployment

is focused on planning the deployment of, and actually deploying, the software

Seite 5

Configuration and Change Management is focused on managing change to the

project’s work products.

Project Management

is focused on standard project management activities

Environment

is focused on supporting the overall project and development efforts

through managing environmental factors.

The Phases

Inception Phase

"why" of the development effort is defined.

Stakeholder agreement on business case, scope, and project cost and schedule estimates

The final prototypes are sufficient indications of the correct future development goals

Seite 6

Elaboration Phase

Is the part of the framework when more detailed analysis and planning are undertaken to better understand the problem domain, develop a more concrete project plan, Identify and eliminate the high-risk elements.

Detailing the non-functional requirements and any requirements not related to a use case are completed

business case and risk lists have been updated

executable architecture prototype has been created and approved for use

Construction Phase

Is the part of the framework where software development, integration, and

testing takes place.

The specific activities of this phase include:

The software is built, integrated, and tested

The user manuals have been created

The software product is stable and mature enough to be deployed to end users

Stakeholders are ready to transition to the new / updated software

Seite 7

Transition Phase

The software is deployed to end users and is essentially a broad "beta" test of the application.

The transition phase can include multiple iterations of the software, including beta releases, bug fixes, and enhancements

The specific activities of this phase include:

"Beta testing“ or "user acceptance testing”

Parallel operation with legacy systems

Users and maintainers of the software are fully trained

The software is fully rolled-out

Users are satisfied with the software

Actual versus planned expenditures are still acceptable enough to move forward with the project

Seite 8

Unified Process Variations

Agile Unified Process (AUP)

is a simplified version of RUP developed by Scott Ambler. It makes a

number of changes to RUP

It adds agile techniques such as test driven development

It combines the Business Modeling, Requirements, and Analysis & Design disciplines from UP

Focus on high-value activities: possible thing that could happen to you on a project

Tool independence: You can use any toolset that you want with the Agile UP.