National University of Callao

Faculty of Industrial Engineering and Systems

Research Project
RUP (Rational) software development methodology
Unified Process)

Presented by:
Cesar Jackson, Sánchez Casas
Alessandra, Ramos Arias

Teacher: Ortega Rojas, Yesmi Kata

Callao
2020
 INDEX
CHAPTER I INTRODUCTION.........................................................................................................3
1.1 Background....................................................................................................................3
1.1.1 Brief History of RUP.................................................................3
1.1.2 Research Conducted in Peru..........................................................................3
1.2 Problem Statement..............................................................................................3
1.2.1 Definition of the topic.....................................................................................................3
1.3 Juicetfiction.................................................................3

1.4 Objecttyou

1.4.1 Objecttgeneral

1.4.2 Objecttyour specific..........................................................3

1.5 Alcances.............................................................................................................................3
1.6 Limitations...........................................................................................................................3
1.7 Delimitantes.......................................................................................................................3
CHAPTER II FRAME OF REFERENCE
2.1 Theoretical Framework....................................................................................................................3
2.1.1 Object-oriented software development methodology......................................3
2.1.2 RUP (RatUnified Process
2.1.3 Driven by use cases........................................................................................3
2.1.4 Focused on architecture..........................................................................................3
2.1.5 Interactit's Incremental
2.2 Research Methodologytnavigation
CHAPTER III INTRODUCTION TO SOFTWARE ENGINEERING...................................................3
3.1 Introduction
3.2 Basic concepts..............................................................................................................3
3.2.1 What is Software Engineering?.................................................................................4
3.2.2 What is quality software?......................................................................................4
CHAPTER IV SOFTWARE DEVELOPMENT PROCESSES............................................................4
4.1 Introduction
4.2 Stages of the software development process
4.2.1 Requirements Analysis
4.2.2 Specification principles.........................................................................................4
4.2.3 Design and architecture
4.2.4 Programming
4.2.5 Test
4.2.6 Documentation
 4.2.7 Maintenance
4.3 Life Cycle Models.............................................................................................4
4.3.1 Cascade model......................................................................................................4
4.3.2 Evolu development modeltvo
4.3.3 Prototype modeltRequirements Section............................................................4
4.3.4 Development model based on reusetlocalization............................................................4
4.3.5 Spiral development model
4.3.6 Incremental development model..............................................................................4
CHAPTER V RatUnified Process (RUP) Unified Process of Ratonal................................4
5.1 Introduction.......................................................................................................................4
5.2 Characteristicstcase of RUP........................................................................................................4
5.3 Development Principle
5.3.1 Adapt the process
5.3.2 Balance priorities
5.3.3 Demonstrate iterative valuetagain..................................................................................5

5.3.4 Raise the level of abstraction......................................................................................5

5.3.5 Focus on quality
5.4 RUP Lifecycle
5.5 Process
5.6 Phases
5.7 Phases
5.7.1 Start Phase
5.7.2 Development Phase
5.7.3 Construction Phase
5.7.4 Transition Phase
5.8 Level of knowledge of the RUP Method in Peru..........................................................5
CHAPTER VI ELEMENTS OF RUP
6.1 Elements of RUP
6.2 Actlife
6.3 Worker (ROLE)
6.4 Artifacts
6.5 AcrestPrimary and secondary or support activities................................................................6
CHAPTER VII PRACTICAL CASE USING RUP........................................................................6
7.1 Introduction.......................................................................................................................6
7.2 VOLVO IT Case
7.2.1 Experience with RUP projects.................................................................6
 7.2.2 Effects of using RUP
BIBLIOGRAPHY...............................................................................................................................6
GLOSSARY.....................................................................................................................................6
ANNEXES........................................................................................................................................6
 List of Figures
Figure 1. History of the RUP methodology....................................................................................6
Figure 2. Software Engineering................................................................................................13
Figure 3. Software quality model15
 CHAPTER I INTRODUCTION

The present research work covers the topic of the Rational Unified Process.

known by its acronym RUP), which can be defined as an engineering process of

software to produce high-quality software that meets global standards

and provide elasticity in terms and budgets. Due to the combination of the best

practices in software engineering, such as: requirements management, use of

component architecture, visual model, continuous quality verification and control

of changes, etc., makes the RUP one of the most used standards for examining,

carry out and demonstrate object-oriented systems.

Understanding RUP is essential for students specializing in the career of

Systems Engineering. A true systems engineer is not someone who has the

Title to hang on the wall and say I am a professional, on the contrary, being an engineer

