0% found this document useful (0 votes)
11 views21 pages

20 - Lecture

Uploaded by

mihiyer158
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
11 views21 pages

20 - Lecture

Uploaded by

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

INTRODUCTION TO SOFTWARE

ENGINEERING
SE-101
RUP Model

Lecture By:
Shakir Rasheed Khan Khattak

1
RUP MODEL

2
RUP Model
1. Rational Unified Process (RUP) is a software development process for object-
oriented models.
i. There are 3 types of models in the object oriented modeling and design are: Class
Model, State Model, and Interaction Model
2. It is also known as the Unified Process Model. It is created by Rational corporation
and is designed and documented using UML (Unified Modeling Language).
3. This process is included in IBM Rational Method Composer (RMC) product. IBM
(International Business Machine Corporation) allows us to customize, design, and
personalize the unified process.
4. RUP is proposed by Ivar Jacobson, Grady Bootch, and James Rambaugh. Some
characteristics of RUP include use-case driven, Iterative (repetition of the process), and
Incremental (increase in value) by nature, delivered online using web technology, can
be customized or tailored in modular and electronic form, etc.
5. RUP reduces unexpected development costs and prevents wastage of resources.
6. The RUP is an agile software development method, in which the life cycle of a
project, or the development of software, is divided into four phases. Various activities
take place during these phases: modelling, analysis and design, implementation,
testing and application.
3
RUP Model
1. RUP is iterative, meaning repeating; and agile. Iterative because all of the process’s
core activities repeat throughout the project.
■ RUP Methodology:
1. The process is agile because various components can be adjusted, and
phases of the cycle can be repeated until the software meets requirements
and objectives.
2. The process, as visualized in the image in this Lecture, should be looked at
from two dimensions. Firstly, there is the TIME DIMENSION, represented by the
horizontal axis. The time dimension is expressed in terms of the phases and
cycles, iterations, and milestones.
3. Secondly, the vertical axis is the PROCESS DIMENSION. This dimension
represents the static aspect of the process and is described in terms of
activities, artefacts, workers, and workflow.

4
RUP Model - Diagram

5
RUP Model
■ Rational Unified Process: TIME DIMENSION
– The time dimension means the dynamic organization from the process over
time. The software’s life cycle is itself divided further into cycles.
– Each cycle corresponds to, for example, a period in which a new generation of a
product is being worked on. The Rational Unified Process (RUP) divides
development into the four consecutive phases:
1. Inception phase
2. Elaboration phase
3. Construction phase
4. Transition phase
– Each phase is finalized with a milestone. A milestone is a point in time where
decisions of critical importance must to be made. In order to be able to make
those decisions, the objectives must have been accomplished.
– For example, a milestone from the first two phases is the progress of the use
case. A use case is a description of a system’s behaviour and describes who
can do what using a system. This is an important component in the
development of software.
– As can also be seen in the RUP visualization, testing already starts in the first
phase. Normally, a product will already have to be completed by then. That is
because this involves prototypes and test models.
6
RUP Model - Diagram

7
RUP Model – Phases

Phases of RUP: There is total of five phases of the life cycle of RUP:
■ Phase 1: Inception
■ Phase 2: Elaboration
■ Phase 3: Construction
■ Phase 4: Transition

8
RUP Model - Phases
Phases of RUP: There is total of Four phases of the life cycle of RUP:
■ Phase 1: Inception
1. During the first phase, the basic idea and structure of the project are
determined. In this phase, the team meets regularly to determine the project’s
necessity, but also its viability / feasibility and suitability / correctness. Viability
and suitability also include the expected costs and the means needed to
complete the project after the green light has been given.
2. Depending on the project, the result of the first phase could be:
1. A vision statement
2. First use case (20% completed)
3. Market research results
4. Financial prognosis / Forecast
5. Risk assessment
6. Project plan
7. Corporate or business model
8. Prototypes
9
RUP Model - Phases
■ Phase 1: Inception Continue..
■ The results should then be assessed according to several criteria:
1. Were all interested parties included and do they all agree?
2. Are the requirements of the development reliable?
3. Are the costs credible? What are the priorities and risks?
■ Phase 2: Elaboration
1. During the elaboration phase, the system’s requirements and its required
architecture are assessed and analyzed. This is where the project begins to
take shape. The objective of the elaboration phase is to analyze products and
to lay a foundation for the future architecture. Results of the elaboration phase
include:
1. Use case (80% completed)
2. Description of the feasible architecture
3. Project development plan
4. Prototypes for tackling risks
5. User manual
10
RUP Model - Phases
■ Phase 2: Elaboration
■ Criteria for the results:
1. Is the architecture stable?
2. Are important risks being tackled?
3. Is the development plan sufficiently detailed and accurate?
4. Do all interested parties agree on the current design?
5. Are the expenditures acceptable?
■ Phase 3: Construction
1. In the construction phase of the Rational Unified Process (RUP), the software
system is constructed in its entirety. The emphasis is on the development of
components and other features of the system.
2. The majority of coding also takes place in this phase. In this production
process, the emphasis is on managing costs and means, as well as ensuring
quality. Results from the production phase include:
1. Fully completed software system
2. User manual
11
RUP Model - Phases
■ Phase 3: Construction
■ To be assessed according to:
1. Is the product stable and complete enough for use?
2. Are all interested parties/users ready for the transition into the product’s
usage?
3. Are all the expenditures and means still in good order?
■ Phase 4: Transition
■ The objective of the transition phase is to transfer the product to its new user. As
soon as the user starts using the system, problems almost always arise that require
changes to be made to the system. The goal, however, is to ensure a positive and
smooth transition to the user. Results and activities in the last phase:
1. Beta testing
2. Conversion of existing user databases
3. Training new users
4. Rolling out of the project to marketing and distribution
■ Input from the new users should guide the assessment here.
12
RUP Model – Building Blocks
■ The Rational Unified Process is a combination of building blocks used to describe
who, what, when, and how the development process will occur.
■ These four building blocks are:
1. (Roles) the ‘Who’: It shows who are the responsibilities for developing the
software product. It may be an individual or a group of individuals together as
a team who work on it.
2. (Work Products) the ‘What’: It indicates what will be produced. That shows the
behavior and type of software product.
3. (Workflows) the ‘When’: It represents the flowchart of activities in order to
produce a software product.
4. (Tasks) the ‘How’: It describes how the development will take place, i.e. a unit
of work assigned to a Role to perform and that provides a meaningful result.

