The Unified Process Disciplines/Workflows

Business Modeling

The Business Modelling discipline focuses on efforts to understand the organization, its processes, and the problem domain.  The discipline focuses on understanding the following factors and how they may impact or relate to the software being considered: ^[4]

• Enterprise business rules
• Enterprise business process model
• Enterprise domain model
• Enterprise mission statement
• Enterprise vision
• Organization model

 Requirements

   The requirements discipline in RUP is like the requirements discipline in pretty much every other    software process.  The main difference is that RUP requirements are highly focused in the form of UML models and Use Cases (both diagrams and descriptions).

Analysis and Design

The requirements are analyzed from a solution design perspective, rather than a requirements analysis perspective. Specific activities that are part of this discipline include: 

• Understanding and analyzing the requirements for the system.
• Defining a candidate architecture for a system.
• Constructing a proof-of-concept or prototype to validate a candidate architecture.
• Design of components, services, and/or modules
• Design of interfaces (network, user, and databases)

       Implementation

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

Testing

The Testing discipline is focused on quality assurance of the software being released in that cycle or iteration.  It includes such activities as:

• Planning test efforts
• Creating test cases
• Running tests
• Reporting defects

Deployment

The Deployment discipline is focused on planning the deployment of, and actually deploying, the software that is being completed that cycle, phase or iteration.  It includes such activities as:

• Planning the deployment.
• Developing support and operations materials.
• Planning alpha, beta, and pilot testing efforts.
• Deploying the software.Training end users.
• Managing acceptance testing efforts

Configuration and Change Management

The Configuration and Change Management discipline is focused on track the changes and identify the current versions of the system. This includes such activities as:

• Managing change requests
• Setting up the Change Management process and environment
• Planning configuration control
• Monitoring and reporting the configuration status
• Managing baselines and releases

Project Management

The Project Management discipline is focused on standard project management activities such as:

• Managing project staff.
• Stakeholder coordination and management.
• Managing project risks.
• Project estimating, planning, and scheduling.
• Iteration planning.

Environment
The Environment discipline is focused on supporting the overall project and development efforts through managing environmental factors such as:

• Processes.
• Standards.
• Tools (hardware, software, etc.

Fig. UP Disciplines

Disciplines and Phases

The below figure illustrates the changing relative effort with respect to the phases.

Fig. Disciplines and Phases