SOFTWARE ENGINEERING 1

Introduction

SOFTWARE ENGINEERING 2
 RUP
 The Rational Unified Process (RUP) is
an iterative software development
process framework created by the Rational
Software Corporation, a division of IBM since
2003.
 The Rational Unified Process (RUP) is a software
development and project management process
that provides a disciplined and methodical
approach towards assigning tasks and
responsibilities in a team.
 Developed by Rational Software, it is used to
build complex systems and covers the entire
software development lifeENGINEERING
SOFTWARE cycle (SDLC).. 3
 Unified process (UP) is an
architecture-centric, use-case
driven, iterative and incremental
development process.
 UP is also referred to as the unified
software development process.

SOFTWARE ENGINEERING 4
 Rational Unified Process (RUP)?
 A Rational Unified Process is an approach for software
engineering for delegating activities and responsibilities
inside a software development organization.
 Its primary purpose is to enable the creation of high-quality
software that satisfies the end user’s requirements within a
predictable budget and timeframe.
 RUP is a systematic way to allocate tasks and responsibilities
within a development team that offers best practices and
guidelines for effective software development.
 By doing so, it is able to produce high-quality software on
time and within budget while satisfying the demands of its
customers.

SOFTWARE ENGINEERING 5
What are the Key Principles of RUP?
 Iterative and incremental development: RUP
emphasizes iterations, or cycles, of work, rather than
trying to complete all work upfront.
 Strong focus on requirements: RUP puts strong
emphasis on requirements gathering and management.
 Architecture-centric development: RUP takes an
architecture-centric approach, meaning that the
software’s overall design is created first before any
code is written.
 Architecture-centric development: RUP takes an
architecture-centric approach, meaning that the
software’s overall design is created first before any
code is written.
SOFTWARE ENGINEERING 6
Software…
Phases of the Unified Process
This process divides the development
process into five phases:
  Inception

  Elaboration

  Construction

  Transition

  Production

SOFTWARE ENGINEERING 7
SOFTWARE ENGINEERING 8
Software…

SOFTWARE ENGINEERING 9
Software…

SOFTWARE ENGINEERING 10
 inception phase
 The inception phase of the UP
encompasses both customer
communication and planning activities.
 By collaborating with stakeholders,
business requirements for the software
are identified;
 a rough architecture for the system is
proposed; and
 a plan for the iterative, incremental
nature of the ensuing project is developed

SOFTWARE ENGINEERING 11
 Elaboration phase
 The elaboration phase encompasses the
communication and modeling activities of the
generic process model.
 Elaboration refines and expands the preliminary
use cases that were developed as part of the
inception phase and expands the architectural
representation to include five different views of
the software—the use case model, the
requirements model, the design model, the
implementation model, and the deployment
model.
 Elaboration creates an “executable architectural
baseline” that represents a “first cut”
executable system.SOFTWARE ENGINEERING 12
 construction phase
 The construction phase of the UP is identical
to the construction activity defined for the
generic software process. Using the
architectural model as input, the construction
phase develops or acquires the software
components that will make each use case
operational for end users.
 To accomplish this, requirements and design
models that were started during the
elaboration phase are completed to reflect the
final version of the software increment.
 All necessary and required features and
functions for the software increment (i.e., the
release) are then implemented in source code.
SOFTWARE ENGINEERING 13
 transition phase
 The transition phase of the UP
encompasses the latter stages of the
generic construction activity and the first
part of the generic deployment (delivery
and feedback) activity.
 Software is given to end users for beta
testing and user feedback reports both
defects and necessary changes.
 At the conclusion of the transition phase,
the software increment becomes a usable
software release.
SOFTWARE ENGINEERING 14
 Production phase
The production phase of the UP coincides with the
deployment activity of the generic process.
During this phase, the ongoing use of the
software is monitored, support for the operating
environment (infrastructure) is provided, and
defect reports and requests for changes are
submitted and evaluated.
It is likely that at the same time the construction,
transition, and production phases are being
conducted, work may have already begun on the
next software increment.
This means that the five UP phases do not occur in a
sequence, but rather with staggered concurrency.

SOFTWARE ENGINEERING 15