1September 10, 2008 Lecture 7 1CS 390 – Lecture 7The Phases of the Unified ProcessIncrements are identified as phases (Figure 3.1)September 10, 2008 Lecture 7 2The Phases of the Unified Process (2)The four increments are labeledInception phaseElaboration phaseConstruction phaseTransition phaseThe phases of the Unified Process are the incrementsSeptember 10, 2008 Lecture 7 3The Phases of the Unified Process (3)In theory, there could be any number of incrementsIn practice, development seems to consist of four incrementsEvery step performed in the Unified Process falls into One of the five core workflows and alsoOne of the four phasesSeptember 10, 2008 Lecture 7 4The Phases of the Unified Process (4)Why does each step have to be considered twice?Workflow: Technical context of a stepPhase: Business context of a stepSeptember 10, 2008 Lecture 7 5The Inception PhaseThe aim of the inception phase is to determine whether the proposed software product is economically viableSeptember 10, 2008 Lecture 7 6The Inception Phase (2)1.Gain an understanding of the domain2.Build the business model3.Delimit the scope of the proposed projectFocus on the subset of the business model that is covered by the proposed software product4.Begin to make the initial business case2September 10, 2008 Lecture 7 7The Inception Phase : The Initial Business CaseQuestions that need to be answered include:Is the proposed software product cost effective? How long will it take to obtain a return on investment? Alternatively, what will be the cost if the company decides not to develop the proposed software product?September 10, 2008 Lecture 7 8The Inception Phase : The Initial Business Case (2)If the software product is to be sold in the marketplace, have the necessary marketing studies been performed?Can the proposed software product be delivered in time? If the software product is to be developed to support the client organization’s own activities, what will be the impact if the proposed software product is delivered late?September 10, 2008 Lecture 7 9The Inception Phase : The Initial Business Case (3)What are the risks involved in developing the software product?How can these risks be mitigated? Does the team who will develop the proposed software product have the necessary experience? Is new hardware needed for this software product?If so, is there a risk that it will not be delivered in time?September 10, 2008 Lecture 7 10The Inception Phase : The Initial Business Case (4)If so, is there a way to mitigate that risk, perhaps by ordering back-up hardware from another supplier? Are software tools (Chapter 5) needed? Are they currently available? Do they have all the necessary functionality?Answers are needed by the end of the inception phase so that the initial business case can be madeSeptember 10, 2008 Lecture 7 11The Inception Phase: RisksThere are three major risk categories:Technical risks See earlier slideThe risk of not getting the requirements rightMitigated by performing the requirements workflow correctlyThe risk of not getting the architecture rightThe architecture may not be sufficiently robustSeptember 10, 2008 Lecture 7 12The Inception Phase: Risks (2)To mitigate all three classes of risksThe risks need to be ranked so that the critical risks are mitigated firstThis concludes the steps of the inception phase that fall under the requirements workflow3September 10, 2008 Lecture 7 13The Inception Phase: Analysis, Design WorkflowsA small amount of the analysis workflow may be performed during the inception phaseInformation needed for the design of the architecture is extractedAccordingly, a small amount of the design workflow may be performed, tooSeptember 10, 2008 Lecture 7 14The Inception Phase: Implementation WorkflowCoding is generally not performed during the inception phaseHowever, a proof-of-concept prototype is sometimes build to test the feasibility of constructing part of the software productSeptember 10, 2008 Lecture 7 15The Inception Phase: Test WorkflowThe test workflow commences almost at the start of the inception phaseThe aim is to ensure that the requirements have been accurately determinedSeptember 10, 2008 Lecture 7 16The Inception Phase: PlanningThere is insufficient information at the beginning of the inception phase to plan the entire developmentThe only planning that is done at the start of the project is the planning for the inception phase itselfFor the same reason, the only planning that can be done at the end of the inception phase is the plan for just the next phase, the elaboration phaseSeptember 10, 2008 Lecture 7 17The Inception Phase: DocumentationThe deliverables of the inception phase include:The initial version of the domain modelThe initial version of the business modelThe initial version of the requirements artifacts September 10, 2008 Lecture 7 18The Inception Phase: Documentation (2)A preliminary version of the analysis artifacts A preliminary version of the architectureThe initial list of risksThe initial ordering of the use cases (Chapter 10)The plan for the elaboration phaseThe initial version of the business case4September 10, 2008 Lecture 7 19The Inception Phase: The Initial Business Case (5)Obtaining the initial version of the business case is the overall aim of the inception phaseThis initial version incorporates A description of the scope of the software product Financial detailsIf the proposed software product is to be marketed, the business case will also include Revenue projections, market estimates, initial cost estimatesIf the software product is to be used in-house, the business case will includeThe initial cost–benefit analysisSeptember 10, 2008 Lecture 7 20The Elaboration PhaseThe aim of the elaboration phase is to refine the initial requirementsRefine the architectureMonitor the risks and refine their prioritiesRefine the business caseProduce the project management planThe major activities of the elaboration phase are refinements or elaborations of the previous phaseSeptember 10, 2008 Lecture 7 21The Tasks of the Elaboration PhaseThe tasks of the elaboration phase correspond to:All but completing the requirements workflow Performing virtually the entire analysis workflow Starting the design of the