Unified Software Practices v 5.0-D Copyright  1998 Rational Software, all rights reserved 1 /26 RUP Architecture

Unified Software Practices v 5.0-D Copyright  1998 Rational Software, all rights reserved 2 /26 InceptionElaborationConstructionTransition Process Architecture - Lifecycle Phases The Unified Process has four phases: Have phases are described below and note what the expectation is at the end (milestone) of each phase.  Inception - Define the scope of project What is included; what is not; identify all actors and use cases; draft about 20% of essential use cases; High level identification. Lots of artifacts : Business Rules, Vision, desired Features, Domain Model, costs, schedule, Risk List, Business modeling, and more)  Elaboration - Plan project, Specify features, Baseline Architecture; have about 80% of essential requirements identified; (for us, use-cases) Good grasp of requirements and architecture. Most key analysis and design done. (often a couple of iterations…)  High risk items addressed and mitigated time

Unified Software Practices v 5.0-D Copyright  1998 Rational Software, all rights reserved 3 /26 InceptionElaborationConstructionTransition Process Architecture - Lifecycle Phases The Unified Process has four phases: At the milestones, we have:  Construction - Build the product via several iterations; up to beta release; Essentially programming and unit test; iterations; assessment, … Several iterations (t ime-boxed )…  Transition - Transition the product to end user community; end-user training and support; installation, etc. Alpha testing Beta testing Get ready for total deployment time

Unified Software Practices v 5.0-D Copyright  1998 Rational Software, all rights reserved 4 /26 Number of Iterations?  Amount of time spent in each varies; sometimes 3-5 iterations in construction;  For a simple project – one iteration in elaboration; Can be very complex.  Most practitioners suggest six plus or minus three iterations!

Unified Software Practices v 5.0-D Copyright  1998 Rational Software, all rights reserved 5 /26 InceptionElaborationConstructionTransition Phase Boundaries Mark Major Milestones Lifecycle Objective Milestone Lifecycle Architecture Milestone Initial Operational Capability Milestone Product Release time At each of the major milestones, project is reviewed; decision made to proceed with project as planned, abort project, or to revise it. The criteria used to make this decision vary by phase. These are indeed milestones! (Minor milestones are at the end of iterations – coming) Lots of evaluation criteria as we move from phase to phase… (next overhead.) Note the titles of the Milestones.

Unified Software Practices v 5.0-D Copyright  1998 Rational Software, all rights reserved 6 /26 Major Milestones – Evaluation Criteria (at end of phase)  Inception Phase (Life Cycle Objective Milestone) includes:  Stakeholder concurrence on scope definition and cost/schedule estimates;  Business Model, business vision, and related business / domain related documents developed and verified.  Requirements understanding as evidenced by the fidelity of the primary Use-Cases of new application; Very high level.  Credibility of cost/schedule estimates, priorities, risks, and development process;  Clear vision of project  Depth and breadth of architectural prototype; High level.  Perhaps some basic modeling… actual expenditures versus planned expenditures  All stakeholders ‘on same page.’ Go - No-go decision.

Unified Software Practices v 5.0-D Copyright  1998 Rational Software, all rights reserved 7 /26 Major Milestones – Evaluation Criteria (at end of phase)  Elaboration phase (Life Cycle Architecture Milestone):  Stability of the product vision;  Resolution of major risk elements;  Adequate planning and reasonable estimates for project completion agreed upon; Note: we really don’t have a ‘time projection’ until this milestone.  Stakeholder acceptance of the product vision and project plan;  Acceptable expenditure level.  A base line architecture established. (note title of milestone!)  Around 80% of use cases captured, modeled, and understood.

Unified Software Practices v 5.0-D Copyright  1998 Rational Software, all rights reserved 8 /26 Major Milestones – Evaluation Criteria (at end of phase)  Construction phase (IOC – Initial Operational Capability Milestone)  stability and maturity of the product release (i.e., is it ready to be deployed? – ready to go into beta?);  readiness of the stakeholders for the transition; acceptable expenditure level.  Note, again, title of milestone Initial  Are we ready to ease into transitioning to the new application? alpha, beta testing training customer service transition plans established…. configuration management?

Unified Software Practices v 5.0-D Copyright  1998 Rational Software, all rights reserved 9 /26 Major Milestones – Evaluation Criteria (at end of phase)   Transition phase, (Product Release) - decision made whether to release the product.   Based primarily on the level of user satisfaction achieved during the transition phase. Note: considerable testing takes place during Transition.  Chance for remedial maintenance prior to release.  Often this milestone coincides with the initiation of another development cycle to improve or enhance the product. In many cases, new development cycle may already be underway.  This phase also includes training, user documentation, clean- up…

