Report on Rational Unified Process

Report on Rational Unified Process (RUP) and Scrum methodology
RAJVEER KAUR UNIT CO-ORDINATOR:
33139411 MS. TANYA GILL
DATE OF SUBMISSION:
24/9/2018
Table of Contents
Introduction……………………………………………………………………………. 3
Rational Unified Process………………………………………………………………. 3
Scrum……………………………………………………………………………………3
Comparison between RUP and Scrum…………………………………………………. 4-5
Guidelines for RUP by discipline ……………………………………………………….5-7
Guidelines for RUP by phases…………………………………………………………… 7-8
Guideline for scrum……………………………………………………………………….8
Bibliography.………………………………………………………………………………9-10
INTRODUCTION
This report explains the mainly two types of methodologies, which helps to improve the development of software systems. Software development methodology “is the collection of procedures, techniques, tools and documentation aids which will help the system developers in their efforts to implement a new information system” (Avison and Fitzgerald, 2006). Organizations always intend to reduce their cost, development time, risks and looking for appropriate processes and approaches which can help to improve the performance, raise the profit, better quality. Various factors that contribute to the choice of the methodology for specific organization such as, organization size, what type of products and services the organization provides, level of the organization, team size. This report is for the employees of the consulting firm, called Innovative Solution, which mainly experts in two approaches: Rational Unified Process and Scrum. Both approaches apply in different situations, means depends upon the factors, which will discuss followed.
Rational Unified Process (RUP): Rational Unified Process is the process which was developed by Rational Software to gain developments in the software systems. RUP uses the Unified Modeling Language (UML) to describe its different phases, Unified Modeling Language is the most crucial segment of the Rational Unified Process. The main aims of the Rational Unified Process are the growth and preservation of the software systems under the development (Krutchen, 2000). Unified Modeling Language represents a different type of graphical diagrams, which shows various stages of the processes under the development. There are mainly four phases of the Rational Unified Process: Inception, Elaboration, Construction and Transition phase.

Scrum: In present’s scenario, scrum methodology is prevalent among the IT industries. This approach focuses on the best quality, quick response, and collaboration between the teams. Scrum is an agile and iteration based methodology, used as a framework for the development of a software system. It is an adaptive approach so that the team can quickly adopt the changes during the process at any stage, but this methodology is not appropriate for the distributed projects. Team communication and collaboration are extremely crucial in this approach, due to that the team size is 7 -10 members so that they can communicate face to face with each other. Main components of the scrum are product backlog, sprint planning meeting, sprint backlog, scrum sprint, and executable increment.

We Will Write a Custom Essay Specifically
For You For Only $13.90/page!


order now

Comparison between RUP and Scrum:
Rational Unified Process is a perspective process, as everything is pre-planned in this approach. While deciding this approach, all other factors should count into the account.
RUP Scrum
Rational Unified Process is an iterative based methodology. Scrum is also followed the Agile Manifesto and based on iterations.

The Rup is the predictive approach. But, scrum is an adaptive and self- organized approach.
This approach starts with the User Interface (UI), in which the team discusses with the stakeholders about their requirements and objectives of the project. In Scrum methodology, product backlog is very important part of prioritized requirements.

Rational Unified Process is the predefined approach. It is not a predefined methodology.

The whole methodology defines in the four main phases: Inception, Elaboration, Construction, and Transition. This approach executes in iterations called sprints, and one sprint is a complete cycle. The newsprint only can start, when the previous sprint has completed.

Duration of the iteration in the RUP approach, approximately, two weeks- 6 months, depends upon which iteration it is. Mostly the time frame of each sprint (iteration) is 2-4 weeks.

RUP approach produces some artifacts such as models, model documents, graphical diagrams, risk list and use case, which assist in the other similar projects. Limited support for building the artifacts in the scrum.

RUP methodology is appropriate for the large projects. For the small projects, Scrum is the best option.

Guidelines for RUP and Scrum methodology: For the organizations, an adequate methodology plays an important role towards the success rate. Numerous factors that should be considered while choosing a methodology for the specific client or project. Here are some guidelines for the employees of the Innovative Solution firm, which can help to select an appropriate approach, RUP and Scrum.

Rational Unified Process: Mostly RUP is perfect for large and distributed projects. The team follows some phases and disciplines in this methodology. Firstly, by disciplines:
Business modeling:
In the business modeling discipline, employees should understand the environment of the target organization.

In this stage, discussion between employees and stakeholders is hugely crucial on the current problem domain that is being addressed by the system.

Requirements:
Understand the basic needs of the stakeholder and explain them adequately what the plan is, what it will cover and what it will not include.

There is an agreement between the team and the stakeholder on the scope of the project.

Recognizing and prioritizing the new requirements that can be produced in the future.
Analysis and Design:
Design the perfect solution that specifies the requirements, tackles with the constraints and produces the positive results for the target organization.

