Semester 2, 2018
Unit Code: ICT501
Unit Coordinator: Tanya McGill
Unit Name: Business Analysis and Systems Development
Waseem Iqbal (33495713)
Table of Contents
Rational Unified Process (RUP) 3 Rational Unified Process (RUP) ( Continue ) 4
Difference between the Scrum and Rational Unified Process 6
1. Rational Unified Process (RUP)
A task assigned to me in system development process and consider as an employee of a firm “Innovative Solutions” that specializes in systems analysis, design, and development services. It provides solution to all types of end users from one room end users or a big multinational company. There are a wide variety of possible approaches to the development of systems. These vary considerably in terms of factors such as whether they are:
Sequential versus iterative
Model driven versus product driven
Prescriptive versus adaptive
Proprietary versus in-house
Different approaches are suited to different types of projects in different types of organizations. Innovative Solutions has expertise in two system development methodologies: Rational Unified Process and Scrum.
Now I ‘would be tell you about the Rational Unified Process. It is a process in which object oriented programming approach has a highly effective project management and software production. RUP has key characteristics which are use case diagram, architecture –centric and least not last iterative and incremental approach.
In a RUP we have following four phases which are useful in whether it is small firm projects or large or a multinational companies. These are inception, elaboration, construction, and transition.
RUP fundamental practices
In the RUP there are six RUP fundamental practices which are used widely in every project to make the RUP suitable.
Develop of software iteratively: when there is problem to understand the problem then it allows making the changes in to achieve the reasonable solution.
Manage requirements: this phase describes how to manage the all thing how to take the decision and documents as well.
Use component-based architecture: in this system architecture into components which are reusable not only on the projects, it also useful in future projects.
Visually model software: this shows how to create the structure of the software, visual modes and behavior of architecture.
Verify Software Quality: it allows controlling the quality and evaluating the software in the software development phase.
Control changes to software: it provides the ability to control, track and monitor changes which have been completed for success fully of development of the software.
There are four phases of rational unified process
Inception = Define the scope of the project.
Elaborations= plan the project and define the specify features.
Construction= they can build the product.
Transition = transition the product in to end of the user and community.
Also it has some building blocks which are workers (who), activities (how), artifacts (what), workflows (when).
Analyze the problem
Understand stake holder needs
Define the system
Mange scope of the system
Refine the system definition
Mange the change requirement
To provide the better system developers with better understanding of the system requirement.
The RUP has following benefits which are given below:
Develop software iteratively
Use component based architecture
Visually model software
Verify software quality
Control changes software
On the other hand RUP has some drawbacks:
All the members of the team are expert in their work and experienced member is required for the work.
In this process reuse able of any component is not possible; it’s just like some of water fall model.
It is not beneficial for large projects because when testing phase occurs the project require moving back and correcting that thing but possible due to res usable of resources is not possible.
Scrum is a simple and it is an opposite of any complex algorithms and it is easy to understand. Scrum is mainly consist of product owners, development team and scrum master. Scrum chose the best way to accomplish their work by team work internally rather listening from outside the team members. It is designed to optimize the work of a project in a flexibility way, creativity and productivity.
Scrum have many types of characteristics which are self-organized, empowered, collaborations, shared goal and purpose, optimize size, diverse skills.
Benefits of scrum:
Speed to market
Uses of Scrum
Scrum was used development for development and managing products. Starting of the early 1990, Scrum model has used worldwide.
Research and identify viable, product capabilities, technologies, and markets.
Development of products and enhancements of product.
3) Releasing the products and if needed then enhancements, that can be many times per day.
4) Develop Cloud and other operational environments for customer use and product use.
5) To sustain and reproduce or renew products.
Scrum model used to develop hardware’s , Software’s , embedded software, networks and their function, government, schools, Managing, marketing the operation which done in organizations and even everything we used in our daily lives, as individuals. In technology, marketing, and environmental complexities and the interaction between these rapidly increase; Scrum used can be used in our daily life in decrease the complexity. Scrum model is very effective into the iterative knowledge and incremental knowledge. Scrum model now a days use widely for every product, management of origination and services as well. The essence of Scrum is a small team of people. The individual team is highly flexible and adaptive. Just some people can be work as a team in this because they can handle all the work. They cooperate through sophisticated-development-architectures and release environments. When the words “development” and “develop” are used in the Scrum model they refer to the complexity of work.
Draw backs of scrum
Scrum projects are not able to define the definition of its projects.
Daily routines meeting also increase the cost of the projects to some extent because day to meeting also take time resource which is very precious for every humans.
It also require the high level of communications to see through the each back log and review of their team members and master scrum and the owner.
Difference between the Scrum and Rational Unified Process
RUP is a formal cycle but some of its cycle are concurrent and uniform and Scrum is a complete cycle in each sprint
RUP has a multiple Iterations and scrum has end to end project plan
RUP has controlled scope and if we to change there is a whole procedure in it. But, on the other hand Scrum uses a project Backlog.
RUP is for long term projects and enterprise level but Scrum is for small projects.
The scrum master helps the team and understand and it can be used the self-management and it can be used the cross functionality on the other hand Rup “Collaborate across Team and it can be create the self-managed teams.
Each scrum member applies on expertise and Rup is always on quality
By the every end of the sprint the scrum team should be identified actionable and apply on the next sprint on the other hand Rup the can be adapt the process and prove the process continuous.
Both Rational Unified Process (RUP) and Scrum are software development frameworks. Both are considered to be agile, which means that the requirements and solutions of the project evolve as a result of team collaboration. They also both use an iterative approach, splitting the development process into distinctive stages. Both frameworks emphasize cross-functionality and collaboration, and promote self-management within the team. And finally, there is a focus on product quality within both frameworks.
Both UP and agile methods attempt to bring the focus of software development back onto software. Since it is software that is shipped, and paid for, then using a project team’s resources to develop software that addresses customer requirements should be the main focus of any project. While documentation, design and analysis are necessary parts of the development approach, they should be seen as useful tools to be used as needed, and not ends in themselves.
Grady Booch, Ivar Jacobson, and James Rumbaugh, Unified Modeling Language 1.3, White paper, Rational Software Corp., 1998.
Philippe Kruchten, A Rational Development Process, CrossTalk, 9 (7), STSC, Hill AFB, UT, pp.11-16
Ivar Jacobson, Grady Booch, and Jim Rumbaugh, Unified Software Development Process, Addison-Wesley, 1999.
Grady Booch, Jim Rumbaugh, and Ivar Jacobson, Unified Modeling Language—User’s Guide, Addison-Wesley, 1999.
Philippe Kruchten, Rational Unified Process—An Introduction, Addison-Wesley, 1999.
Ivar Jacobson, Magnus Christerson, Patrik Jonsson, and Gunnar Övergaard, Object-Oriented Software Engineering—A Use Case Driven Approach, Wokingham, England, Addison-Wesley, 1992, 582p.