Rational Unified Process – Part 2

1. Rational Unified Process – Part 2 Original slides modified for instructional purposes. Originally designed by Rational Software Corporation

2. Chapter 2 Text Introduction to Rational Unified Process - Continued CONTINUE to read the RUP, third edition, especially chapters 3-6 I assume you have very carefully read chapters 1 and 2 at a minimum.

3. time Process Architecture - Lifecycle Phases Inception Elaboration Construction Transition The Rational Unified Process has four phases: • 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; • Good grasp of requirements and architecture. • Reduce risk. • Most key analysis and design done. (often a couple of iterations…)

4. time Process Architecture - Lifecycle Phases Inception Elaboration Construction Transition The Rational Unified Process has four phases: • Construction - Build the product via several iterations; up to beta release; • Essentially more design, programming and unit test; • iterations; • assessment, … • Several iterations – all time-boxed… • Is product ready for beta testing, training, captured all functionality, etc.?? • Transition – • Transition the product to end user community; • end-user training and support; • installation, etc. • (Here again, lots of activities: clean up, plan next evolution?? etc.) • Product deployed at end of Transition.

5. UP Phases Overview – key elements within development.

6. Number of Iterations? • Amount of time spent in each varies; sometimes 3-5 iterations in construction; • Inception – usually ‘none’ or one • Elaboration – often two; may be more. Can be very complex. • Most practitioners suggest six plus or minus three iterations!

7. Inception Elaboration Construction Transition Lifecycle Objective Milestone Lifecycle Architecture Milestone Initial Operational Capability Milestone Product Release Phase Boundaries Mark Major Milestones time Note the titles of the Milestones. At each of the major milestones, the project is reviewed and a decision made as to whether to proceed with the project as planned, to abort the project, or to revise it. The criteria used to make this decision vary by phase. These are indeed MAJOR milestones! Lots of evaluation criteria as we move from phase to phase… (next overhead.)

8. Major Milestones – Evaluation Criteria (at end of phase) • Inception phase (LCO – Life Cycle Objective Milestone) include: • 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.

9. Major Milestones – Evaluation Criteria (at end of phase) • Elaboration phase (LCA Architecture Milestone) include: •  Resolution of major risk elements; •  Adequate planning; reasonable estimates for project completion; • Note: we really don’t have a ‘time projection’ until this milestone. •  A base line architecture established. (note title of milestone!) •  Around 80% of use cases captured, modeled, and understood. • Stability of the product vision; • Stakeholder acceptance of the product vision and project plan; • Acceptable expenditure level.

10. Major Milestones – Evaluation Criteria (at end of phase) • Constructionphase (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. •  Are we ready to ease into transitioning to the new application? • alpha, beta testing • training • customer service • transition plans established…. • configuration management?

11. Major Milestones – Evaluation Criteria (at end of phase) • Transitionphase, (Product Release) - a decision is made whether to release the product. This will be 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 / evolution to improve or enhance the product. In many cases, this new development cycle may already be underway. • This phase also includes training, user documentation, clean-up

12. Inception Elaboration Construction Transition Preliminary Iteration Architect. Iteration Architect. Iteration Devel. Iteration Devel. Iteration Devel. Iteration Transition Iteration Transition Iteration Iterations and Phases Minor Milestones: Releases • 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. • Each iteration can provides an ‘increment’ of business value as system evolves into a large system. • (I prefer the term ‘base-lining’ or ‘versioning’ vice executable release. )

13. Releases – Internal and External • An internal release is kept within the development environment and (optionally) demonstrated to the stakeholder community. (Depends on nature of iteration) • An external release is provided to stakeholders (usually users) for installation in their own environment. • May be for operational testing prior to Product Release, … • External releases are much more expensive (they require user documentation and technical support) and normally occur only during the transition phase. • Remember, • endsofaniteration marks a minor milestone. • end of aphasemarks a major milestone.

14. BusinessModeling Requirements Implementation Test :Major Disciplines (Activities) Produce Models: The business itself; generally larger than the application domain of project…, Business Vision, Business Rules, Domain Model… 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. realized by Use-CaseModel Analysis & Design implemented by DesignModel verified by ImplementationModel TestModel In more detail:

15. Major Models • The Business Model • A model of what the business processes are and the businessenvironment. • (Very Important!!) • What is the application domain? • It can be used to generate requirements on supporting information systems. • The Use-Case Model • A model of what the application is supposed to do and its environment. (functional requirements) •  Create Use Case diagrams and Use Case Narratives (Specification)

16. Major Models • The Analysis and Design Model may be considered an object model that realizes the Use-Cases. • Serves as abstraction of the implementation model and its source code. • Create analysis and design classes and interaction diagrams • Architecture-centric. • The Implementation Model • A collection of components, and the implementation subsystems that contain them. • Primarily programming – realizing the design model; unit testing and more.

17. Major Models • The 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

18. In an iteration, you walk through all disciplines. Relative amount of color shows level of activity in each iteration Disciplines group activities logically Bringing It All Together: The Iterative Model Development Team Focus Phases Core Process Disciplines Inception Elaboration Construction Transition Business Modeling Requirements Analysis & Design Implementation Test Deployment Core Supporting Disciplines Configuration & Change Mgmt Project Management Environment Preliminary Iteration(s) Iter.#1 Iter.#2 Iter.#n Iter.#n+1 Iter.#n+2 Iter.#m Iter.#m+1 Iterations

19. Summary these last two sets of slides: (1 of 2) • 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

20. Summary (cont.): • A discipline groups related activities together • Rational Team Concert is a framework within which the development activities are defined and executed • RTC can be used to manage agile planning, process definition, defect tracking, build management, and reporting. • Users can use the software to track and manage the relationships between artifacts and promote best practices for development and gather project information.