Produce network models
Create a use case driven model and use cases
Implementation:
Apply practically all the models that produce in the analyze and design discipline
Program codes can be written in this phase
Testing:
In this discipline, the team try to test the created system, test the quality and try to find out the defects in the system.

If there is a default in the system, employees give an efforts to find out the solution, how can addressed those defaults.

Develop the test cases
Create the report on the test
Deployment:
In this discipline, the team should make sure that the delivery must be ready for the end users on time.

The team prepare the strategy for the deployment
Follow the installation process for the system
Training to the end users is very pivotal that the end users should know how they can access the system in their organization to elevate the profit.

Project Management:
This discipline focuses on the entire project from the beginning to end-stage and mainly followed by the manager.

Manager provides the guidelines to the whole team about the management of time, cost, risk, and quality
Planning for the next iterative at the end of each iteration.

Configuration and change management:
Integrate the different versions of the system and adapt to the changes throughout the project.
Change requests ought to be handled impeccably by the developers because it affects the whole management and plans which was already produced in the initial stage.

For handling the change request, a collaboration and communication between the teams and stakeholders play an essential role so that requirements can understand by project team.

Moreover, developers should fix a meeting with the end users to understand the changes and the new requirements.

Environment:
This discipline supports the rest of the effort concerning the proper guidance and tools must be available for the entire team.

By Phases:
Inception phase:
This is the first phase of the Rational Unified Process and takes around 10% time of the entire process.

Teams should not spend much time on this phase
Developers fix the meeting with the customers and achieve end user’s consensus on the goals of the project.

Demonstrate the use cases that will evolve in the project
Estimate the overall cost and time
At the end of this phase, developers create the Lifecycle Objectives (LCO) milestone.

Elaboration phase:
Create an architecture for the project and redefine the requirements in detail.

Identify the risks
It takes around 30% time and Lifecycle Architecture (LCA) milestone is produced in this phase.

Construction phase:
The third phase is paramount, and it takes the maximum time of the project,50%.

This phase mainly focusses on the specify the requirements of the end users.

Coding and testing of the system is also done in this phase
The milestone of this phase is Initial Operational Capability (IOC) and stakeholders must agree with this milestone.

Transition phase:
In this phase, teams make ensure that the system is ready to deliver to the end users. It takes almost 10% time of the entire project.

Training to the end users is done in this phase as well.

Most important that the system should be operated once in the organization.

At the end of this phase, teams can hold the milestone that is Product Release (PR).

Guideline for the Scrum: Scrum methodology follows the Agile manifesto. There are some guidelines if teams chose the Scrum methodology:
If the customer wants a quick response, then the team can choose an agile methodology
For the agile methodology teams should be motivated and self- organised because all the process is in the hand of the manager and project team.

The team must fix the daily meeting with the team and stakeholders as well to gain the highest success rate in the short interval.

Scrum master (manager) consistently meet the team to track the progress of the project.
In the agile methodology, the process ought to be simple so that end users can easily operate the system.
Product backlog should effectually describe the requirements by product owner.

At the end of each sprint, the team makes sure that the objectives of sprint have achieved.

Bibliography:
Ambler, S.W. (December, 2015). A Manager’s Introduction to the Rational Unified Process
http://www.ambysoft.com/downloads/managersIntroToRUP.pdfAlexander, M. (2018). Agile Project Management: A Comprehensive Guide.
https://www.cio.com/article/3156998/agile-development/agile-project-management-a-beginners-guide.htmlGeambasu, C.V. ; Jianu, I. ; Gavrila, A. (2011) Influence Factor for The Choice of a Software Development Methodology. “Accounting and Management Information Systems.” Vol. 10, No. 4, pp. 479-494.

ftp://ftp.repec.org/opt/ReDIF/RePEc/ami/articles/10_4_3.pdfJaidi, A.S ; Qureshi, M. R.J. (Oct, 2014). “Scrum Practices and Global Software Development.” I.J. Information Engineering and Electronic Business, Hong Kong, vol 6, no 5, P.N. 22-28.

https://search-proquest-com.libproxy.murdoch.edu.au/docview/1769786724?pq-origsite=summon;accountid=12629;selectids=10000039,1006985,10000155John Smith. (2009). “A comparison of the IBM Rational Unified Process and Extreme Programming” https://pdfs.semanticscholar.org/50c7/2ed4e8457e6b908a7b0132f829eb46f0f750.pdfJoslin, R ; Muller, R. (2014). The Impact of Project Methodology on Project Success in different Contexts. Project Management Institute Research and Education Conference, Phoenix, AZ.
https://www.pmi.org/learning/library/project-methodologies-impact-success-contexts-8947Rational Unified Process: A Best Practices Approach. IBM
https://pdfs.semanticscholar.org/presentation/f512/ff1bd6bfca247a238a377d3bc344a08fce6c.pdf.

http://www.perftestplus.com/resources/rupfordummies_ppt.pdf