1. J. Scott Hawker 2003-01-21p. 1Some material © Rational Corp. Rational Unified Process Overview See and use the RUP Browser on lab machines

2. J. Scott Hawker 2003-01-21p. 2Some material © Rational Corp. Software Engineering Process

3. J. Scott Hawker 2003-01-21p. 3Some material © Rational Corp. Features of RUP  Use-Case Driven  Requirements drive and focus development  The “function” of “function + form”  Architecture-Centric  The over-arching structure; the foundation of the design  The “form” of “function + form”  Iterative and Incremental  Step-wise, controlled growth through “mini-projects”  Each step reacts to current needs and risks

4. J. Scott Hawker 2003-01-21p. 4Some material © Rational Corp. Rational Unified Process time

5. J. Scott Hawker 2003-01-21p. 5Some material © Rational Corp. Phases  Four phases  Inception  Establish business case, system viability  Deliver life-cycle objectives  Elaboration  Establish feasibility and constraints: financial, schedule, technical, etc.  Deliver life-cycle architecture  Construction  Build the system  Deliver initial operational capability  Transition  Roll out the fully functional system to customers  Deliver product release

6. J. Scott Hawker 2003-01-21p. 6Some material © Rational Corp. Each Discipline Contributes a Particular Set of Models

7. J. Scott Hawker 2003-01-21p. 7Some material © Rational Corp. Artifacts

8. J. Scott Hawker 2003-01-21p. 8Some material © Rational Corp. Time and the Unified Process  In the Unified Process, time flows through phases, increments and iterations, not through the traditional workflows of requirements  design  implementation  test  Phase  Time between two major milestones – points at which management decides whether to proceed with development and to commit scope, budget and schedule to the next phase  Iteration  A “mini-project” that typically crosses all five workflows (disciplines)  Results in a release (internal or external)  May contain multiple increments -- builds  Increment  A small, manageable part of the system – a build  Usually the difference (“delta”) of functionality added to the results of a previous increment

9. J. Scott Hawker 2003-01-21p. 9Some material © Rational Corp. Deliverables  Increments (and phases) deliver artifacts  Align deliverables with the phases and iterations, not the disciplines  Each discipline will contribute to part of the deliverables  A given deliverable contains content from multiple disciplines  Example: Vision document has contributions from requirements and analysis (scope), design (architecture), and project management (schedule and risk)

10. J. Scott Hawker 2003-01-21p. 10Some material © Rational Corp. Iterative and Incremental  Small steps!  Iteratively go through each discipline  Plan a little  Specify, design and implement a little  Integrate, test and run each iteration a little  Assess and repeat (iterate), as necessary  Transform a delta (chunk) of users’ requirements into a delta (chunk) of software product  Mini-project: one step at a time  Each one includes planning, disciplines, environment support, etc.  Early increments build knowledge (reduce risk) of required functionality and technical viability. Later increments build product functionality  Risk-Driven  Each iteration adds an increment and demonstrates the reduction of the risks with which it was concerned

11. J. Scott Hawker 2003-01-21p. 11Some material © Rational Corp. Phases  Iterations help management plan, organize, monitor, and control (react to change in) the project  Iterations are organized into phases, each with staffing, funding, and scheduling requirements and entry and exit criteria

12. J. Scott Hawker 2003-01-21p. 12Some material © Rational Corp. Inception Phase  Inception Launches the Project  Make the business case to justify launching the project  Define scope  Define candidate architecture  Identify risks and develop risk management plan  Estimate cost, schedule, return on investment  Define development process and support

13. J. Scott Hawker 2003-01-21p. 13Some material © Rational Corp. Inception Phase Deliverables  Feature list  First version of business or domain model  First version of use case model, analysis model and (maybe) design model  First draft candidate architecture description with use case, analysis and design views  (Maybe) Proof-of-concept prototype  Initial risk list  Initial use case priority list  Initial project plan (for all phases)  First draft of business case  Stakeholder agreement to proceed or cancel

14. J. Scott Hawker 2003-01-21p. 14Some material © Rational Corp. Inception Phase Deliverables For this course  Feature list  First version of business or domain model  First version of use case model, analysis model and (maybe) design model  First draft candidate architecture description with use case, analysis and design views  (Maybe) Proof-of-concept prototype  Initial risk list  Initial use case priority list  Initial project plan (for all phases)  First draft of business case  Stakeholder agreement to proceed or cancel with priority sketch technical approach schedule state “why this project”

15. J. Scott Hawker 2003-01-21p. 15Some material © Rational Corp. Artifacts For this course

16. J. Scott Hawker 2003-01-21p. 16Some material © Rational Corp.  Note that the requirements and design are addressed simultaneously  Define and evolve requirements – problem space  Define and evolve solution  Design, implement, test

17. J. Scott Hawker 2003-01-21p. 17Some material © Rational Corp. A Layered Architecture Middleware Application Platform Functional Architecture Technical Architecture Operating Systems Networking etc. Distributed communications Databases Security User interface framework etc. Domain objects Business logic Workflow etc. Functional Requirements Non-functional (quality) Requirements

18. J. Scott Hawker 2003-01-21p. 18Some material © Rational Corp. Simultaneously Address Function and Form Define requirements Design solution Implement solution Test solution Application Model Elements Technical Model Elements Define requirements Design solution Implement solution Test solution Support Project Mgmt. Environment Tools & Methods Configuration/Change Mgmt. Scope 50% Prototype Scope 50% Feasible approach Prototype Business case Schedule estim. Cost estimate Risks known 100% 90% 100% of built Go/No Go Schedule Cost Risks managed Go/No Go Manage cost schedule risk 100% Go/No Go Customer support Manage scope change delivery Fix and maintain Inception Phase Elaboration Phase Construction Phase Transition Phase Defined 80% Funct. arch. 80% other 20% Impl. 20% Test 20% 100%  Define the function early  Build the form early = “completeness”