Scribd
Upload
12 views

Unified Process model

The Unified Process (UP) is an iterative software development methodology that focuses on building object-oriented systems through a series of phases: Inception, Elaboration, Construction, and Transition. It emphasizes risk management, use case-driven requirements, and architecture-centric design, with each phase contributing to the overall development and deployment of the software. The process includes various disciplines such as business modeling, requirements analysis, design, and implementation to ensure a comprehensive approach to software development.

Uploaded by

vedaraj
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
12 views

Unified Process model

The Unified Process (UP) is an iterative software development methodology that focuses on building object-oriented systems through a series of phases: Inception, Elaboration, Construction, and Transition. It emphasizes risk management, use case-driven requirements, and architecture-centric design, with each phase contributing to the overall development and deployment of the software. The process includes various disciplines such as business modeling, requirements analysis, design, and implementation to ensure a comprehensive approach to software development.

Uploaded by

vedaraj
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 3

2. What do you mean by Unified Process? Explain the phases with suitable diagrams.

Unified Process

 A software development process describes an approach to building, deploying, and possibly


maintaining software.
 The Unified Process has emerged as a popular iterative software development process for
building object-oriented systems.
 This model is also called as Rational Unified Process or RUP.

Unified Process Characteristics

Iterative and Incremental

 In this lifecycle approach, development is organized into a series of short, fixed length (for
example, three-week) mini-projects called iterations.
 Each iteration includes its own requirements analysis, design, implementation, and testing
activities.
 Each iteration results in increment, which is a release of the system that contains added or
improved functionality compared with the previous release.

Risk-focused

 The Unified Process requires the project team to focus on addressing the most critical risks early
in the project life cycle.

Use Case Driven

 In the Unified Process, use cases are used to capture the functional requirements and to define the
contents of the iterations.

Architecture centric

 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.

Phases in the Unified Process

The Unified Process divides the project into four phases:

 Inception
 Elaboration
 Construction
 Transition

Inception Phase

Inception is the smallest phase in the project. The following are typical goals for the Inception phase.

 Approximate vision
 Business case
 Establish the Project scope
 vague estimates.

Elaboration Phase

Elaboration phase has the following objectives.

 Refined vision
 iterative implementation of the core architecture
 resolution of high risks
 identification of most requirements and scope
 More realistic estimates.

Construction

The analysis and design activities that are started in elaboration phase are completed in this phase and
source code is developed which implements all desired functionalities.

 iterative implementation of the remaining lower risk and easier elements,


 Preparation for deployment.

Transition
 In the transition phase all the activities that are required at the time of deployment of the software
product are carried out.
 Beta testing is conducted when software delivered to the end user.
 User feedback report is used to remove defects from the created system.
 Finally software team prepares user manuals, installation guides and troubleshooting procedures.
This makes the software more usable at the time of release.

The UP Disciplines

 The UP Disciplines represents the set of activities that are required for designing the software
system.
 There are several disciplines in the UP. Following are some important UP Disciplines.

Business Modeling:

A model or graphical representation is created to represent the concept in Application domain.

Requirements Analysis:

The functional and non-functional requiremets are captured in this discipline by creating some specific
type of model.

Design:

All aspects of design, including the overall architecture, objects, databases, networking, and the like.

Implementation:

This Discipline contains the source code that is created for implementing the system.

You might also like