of systems is to know the existing diversity of research methodologies of

software.

The importance of investigating this method is that large companies require a high

software quality level. RUP can be used regardless of size and the

organization sector, but due to the complexity and scale of the system, RUP is used

more and more in large companies.

1.1 Antecedentes
1.1.1 Brief History of RUP1

El precedente mas importante es la metodología de Ericsson, desarrollada por Iván

Jacobson in 1967.

Figure 1 History of the RUP methodology

Figure 1 shows a brief summary of the history of RUP represented

on a timeline.

This is a component-based development method that introduces the concept of

use cases. Between 1987 and 1995, Jacobson founded Objetory AB and began the process of

development of Objetory (abbreviation of Object Factory). Later, in 1995,

Rational Software Corporation acquired Objetory AB, and between 1995 and 1997, the

Rational Objectory Process (ROP) was developed from Objectory 3.8 and the Rational

Approach using UML as a modeling language.

Since then, Rational Software under the leadership of Grady Booch, Ivar Jacobson and

James Rumbaugh has developed and integrated various elements to extend RUP,

particularly focusing on a workflow called business modeling.

Rational Unified Process was launched in June 1998.

[Link]
1
1.2 Statement of the problem

Currently in Peru, there is not enough information about development methods.

of the RUP software, and many professionals and students in the field of computer science

They are not familiar with the term RUP or believe this method is outdated. Due to the rise

international in the development of commercial applications, and considering that some

of the companies in our country that specialize in information technology have

Having started to adopt this approach, all computer scientists must be aware of the latest

technologies for both software development and application programs.

1.2.1 Definition of the topic

Conduct a research study to explore the concepts, the operating logic

and practical examples of the RUP software development methodology implemented in

VOLVO IT in general; also know its advantages and disadvantages.

1.3 Justificación

The National University of Callao has considered finding and adopting tools

that can improve and expand the knowledge of the students. The current project of

Research on the Rational Unified Process (RUP) aims to promote the

research on the latest software development methods by students

and/or professionals in the field of computer science, all with the aim of creating

integral professionals ready to face new technologies and paradigms of

work. It is expected that this work will serve as a basis for future research. Having

keep in mind that this content has been included in the agenda of the course on 'Engineering of

Software" taught at the National University of Callao, and because there are many

success stories, this is currently one of the most used tools.

1.4 Objetivos
1.4.1 General objective
Write a research paper on RUP (Rational Unified Process) that presents

the concept, the elements, the life cycle, the success stories and the understanding of the

international companies (like VOLVO IT) that adopt this method. Just like

also to know the opinions of professionals in the field of computer science from

country on this topic, with the purpose that this research will serve as a basis for

future research by students of the National University of Callao on

RUP, software development methodology and software engineering techniques.

1.4.2 Objetivos específicos

a) Create a document that describes the general concepts of engineering

software and software development methods.

b) Obtain a general understanding of the degree of knowledge and use of RUP in

our country.

c) Explain the importance of using these methods in a real work environment.

d) Describe the components of the RUP methodology, the basic components of

RUP, the life cycle of the methodology.

e) Present a case study of VOLVO IT that uses this method in the

software development process.

1.5 Scope
Present the basic concepts of software development methodology, the

basic components of RUP, the life cycle of the methodology, and examples

application practices of Latin American companies, the situation of VOLVO IT is

will be demonstrated in this project.

1.6 Limitations

For the completion of this research work, no limitations were found for

carry it out, since it is a methodology that already has a track record, and we can

get information on the web easily.

1.7 Delimiters
The study of this research work will only include theoretical aspects of the

RUP methodology, as well as examples of companies that have included it in their development.

of the software, like VOLVO IT. The project will not delve into the design and the

RIP system programming developed by IBM.

CHAPTER II FRAME OF REFERENCE

2.1 Theoretical Framework

2.1.1 Object-Oriented Software Development Methodology

2.1.2 RUP (Rational Unified Process)
RUP stands for Rational Unified Process, it is a product of the process.

of software engineering that can provide a standardized optimal method to

assign tasks and responsibilities within the organization. development of. Its objective

it is to guarantee the production of high-quality software, to solve the needs of the

users within the established budget and time. assist in the analysis and design of

the aforementioned makes it easier to develop software with the

famosos casos de uso, diagramas, y un sinfín de herramientas.

RUP is divided into two dimensions, the horizontal axis representing time and

illustrates all aspects of the life cycle of the project process and the vertical axis that

represents the discipline, which naturally defines the activity.

The first dimension represents the dynamic aspect of the process, expressed as

