What is Rational Unified Process? • Rational Unified Process© (RUP) is a RATIONAL UNIFIED software engineering process • Goal: to ensure the production of high- PROCESS quality software that meets the needs of its end-users within a predictable schedule and budget • Developed and maintained by Rational® Software What is RUP (cont)? Best Practices • Enhances team productivity by providing team members with easy access to a knowledge base • RUP effectively deployment of six best – Guidelines practices, among others – Templates – Tools – Develop software iteratively • Creates and maintains models – semantically rich – Manage requirements representations of the software system under development – Use component-based architectures • Guides the team how to effectively use UML – Model software visually • Is supported by tools which automate large parts of the process – Verify software quality • Is a configurable process that can adapt to large and small teams and projects – Control change of software • Captures many of the industry best practices Overview of RUP The Time Dimension • Two dimensions, time and content • The software life-cycle is broken into cycles, each of which involves a new generation of the – The time dimension represents the progress product of the process as it is enacted, and is • Each cycle is divided into four phases in RUP expressed in terms of cycles, phases, – Inception phase iterations, and milestones. – Elaboration phase – Construction phase – The content dimension represents what is – Transition phase being done along the respective time • Each phase is concluded with a well-defined dimension. milestone – a point in time at which certain critical decisions must be made and key goals must have been achieved 1 Two Dimensions of RUP The Content Dimension • Core process workflows – Business model – Requirements – Analysis & design – Implementation –Test – Deployment The Content Dimension (cont) Some Details of Time Dimension • Core supporting workflows • Inception phase: establish the business case for – Configuration & change management the system and delimit the project scope – Identify all external entities with which the system will – Project management interact – Environment – Identify all use cases – Specify success criteria – Assess risks – Estimate resources needed – Develop a plan showing dates of major milestones Inception Phase (cont) Inception Phase (cont) • Outcome of the inception phase (milestone) • Project milestone: the Lifecycle Objectives – A vision document: a general vision of the core Milestone project’s requirements, key features, and main • Evaluation criteria constrains – Stakeholder concurrence on scope definition and – A initial use-case model (10%-20% complete) cost/schedule estimates – An initial project glossary – Requirements understanding as evidenced by the – An initial business case which includes business fidelity of the primary use cases context, success criteria (revenue projection, market – Credibility of the cost/schedule estimates, priorities, recognition …), and financial forecast risks, and development process – An initial risk assessment – Depth and breadth of any architectural prototype that – A project plan showing phases and iterations was developed – A business model if necessary – Actual expenditures versus planned expenditures – One or several prototypes 2 Elaboration Phase Elaboration Phase (cont) • Analyze the problem domain • The outcome of the elaboration phase – A use-case model (at least 80% complete) – all use cases and actors have been identified, most use case descriptions have • Establish a sound architectural foundation been developed • Develop the project plan – Supplementary requirements capturing the non-functional requirements and any requirements that are not associated with • Eliminate the highest risk elements of the a specific use case – A software architecture description project – An executable architecture prototype – A revised risk list and a revised business case • “mile wide and inch deep” view of the – A development plan for the overall project, including the coarse- system grained project plan, showing iterations and evaluation criteria for each iteration • An executable architecture prototype is – An updated development case specifying the process to be used built in one or more iterations – A preliminary user manual (optional) Elaboration Phase (cont) Construction Phase • Project milestone: the Lifecycle Architecture Milestone • All components are developed and integrated • Evaluation criteria into the product – Stability of the vision of the product • All features are thoroughly tested – Stability of the architecture – Demonstration of the executable showing that the major risk • Parallel constructions are possible, depending elements have been addressed and credibly resolved on the size of the project – Sufficiently detailed and accurate construction phase – Agreement of the stakeholders that the current vision is • The outcome of the construction phase achievable in the context of the current architecture – The software product integrated on the adequate – Actual resource expenditure versus planned expenditure platforms acceptable – The user manuals – A description of the current release Construction Phase (cont) Transition Phase • Project milestone: Initial Operational • Transition the software product to the user community Capability Milestone • Issues usually arise that require new releases, • Evaluation criteria correct problems, or finish the features that were postponed – Is this product release stable and mature • Primary objectives enough to be deployed in the user community – Achieving user self-supportability – Are all stakeholders ready for the transition – Achieving stakeholder concurrence that deployment baselines are complete and consistent with the into the user community evaluation criteria of the vision – Are the actual resource expenditures versus – Achieving final product baseline as rapidly and cost planned expenditures still acceptable effectively as practical 3 Transition Phase (cont) Transition Phase (cont) • Expected results • Project milestone: the Product Release – “beta testing” to validate the new system Milestone against user expectations • Evaluation criteria: – Parallel operation with a legacy system that it – Is the user satisfied is replacing – Are the actual resource expenditure versus – Conversion of the operational databases planned expenditure still acceptable – Training of users and maintainers – Roll-out the product to the marketing, distribution, and sales teams Iterations Time Distribution • Although no projects are the same, time distribution is • Each phase in RUP can be further divided roughly the following into iterations • Inception: effort 5% schedule 10% – Business modeling •An iteration is a complete development – Requirement loop resulting in a release (internal or • Elaboration: effort 20% schedule 30% – Analysis external) of an executable product –Design • Construction: effort 65% schedule 50% • A subset of the final product, which grows – Implementation incrementally from iteration to become the – Testing • Transition: effort 10% schedule 10% final system – Deployment Workers and Activities Life-cycle Artifacts • Worker: a worker defines the behavior and • RUP is not document-driven responsibilities of an individual, or a group of • Main artifact should be software product individuals working together as a team itself – One person can be in multiple roles • Documentation should remain lean and • Activity: an activity of a specific worker is a unit limited to the few that bring real value of work that an individual in that role may be asked to perform • Two main categories of artifacts besides the software • Artifact: an artifact is a piece of information that is produced, modified, or used by a process • Management artifacts and technical artifacts 4 Life-cycle Artifacts (cont) Life-cycle Artifacts (cont) • Management artifacts –An Organizational Policy document which is the codification of the • Technical artifacts organization’s process –A Vision document which describes the system level requirements, – User’s Manual: developed early in the life- qualities and priorities cycle –A Business Case document which describes the financial context, contract, projected return on investment and others – Software Documentation: preferably in the –A Development Plan document which contains in particular the overall iteration plan, and plan for the current and upcoming iteration form of self-documenting source code –An Evaluation Criteria document which contains the requirements, acceptance criteria and other specific technical objectives –A Software Architecture document: extracted – Release Description documents for each release from the software documentation describing – Deployment document which contains additional information useful for transition, training, installation, sales, and others the overall structure of the software, its – Status Assessment documents which contains periodic snapshots of decomposition in major elements, and project status with metrics of progress, staffing, expenditure, results, critical risks, actions items and others rationale for the key design decisions Workflows – the content dimension Workflows (cont) • Core process workflows • Business modeling: – Business model – Common language (vocabulary) between business – Requirements section and technical section – Analysis & design – Business use cases – Implementation • Requirements: –Test – What