Unified Software Practices v 5.0-D Copyright  1998 Rational Software, all rights reserved 10 /26 Iterations and Phases – Closer Look at Process Architecture  An iteration is a distinct sequence of activities with an established plan and evaluation criteria, resulting in an ‘executable’ release (internal or external) and assessment of the iteration  An iteration is a distinct sequence of activities with an established plan and evaluation criteria, resulting in an ‘executable’ release (internal or external) and assessment of the iteration Number of iterations per phase is variable. Number of iterations per phase is variable. Each iteration can result in an executable release where the system Each iteration can result in an executable release where the system evolves into a large system. evolves into a large system. PreliminaryIterationArchitect.IterationArchitect.IterationDevel.IterationDevel.IterationDevel.IterationTransitionIterationTransitionIteration InceptionElaborationConstructionTransition Minor Milestones: Releases

Unified Software Practices v 5.0-D Copyright  1998 Rational Software, all rights reserved 11 /26 Major Core Disciplines (Activities) Produce Models: Analysis & Design Implementation Model Test Model realized by implemented by verified by Requirements Implementation Test Use-Case Model Design Model Business Modeling Business Use-Case Model Business Object Model The RUP is a model-driven approach; Models are needed to fully describe the application from viewpoints of different stakeholders. The business itself; generally larger than the application domain of project…, Business Vision, Business Rules, Domain Model… In more detail:

Unified Software Practices v 5.0-D Copyright  1998 Rational Software, all rights reserved 12 /26  Business Model  Business Model is a model of what the business processes are and the business environment. (Very Important!!) What is the application domain?  Use-Case Model models what the application is supposed to do and its environment. ( functional requirements )  Create Use Case diagrams (graphics); Use Case Narratives (Specification) (some key alternative / exception scenarios in use cases.)  Analysis and Design Model realizes the Use-Cases.  Serves as abstraction of the implementation model and its source code.  Architecture-centric.  Implementation Model is a collection of components, and the implementation subsystems that contain them.  Primarily programming – realizing the design model; unit testing and more.  Test Model encompasses all of the test cases and procedures required to test the system. (test plans; test scripts; test suites, etc.)  Development team verification; user validation

Unified Software Practices v 5.0-D Copyright  1998 Rational Software, all rights reserved 13 /26 Bringing It All Together: The Iterative Model Project Management Environment Business Modeling Implementation Test Analysis & Design Preliminary Iteration(s) Iter. #1 Phases Core Process Disciplines Iterations Core Supporting Disciplines Iter. #2 Iter. #n Iter. #n+1 Iter. #n+2 Iter. #m Iter. #m+1 Deployment Configuration & Change Mgmt Requirements ElaborationTransitionInceptionConstruction In an iteration, you walk through all disciplines. Relative amount of color shows level of activity in each iteration Development Team Focus

Unified Software Practices v 5.0-D Copyright  1998 Rational Software, all rights reserved 14 /26 Process Notation – Figures used in the RUP Role Activity Artifact Describe a Use-Case Use-Case Package Use-Case responsible for Use-Case Specifier A work item - a worker may be asked to perform A piece of information that is produced, modified, or used by a process A role that may be played by an individual or a team in the development organization Could be source code, documents, class, risks list, glossary, sequence diagram…etc. Part of the Configuration Smallest piece of work that is relevant. Workload divided by activities needed. Defines the behavior and responsibilities of an individual or a group working as a team. In the RUP, a Worker is more of a ‘role’ that defines how individuals should carry out work. kept in a Package (repository)

Unified Software Practices v 5.0-D Copyright  1998 Rational Software, all rights reserved 15 /26 Resource Paul Mary Joe Sylvia Stefan Workers Are Used for Resource Planning Each individual in the project is assigned to one or several workers / roles Worker (role) Designer Use-Case Specifier System Analyst Implementer Architect Activities (work items) Define Operations Detail a Use-Case Find Actors and Use-Cases Perform Unit Tests Identify Design Mechanisms A worker may wear several hats. all in same day… Some ‘roles’ are accomplished by a team. Often the case…

Unified Software Practices v 5.0-D Copyright  1998 Rational Software, all rights reserved 16 /26  The Unified Modeling Language (UML) is a language for specifying, visualizing, constructing, and documenting the artifacts of a software-intensive system  A software development process defines Who is doing What, When and How in building a software product  The Rational Unified Process has four phases: Inception, Elaboration, Construction and Transition  Each phase ends at a major milestone and contains one or more iterations  An iteration is a distinct sequence of activities with an established plan and evaluation criteria, resulting in an executable release Summary: Rational Unified Process (1 of 2)

Unified Software Practices v 5.0-D Copyright  1998 Rational Software, all rights reserved 17 /26 Summary (cont.): Rational Unified Process   An artifact is a piece of information that is produced, modified, or used by a process   A worker is a role that may be played by an individual or a team in the development organization   An activity or work item is a unit of work a worker may be asked to perform