Stages, iterations, and conditions to complete the stage. The second dimension

it represents the static aspect of the process: how to describe it. In terms of

composition of processes, disciplines, activities and processes. Jobs, artifacts and

roles.

Figure 2 shows how the focus of each discipline changes under circumstances

specific Time and each stage. For example, in the iteration At the beginning, we spend more

time on the requirements and the last iteration We spent more time implementing the

project in itself.

Figure 2 Disciplines, phases, iterations of the RUP

2.1.3 Driven by use cases
According to Kruchten, P. (2000), a use case is a requirement capturing technique.

They make you think about the importance. Users, not just in terms of functions.

which can be considered. Use cases are defined as part of the function A

system that provides users with added value. Likewise, they represent the

functional requirements of the system. In RUP, use cases are more than a

designated tool System requirements. They also guide their design,

implementation and testing.

Use cases are a general element and a guide The working method is

shown in figure 2.

Figure 3 The Use Cases integrate the work

2.1.4 Centered on architecture

The structure of the system is the organization or structure of its most relevant part, the

that allows all relevant personnel to have a common vision and perspective

clear of the complete system necessary to control the development. The architecture

involves the most important static and dynamic aspects of the system and is

related to decision-making that dictates how the system should be built and

help to determine the order in which to proceed. In addition, the definition of the architecture

should consider the quality elements of the system, performance, capacity of

reuse and capacity for evolution, so it must be flexible throughout

development process. The architecture is influenced by the software platform, the

operating system, the database administrator, the protocol, the considerations

of development as in the old systems. Many of these restrictions constitute

non-functional system requirements.

Figure 5 illustrates the evolution of architecture in this stage. From RUP. There will be a

more robust architecture at the end of the following drought phases. In the initial stage, what

We need to consolidate. Determine the architecture through comparative evaluation.

and modify it according to the project's requirements.

Figure 4 Evolution of the system architecture

2.1.5 Interactive and Incremental

2.2 Research Methodology
 CHAPTER III INTRODUCTION TO ENGINEERING
SOFTWARE
3.1 Introduction

We cannot start talking about the software analysis methodology without knowing

First, what is the general stage of software development in general. How

we all know, computer systems consist of hardware and software. Regarding the

hardware, its production is carried out systematically, and the basis of

knowledge to develop this activity is clearly defined. In principle, the

the reliability of hardware is comparable to any other artificial machine. A

difference of the software, whose architecture and results have been questioned

historically due to related issues. Among them, we can emphasize the

next points: the system cannot meet the user's expectations, the

The program "failed" at a certain frequency and the software costs are difficult to

to predict and often exceed estimates, so modifying the software is

a difficult and costly task.

Large-scale software projects require stable and comprehensive tools.

that can provide resources at all stages of the project development. The
Rational Unified Process (RUP) is a tool that offers a large amount of

advantages, the most important is the involvement of all participants in the

project development, thus improving communication between users and programmers,

thus reducing misunderstandings, avoiding possible defects in the system

and discovering them quickly; due to these advantages and many other advantages, RUP is

has become an enticing option for software production companies.

3.2 Basic Concepts

3.2.1 What is Software Engineering?

This engineering involves very diverse fields of computer science and the sciences of

computing, such as the construction of compilers, operating systems, or the

intranet/internet development, addressing all phases of the development life cycle of

any type of information system. And apply to fields (business, research

scientific, medicine, production, logistics, banking, traffic control, meteorology,

law, internet and intranet, etc.) (Blanco, 2015).

In Figure 2, we can schematically visualize that it includes the

software engineering
 Figure 5. Software Engineering

Over time, some authors have provided some definitions:

Software Engineering is the study of the principles and methodologies for

development and maintenance of software systems" (Zelkovitz, 1979)

Software Engineering is the establishment and use of solid principles of

engineering in order to obtain software in a cost-effective manner, that is reliable and

I worked on real machines" (Bauer, 1972).

It is the application of a systematic, disciplined, and quantifiable approach to

development, operation and maintenance of the software; that is, the application of

software engineering" (IEEE, 1993).

With all of the above mentioned, we can say that of the four authors described

the main objectives of software engineering in a different way, which is the

basis for establishing and implementing principles and methods. These principles and methods

they will guide us to carry out an effective development from all stages of

software development, from inception to implementation and maintenance.

3.2.2 What is quality software?

Rafael Gómez Blanes on his personal blog tells us that:

Far from proposing a definition that is too academic and being pragmatic, one can

to say that quality software not only has the ability to define correctly the

