What Is RUP Process
What Is RUP Process
What Is RUP Process
What is RUP (rational unified process)?
RUP stands for Rational Unified Process. Its a software development process framework
which has been taken forward by Rational(part of IBM corporation)
In the figure, the Rational Unified Process Model can be diagrammatically viewed. As
depicted, RUP has four distinct project life cycle phases:
a) Inception – is the part where the actual exploration of the concept happens with the
stakeholders management, definition of the project scope, cost benefit and feasibility analyses.
This is the starting phase of the project and actually provides the foundation for each of the
ensuing processes.
b) Elaboration – This is the phase where the project starts to take shape. The requirements are
more or less frozen and the design of the system gets into its first draft.
c) Construction – This phase is the actual building phase of the project where the software
takes shape and it involves the major coding part out of the four phases. Testing is also part of
this phase. The first cut release of the software is the objective of the phase
d) Transition – This phase is the wrapping up of the system with the release to the client and
the final support phase of the software system starts.
RUP also has six engineering disciplines and three supporting disciplines. These nine RUP
disciplines are part of each iterations required in the project life cycle. The six engineering
disciplines are somewhat similar to the waterfall model phases whereas the three supporting
disciplines are unique to the RUP framework.
a) Business Modeling – Initial modeling of business with the analysis and scope formation
f) Deployment – finally deploying the system at client site and going into production level
b) Project Management – Planning, estimation, resourcing and overall managing the team and
customers as part of the project
c) Environment - Ensuring that the project team is aware of all aspects and of the RUP
implementation.
As per the Fig A , the RUP framework is depicted as a “hump chart” with the matrix showing
the RUP phases and the RUP disciplines. Lets say for example, the requirement discipline is
peaked at the initiation and elaboration stage after which it flattens bout does not completely
disappear. Similarly project management discipline is required to be at a constant peak
throughout the project and cannot flatten or lag behind in any phase.
RUP is one of the most complex software development project life cycles and involves proper
project planning for the successful implementation of the system
Inception Phase:
Interacting with business users , developers and project manager to make business requirements
by using tools like MS Visio and MS word. MS excel also used for some documentation
purpose.
Using RUP (rational unified modeling) to make BRD (business requirement document)
specifications.
Performing requirement analysis and design work with rational rose and analyzed, documented
the system specifications, business requirements and detail design of the existing business by
using a the tool requisite pro for the requirement tracking and analysis.
Elaboration Phase:
In this phase created Activity diagrams, sequence diagrams and collaboration diagram etc by
using Microsoft tool MS Visio.
Documented the critical path analysis and extensively analyzing the ER diagrams (entity relation
diagrams).
Also finding out the different opportunities and parameters that can improve the business process
and performance.
Construction Phase:
Developed a prototype for actual system and developed project blue print. Also developed a
mock web page generation for a part of the system goal.
Identifying the actual network and human resources to utilize properly for development,
documentation and training purposes.
Transition Phase:
In this phase we concentrate in vendor software compatibility , data base integrities and other
performance issues.
Configuration, implementation and deploying the developed software in various cross platforms
to see the products efficiency.
Construction: System code, QA testing cases, / test scripts, and a test plan.