13
Workflows of Rational Unified Process
■ This process passes through six main workflows and three supporting workflows:
■ Main Workflows:
1. Corporate Modeling / Business Modelling(Planning)
2. Requirements Gathering
3. Analysis & Design
4. Implementation / Coding
5. Testing
6. Application / Deployment
■ Supporting Workflows:
1. Project Management
2. Configuration &Change Management
3. Environment Management

14
RUP Model
■ Rational Unified Process: PROCESS DIMENSION
– The various phases related to developing software systems are now clear. As in
any other process, the RUP describes who does what, where, and when.
■ The ‘who’ in this process is the employee who is actively engaged in building the
system. ‘What’ refers to something concrete, a piece of information. These
‘artefacts’ may take many forms, for example that of a user case or prototype.
– The various phases already indicate the various activities involved in the
development of a system. Here follows a more detailed explanation of the core
activities.
1. Corporate modelling
2. Requirements
3. Analysis and design
4. Implementation
5. Testing
6. Application

15
RUP Model
■ Corporate modelling
1. One of the problems in the use of technical systems is that of the system and
the user not being able to communicate properly. This leads to inefficiency in
multiple areas.
1. For example, the input the developer receives from the user is not properly used
for the development of the generation of systems. Rational Unified Process (RUP)
partly solves this problem by creating universal language and offering processes.
■ Requirements
1. The objective of requirements is to describe what the system should do and
how it should function. Both the user and the developer should agree on the
requirements as described in the first phase. Everything is included in a vision
document. After that, a use case is developed.
■ Analysis and design
1. The objective of analysis and design is to show how the system is realized in
the implementation phase. It should meet all requirements, be robust, and
execute all its tasks as described in the use case. This model design functions
as a blueprint for the rest of the process.

16
RUP Model
■ Implementation
1. Implementation is found throughout the Rational Unified Process (RUP), as is
every other activity, but it is also one of the model’s engineering disciplines.
The objective of implementation is to construct the full system. This is where
components are tested and released.
■ Testing
1. The objective of testing is to verify the proper integration of all the components
and the software. The testing phase is also where defects are identified and
resolved. Testing does not only happen in the testing phase. The Rational
Unified Process (RUP) is iterative, so testing happens throughout the project.
2. Tests are carried out along three dimensions:
i. Reliability
ii. Functionality
iii. Application management and system performance

17
RUP Model
■ Application
1. The objective of applying a system is, naturally, successfully releasing a
software system and enabling the user to work with the new system. It
includes many activities described in the transitional phase 4, including:
i. Packaging
ii. Distribution
iii. Installation
iv. Help and assistance
v. Beta tests
vi. Data migration
vii. Acceptance
■ In addition, there are three supporting disciplines:
i. Configuration and change management
ii. Project management
iii. Environment

18
Advantages Of RUP Model
1. It allows us to deal with changing requirements within the project’s development life
cycle as per the client or customer needs, i.e. it welcomes change.
2. It supports incremental build the software product.
3. It provides proper documentation of the software product.
4. It helps to use the resources efficiently.
5. It helps to identify issues early in the process life cycle.
6. It improves process control and risk management.
7. It enhances team productivity.
8. It helps reduces unexpected development costs.

19
Disadvantages Of RUP Model
1. It is a complex model to implement as it has multiple stages of the workflow.
2. It is challenging for organizations to implement which has, small team size or
projects.
3. It should be highly result-oriented from individuals or teams.
4. It emphasizes the integration of modules throughout the software development
process, so this creates trouble during the testing phase.

20
THANK YOU

21

You might also like