required functions, but also, it is considered of better quality when the cost
 its maintenance is low and the difficulty of introducing new changes (new

requirements) is also low or insignificant

The end user measures the quality of the software according to the results it provides.

provide, in order to fulfill the purpose of its creation, to optimize resources

used and their behavior over time. What we are talking about is

a software that is easy to adapt to changes and improvements, in this sense, the quality

the software depends on who will judge. There are methods for evaluating software more

objectives, which include: metrics, statistics, etc.

What standards should be followed when managing software process certification?

ISO 9000, CMMI.

[Link] Software Measurement

Through measurement, we can monitor and control the development of the product and the

evolution of the process. Through measurement, we can evaluate which product or

the process is better. Another key point in software development is to predict from a

planning perspective. (Gómez, 2012).

[Link] Basic concepts

Measure

The measurements provide a quantitative indication of the degree, amount, size,

capacity and size of certain attributes of a process or product2.

Metric

Quantitative measure of the degree to which a system, component, or process has a

given attribute. (IEEE, 1993).

2
[Link]
requirements/#:~:text=Within%20the%20context%20of%20the,act%20of%20determining%20a
%20measure.
Indicator

Metric or combination of metrics that provide an in-depth view of the process.

of the software, the software project or the product itself. (Ragland, 1995).

[Link] Types of indicators

Process indicators
Provide a deeper understanding of the effectiveness of existing processes.

collected over a long period of time from all the projects of the organization

to achieve long-term improvements in the software process.

Project Indicators
Allow:

Evaluate the status of the ongoing project.

Track potential risks.
Identify critical issues before they occur.
Adjust the workflow and tasks.
Evaluate the project team's ability to control the quality of
project.

Product indicators
They allow you to evaluate their quality.

Figure 3 shows the software quality model.

 CAPITULO IV PROCESOS DE DESARROLLO DE
SOFTWARE
4.1 Introduction
4.2 Stages of the software development process
4.2.1 Requirements Analysis
4.2.2 Specification Principles
4.2.3 Design and architecture
4.2.4 Programming
4.2.5 Test
4.2.6 Documentation
4.2.7 Maintenance
4.3 Life Cycle Models
4.3.1 Cascade model
4.3.2 Evolutionary Development Model
4.3.3 Requirements Prototyping Model
4.3.4 Development model based on reuse
4.3.5 Spiral development model
4.3.6 Incremental development model
 CHAPTER V Rational Unified Process (RUP) Process
Unified Rational
5.1 Introduction
5.2 Characteristics of RUP
5.3 Principle of development
5.3.1 Adapt the process
5.3.2 Balancing priorities
5.3.3 Demonstrate value iteratively
5.3.4 Raise the level of abstraction
5.3.5 Focus on quality
5.4 RUP Life Cycle
5.5 Process
5.6 Phases
5.7 Phases
5.7.1 Initiation Phase
5.7.2 Elaboration Phase
5.7.3 Construction Phase
5.7.4 Transition Phase
5.8 Level of knowledge of the RUP Method in Peru
 CHAPTER VI RUP ELEMENTS
6.1 Elements of RUP
6.2 Activity
6.3 Worker (ROLE)
6.4 Artifacts
6.5 Primary and secondary or support activities
 CHAPTER VII PRACTICAL CASE USING RUP
7.1 Introduction
7.2 VOLVO IT Case
7.2.1 Experience with RUP projects
7.2.2 Effects of using RUP
BIBLIOGRAPHY
Blanco, A. (2015). Definition of Software Engineering. Software Engineering.
[Link]
[Link]
Zelkovitz, M. V., Shaw, A. C. and Gannon J. D. (1979). Principles of Software
Engineering and Design. Englewood Cliffs, NJ, USA: Prentice – Hall.
Bauer, F. L. (1972). "Software Engineering" in Information Processing 71:
Proceedings of IFIP Congress 71, Ljubljana, Yugoslavia.
IEEE, IEEE Standard Glossary of Software Engineering Terminology (IEEE Std
610.12-1990). USA: IEEE, 1990.
Gomez Blanes, R. (2018). What is software quality. Professional site of Rafa G.
[Link]://[Link]/blog/elpdpa-que-es-la-calidad-del-software
Gomez, J. (2012). Why should software be measured?. The IT laboratory.
[Link]
The medication allows us to see from a different perspective.
of the planning.
IEEE Software Engineering Standards. Standard 610.12-1990, 1993
Ragland, B. (1995).Measure, Metric or Indicator: What́s the Difference?,Crosstalk, 8
(3), 29-30.
GLOSSARY

ANNEXES