Arlow and Neustadt ch.21 What is the unified process? People are more important than any process. Good people with a good process will outperform good people with no process every time Grady Booch

Arlow and Neustadt ch.2 2

3 Problems with the waterfall model Incomplete requirements Changing requirements Discovering risks late in the developing process Difficult to extend and maintain Difficult to make projects and resource estimates

Arlow and Neustadt ch.2 4 Waterfall developing model Divided in phases Each phase starts when the previous has finished Integration Test Implementation Analysis and design Requirements

Arlow and Neustadt ch.2 5 Risk in the waterfall model i RISkRISk T I M E Integration Test Implementation Analysis and design Requirements

Arlow and Neustadt ch.2 6 A software development process A software development process defines WHO, WHAT and HOW of developing software. Unified Process is an software development Process often referred to as the Unified Process (UP)

Arlow and Neustadt ch.2 7 UP axioms Use case (requirements) and risk driven  Use cases direct the process  Handling of high-risk elements early in the process Which kind of risks do you think there are in a System development project? Architecture centric  Early implementation of core architectural elements Iterative and incremental  Each iteration contains all the elements of a normal system development process  Each iteration generates a baseline that comprises a partially complete version of the finale system

Arlow and Neustadt ch.2 8 Iterations workflows Requirements  Capturing what the system should do Analysis  Refining and structuring the requirements Design  Realizing the requirements in system architecture Implementation  Building the software Test  Verifying that the implementation works as desired

Arlow and Neustadt ch.2 9 Baselines and increments Every UP iteration generates a baseline  Internal release of reviewed and approved artifacts Provides an agreed basis for further review and development

Arlow and Neustadt ch.2 10 Risks T I M E Iteration 1 Iteration 3 Iteration 2 RISkRISk Risk in the waterfall model Risk in iterativ development

Arlow and Neustadt ch.2 11 UP structure Four phases:  Inception  Elaboration  Construction  Transition Each phase can have one or more iterations

Arlow and Neustadt ch.2 12 The unified process

Arlow and Neustadt ch.2 13 Phase:Inception Goal: Get the project of the ground  The goal is to achieve concurrence among all stakeholders on the lifecycle objectives for the project.  To get the project of the ground The primary objectives of the inception phase include:  Establishing feasibility  Creating a business case  Capturing essential requirements  Identifying critical risks  Estimating the overall cost and schedule for the entire project Focus on requirements and analysis Milestone: Life cycle objectives

Arlow and Neustadt ch.2 14 Phase:Elaboration Goals:  Create an executable archtectural baseline  Refine the risk assesment  Capture use cases to 80% of the functional requirements  Create a detailed plan for the construction phase Milestone: Life cycle architecture

Arlow and Neustadt ch.2 15 Phase:Construction Goals:  To complete all requirements, analysis and design into a final system. Focus:  Requirements Uncover missed requirements  Analysis Finish the analysis model  Design Finish the design model  Implementation Build the initial operational capability  Test Milestone: Initial Operational Capability

Arlow and Neustadt ch.2 16 Phase:Transition Starts when beta testning is completedand the system is deployed Goals:  Correct defects  Tailor the software to operate at the user site  Create manuals Milestone: product release