rational unified process
DESCRIPTION
UML, RUP, Software engineering, Rational Unifies ProcessTRANSCRIPT
![Page 1: Rational Unified Process](https://reader034.vdocuments.net/reader034/viewer/2022051414/559de9b31a28ab44148b460e/html5/thumbnails/1.jpg)
Object Oriented Design and Analysis
Rational Unified Process
![Page 2: Rational Unified Process](https://reader034.vdocuments.net/reader034/viewer/2022051414/559de9b31a28ab44148b460e/html5/thumbnails/2.jpg)
Object Oriented Design and Analysis
Software Development Process
An approach to building, deployment, and maintaining software.
![Page 3: Rational Unified Process](https://reader034.vdocuments.net/reader034/viewer/2022051414/559de9b31a28ab44148b460e/html5/thumbnails/3.jpg)
Object Oriented Design and Analysis
Unified Process
• A iterative and incremental software development process framework for building object-oriented systems.
• Emerged as a popular software development process
![Page 4: Rational Unified Process](https://reader034.vdocuments.net/reader034/viewer/2022051414/559de9b31a28ab44148b460e/html5/thumbnails/4.jpg)
Object Oriented Design and Analysis
Iterative and evolutionary development
• An iterative and evolutionary approach allows start of development with incomplete, imperfect knowledge
• Iterative and evolutionary have the following advantages:– Logical progress toward a robust architecture– Effective management of changing requirements– Continuous integration– Early understanding of the system– Ongoing risk assessment
![Page 5: Rational Unified Process](https://reader034.vdocuments.net/reader034/viewer/2022051414/559de9b31a28ab44148b460e/html5/thumbnails/5.jpg)
Object Oriented Design and Analysis
Contd..
Requirements
Design
Implementation &Test & Integration
& More Design
Final Integration & System Test
Requirements
Design
3 weeks (for example)
The system grows incrementally.
Feedback from iteration N leads to refinement and adaptation of the requirements and design in iteration N+1.
Iterations are fixed in length, or timeboxed.
Time
Implementation &Test & Integration
& More Design
Final Integration & System Test
![Page 6: Rational Unified Process](https://reader034.vdocuments.net/reader034/viewer/2022051414/559de9b31a28ab44148b460e/html5/thumbnails/6.jpg)
Object Oriented Design and Analysis
Contd..
Early iterations are farther from the "true path" of the system. Via feedback and adaptation, the system converges towards the most appropriate requirements and design.
In late iterations, a significant change in requirements is rare, but can occur. Such late changes may give an organization a competitive business advantage.
one iteration of design, implement, integrate, and test
![Page 7: Rational Unified Process](https://reader034.vdocuments.net/reader034/viewer/2022051414/559de9b31a28ab44148b460e/html5/thumbnails/7.jpg)
Object Oriented Design and Analysis
Rational Unified Process
• A refinement of the unified process i.e. iterative software development process.
• provides a disciplined approach to assigning tasks and responsibilities within a development organization
• Goal - to ensure the production of high-quality software that meets the needs of its end-users, within a predictable schedule and budget
![Page 8: Rational Unified Process](https://reader034.vdocuments.net/reader034/viewer/2022051414/559de9b31a28ab44148b460e/html5/thumbnails/8.jpg)
Object Oriented Design and Analysis
RUP• Process
– Enhance team productivity
– Configurable• no single process is suitable for all software
development• adapts to small & large development teams
– Documentation• Model based artifacts• UML
![Page 9: Rational Unified Process](https://reader034.vdocuments.net/reader034/viewer/2022051414/559de9b31a28ab44148b460e/html5/thumbnails/9.jpg)
Object Oriented Design and Analysis
RUP
• Building blocks– Roles (who)
• responsibilities
– Tasks (how)• Unit of work• Result oriented – should be useful
– Work products (what)• Resultant product
![Page 10: Rational Unified Process](https://reader034.vdocuments.net/reader034/viewer/2022051414/559de9b31a28ab44148b460e/html5/thumbnails/10.jpg)
Object Oriented Design and Analysis
RUP Best Practiceshow to effectively deploy commercially proven approaches to software development for software development teams•Develop software iteratively
– not possible to
– define the problem upfront
– design the entire solution– each iteration ends with a release
•Manage requirements– use case to capture functional requirements– should be traceable
![Page 11: Rational Unified Process](https://reader034.vdocuments.net/reader034/viewer/2022051414/559de9b31a28ab44148b460e/html5/thumbnails/11.jpg)
Object Oriented Design and Analysis
Contd..
• Use component-based architectures• Visually model software– different models to communicate• different aspects with different stakeholders• UML
![Page 12: Rational Unified Process](https://reader034.vdocuments.net/reader034/viewer/2022051414/559de9b31a28ab44148b460e/html5/thumbnails/12.jpg)
Object Oriented Design and Analysis
Contd..
• Verify software quality– review• functional requirements• non-functional requirements
– should be part of the process
• Control changes to software– continuous integration
![Page 13: Rational Unified Process](https://reader034.vdocuments.net/reader034/viewer/2022051414/559de9b31a28ab44148b460e/html5/thumbnails/13.jpg)
Object Oriented Design and Analysis
RUP Process
• Two dimensions.–Horizontal axis represents time and shows the
dynamic aspect of the process as it is enacted, and it is expressed in terms of cycles, phases, iterations, and milestones.–Vertical axis represents the static aspect of the
process: how it is described in terms of activities, artifacts, workers and workflows.
![Page 14: Rational Unified Process](https://reader034.vdocuments.net/reader034/viewer/2022051414/559de9b31a28ab44148b460e/html5/thumbnails/14.jpg)
Object Oriented Design and Analysis
RUP - Two Dimensions
![Page 15: Rational Unified Process](https://reader034.vdocuments.net/reader034/viewer/2022051414/559de9b31a28ab44148b460e/html5/thumbnails/15.jpg)
Object Oriented Design and Analysis
Phases and Iterations - The Time Dimension
• dynamic organization of the process along time
• the software lifecycle is broken into cycles, each cycle working on a new generation of the product– Inception phase– Elaboration phase– Construction phase– Transition phase
![Page 16: Rational Unified Process](https://reader034.vdocuments.net/reader034/viewer/2022051414/559de9b31a28ab44148b460e/html5/thumbnails/16.jpg)
Object Oriented Design and Analysis
RUP - Lifecycle Phases
![Page 17: Rational Unified Process](https://reader034.vdocuments.net/reader034/viewer/2022051414/559de9b31a28ab44148b460e/html5/thumbnails/17.jpg)
Object Oriented Design and Analysis
RUP- Core Workflows
![Page 18: Rational Unified Process](https://reader034.vdocuments.net/reader034/viewer/2022051414/559de9b31a28ab44148b460e/html5/thumbnails/18.jpg)
Object Oriented Design and Analysis
Inception objectives
• Establish software scope and boundary conditions.– operational concept.– acceptance criteria.– descriptions of what is and what is not included.
• Discriminate critical Use Cases of the system.– primary scenarios of behaviour.
• Exhibit at least one candidate architecture.• Estimate overall cost.• Estimate risks.
![Page 19: Rational Unified Process](https://reader034.vdocuments.net/reader034/viewer/2022051414/559de9b31a28ab44148b460e/html5/thumbnails/19.jpg)
Object Oriented Design and Analysis
Inception activities
• Formulate scope of project• Plan and prepare a business case and evaluate
alternatives for risk management, staffing, project plan
• Synthesise a candidate architecture.
![Page 20: Rational Unified Process](https://reader034.vdocuments.net/reader034/viewer/2022051414/559de9b31a28ab44148b460e/html5/thumbnails/20.jpg)
Object Oriented Design and Analysis
Outcome of inception
• A ‘vision’ document, i.e., a general vision of the core projects requirements, key features and main constraints.
• A Use-Case model survey – all Use Cases and Actors that can be identified so far.
• An initial project glossary.• An initial business case including business context, success
criteria and financial forecast.• Initial risk assessment.• Project plan, with phases and iterations.
![Page 21: Rational Unified Process](https://reader034.vdocuments.net/reader034/viewer/2022051414/559de9b31a28ab44148b460e/html5/thumbnails/21.jpg)
Object Oriented Design and Analysis
Other artifacts produced
• Initial Use Case model (10%-20% complete)• A domain model static picture of scope.• A business model (if necessary)workflow.• A preliminary development case description to
specify the process used.• One or several prototypes.– Behavioral, Structural, Exploratory or Evolutionary.
![Page 22: Rational Unified Process](https://reader034.vdocuments.net/reader034/viewer/2022051414/559de9b31a28ab44148b460e/html5/thumbnails/22.jpg)
Object Oriented Design and Analysis
Evaluation criteria at end
• Agreement on scope definition and cost and schedule estimates
• Requirements understanding as shown by the correctness of the primary Use Cases.
• Credibility of the cost and schedule estimates, priorities, risks and development process.
• Depth and breadth of any architectural prototype that was developed.
• Actual expenditure v planned expenditure.
![Page 23: Rational Unified Process](https://reader034.vdocuments.net/reader034/viewer/2022051414/559de9b31a28ab44148b460e/html5/thumbnails/23.jpg)
Object Oriented Design and Analysis
Elaboration objectives
• To analyse the problem domain.• Establish a sound architectural foundation.• Develop the project plan.• Eliminate high-risk elements.
![Page 24: Rational Unified Process](https://reader034.vdocuments.net/reader034/viewer/2022051414/559de9b31a28ab44148b460e/html5/thumbnails/24.jpg)
Object Oriented Design and Analysis
Elaboration objectives
• Define, validate and agree the architecture as quickly as possible.
• Agree the vision that came from the inception phase.
• Agree a plan for the construction phase.• Demonstrate that the architecture will
support this vision for a reasonable cost in a reasonable time.
![Page 25: Rational Unified Process](https://reader034.vdocuments.net/reader034/viewer/2022051414/559de9b31a28ab44148b460e/html5/thumbnails/25.jpg)
Object Oriented Design and Analysis
Elaboration activities
• The vision is elaborated and a solid understanding is established of the most critical Use Cases that drive the architectural and planning decisions.
• The Process, the infrastructure and the development environment are elaborated, and the process, tools and automation support are put into place.
![Page 26: Rational Unified Process](https://reader034.vdocuments.net/reader034/viewer/2022051414/559de9b31a28ab44148b460e/html5/thumbnails/26.jpg)
Object Oriented Design and Analysis
Elaboration activities
• The architecture is elaborated and components are selected. – Potential components are evaluated.– make / buy / reuse decisions determine the
construction phase cost and schedule.– Architectural components integrated and
assessed against primary scenarios.– This is done iteratively.
![Page 27: Rational Unified Process](https://reader034.vdocuments.net/reader034/viewer/2022051414/559de9b31a28ab44148b460e/html5/thumbnails/27.jpg)
Object Oriented Design and Analysis
Outcome of elaboration
• Use Case model (at least 80% complete).– All Use Cases identified.– All Actors identified.– Most Use-Case descriptions developed.
• Supplementary requirements.– (non-functional or not associated with a Use
Case)
• Software architecture description.
![Page 28: Rational Unified Process](https://reader034.vdocuments.net/reader034/viewer/2022051414/559de9b31a28ab44148b460e/html5/thumbnails/28.jpg)
Object Oriented Design and Analysis
Outcome of elaboration
• Executable architectural prototype.• Revised risk list and revised business case.• Development plan for overall project.– coarse grained project plan, with iterations and
evaluation criteria for each iteration.• Updated development case that specifies
process to be used.• Preliminary user manual (optional).
![Page 29: Rational Unified Process](https://reader034.vdocuments.net/reader034/viewer/2022051414/559de9b31a28ab44148b460e/html5/thumbnails/29.jpg)
Object Oriented Design and Analysis
Evaluation criteria at end
• Is the vision of the product stable?• Is the architecture stable?• Does the executable demonstration show
that major risk elements are addressed?• Is construction phase sufficiently planned?• Do all stakeholders agree that current
vision is achievable, using current plan with current architecture?
• Is the cost acceptable?
![Page 30: Rational Unified Process](https://reader034.vdocuments.net/reader034/viewer/2022051414/559de9b31a28ab44148b460e/html5/thumbnails/30.jpg)
Object Oriented Design and Analysis
Construction
• All remaining components and application features are developed and integrated into the product.
• All features are tested thoroughly.• Emphasis is placed on managing resources and
controlling operations to optimise cost, schedules and quality.
• Parallel construction can accelerate the availability of deployable releases.
![Page 31: Rational Unified Process](https://reader034.vdocuments.net/reader034/viewer/2022051414/559de9b31a28ab44148b460e/html5/thumbnails/31.jpg)
Object Oriented Design and Analysis
Construction objectives
• Minimise development costs by optimising resources and avoiding unnecessary scrap and rework.
• Achieve adequate quality as rapidly as possible.
• Achieve useful versions (alpha, beta or other test releases) as rapidly as practical.
![Page 32: Rational Unified Process](https://reader034.vdocuments.net/reader034/viewer/2022051414/559de9b31a28ab44148b460e/html5/thumbnails/32.jpg)
Object Oriented Design and Analysis
Construction activities
• Resource management, resource control, process optimisation.
• Complete component development and testing against the defined evaluation criteria.
• Assessment of product releases against acceptance criteria for the vision.
![Page 33: Rational Unified Process](https://reader034.vdocuments.net/reader034/viewer/2022051414/559de9b31a28ab44148b460e/html5/thumbnails/33.jpg)
Object Oriented Design and Analysis
Outcome of construction
• A product ready to put into the hands of end users.
• The software product integrated on the adequate platforms.
• The user manuals.• A description of the current release.
![Page 34: Rational Unified Process](https://reader034.vdocuments.net/reader034/viewer/2022051414/559de9b31a28ab44148b460e/html5/thumbnails/34.jpg)
Object Oriented Design and Analysis
Evaluation criteria at end
• Often called the beta release, is it ready?– Is the product release stable and mature enough to be
deployed in the user community?– Are all stakeholders ready for the transition into the use
community?– Are the actual resource expenditures v planned
expenditures still acceptable?
• Transition may have to be postponed by one release if the project fails to reach this milestone.
![Page 35: Rational Unified Process](https://reader034.vdocuments.net/reader034/viewer/2022051414/559de9b31a28ab44148b460e/html5/thumbnails/35.jpg)
Object Oriented Design and Analysis
Transition
• This moves the software project to the user community.
• After release, issues usually arise that require new releases, either to correct problems or finish features that were postponed.
• This phase is entered when a baseline is mature enough to be deployed in the end-user domain.
• This means that some usable subset of the system has beem completed to an acceptable level of quality and that user documentation is available.
![Page 36: Rational Unified Process](https://reader034.vdocuments.net/reader034/viewer/2022051414/559de9b31a28ab44148b460e/html5/thumbnails/36.jpg)
Object Oriented Design and Analysis
Transition phase includes
• Beta testing to validate the new system against use expectations.
• Parallel operation with the legacy system that the project is replacing
• Conversion of operational databases.• Training of users and maintainers.• Rollout of the product to the marketing, distribution
and sales teams.• It concludes when the deployment baseline has
achieved the completed vision.
![Page 37: Rational Unified Process](https://reader034.vdocuments.net/reader034/viewer/2022051414/559de9b31a28ab44148b460e/html5/thumbnails/37.jpg)
Object Oriented Design and Analysis
Transition objectives
• Achieve user self-supportability.• Achieve stakeholder concurrence that
deployment baselines are complete and consistent with the evaluation criteria of the vision.
• Achieve final product baseline as rapidly and cost-effectively as practical.
![Page 38: Rational Unified Process](https://reader034.vdocuments.net/reader034/viewer/2022051414/559de9b31a28ab44148b460e/html5/thumbnails/38.jpg)
Object Oriented Design and Analysis
Transition activities• Deployment-specific engineering, i.e. cutover,
commercial packaging and production, sales rollout, and field personnel training.
• Tuning activities, including bug fixing and enhancement for performance and usability.
• Assessing the deployment baselines against the vision and the acceptance criteria for the product.
• The activities depend on the goal – For fixing bugs, implementation and testing are usually
enough.– For new features, iteration is similar to construction phase.
![Page 39: Rational Unified Process](https://reader034.vdocuments.net/reader034/viewer/2022051414/559de9b31a28ab44148b460e/html5/thumbnails/39.jpg)
Object Oriented Design and Analysis
Evaluation criteria at end
• Is user satisfied?• Are the actual resources expenditures v
planned expenditures still acceptable?
![Page 40: Rational Unified Process](https://reader034.vdocuments.net/reader034/viewer/2022051414/559de9b31a28ab44148b460e/html5/thumbnails/40.jpg)
Object Oriented Design and Analysis
Thank you