Rational Unified ProcessSEI Capability Maturity ModelBest Practices:Develop IterativelyComponents of RUPArtifactsRolesActivitiesWorkflowsSlide 10Implementation WorkflowIterationsFour phasesIteration PlanAn iteration workflowArchitectureSlide 17Summary of RUPSlide 19Keys to good softwareeXtreme ProgrammingCS427 2-1Rational Unified ProcessThe Unified Software Development Process by Ivar Jacobson, Grady Booch, and James RumbaughThe Rational Unified Process: An Introduction, by Philippe KruchtenThe Rational Unified Process Made Easy, by Per Kroll and Philippe KruchtenCS427 2-2SEI Capability Maturity Model1. Initial - anything goes2. Repeatable - SCM, QA, planning, tracking, requirements3. Defined - process defined and followed4. Managed - measure and act on it5. Optimizing - keep improving processCS427 2-3Best Practices: Develop software iteratively Manage requirementsUse component-based architecturesVisually model software Verify software quality Control changes to softwareCS427 2-4Develop IterativelyWaterfallRequirementsHigh level designLow level designImplementationTestingIterative development – all activities at the same timeCS427 2-5Components of RUPArtifacts - what(things people make)Roles - who(roles people play)Activities - how(things people do)Workflows - whenCS427 2-6ArtifactsVision statementIteration planUse-case model (UML)Software architecture document (UML)Design model (UML)ComponentIntegration build planCS427 2-7RolesProject managerArchitectSystem analystUse-case specifierDesignerImplementorTesterCM managerCS427 2-8ActivitiesPlan subsystem integrationImplement classesFix a defectPerform a unit testReview codeIntegrate subsystemCS427 2-9WorkflowsProject management Business modelingRequirementsAnalysis and designImplementationCS427 2-10WorkflowsTestConfiguration and change managementDeploymentEnvironmentCS427 2-11Implementation WorkflowA r c h i t e c tS y s t e m I n t e g r a t o rI m p l e m e n t o rC o d e r e v i e w e rP l a n S y s t e mI n t e g r a t i o nD e f i n eO r g a n i z a t i o no f S u b s y s t e mP l a nS u b s y s t e mI n t e g r a t i o nI m p l e m e n tC l a s s e sF i x a d e f e c tP e r f o r m U n i tT e s tR e v i e w c o d eI n t e g r a t es u b s y s t e mI n t e g r a t es y s t e mCS427 2-12IterationsPreliminary It. Iter. 1 Iter. 2 Iter. 3 Iter. 7 Iter. 8 Iter. 9ElaborationInception Construction TransitionCS427 2-13Four phasesInception get the idea, initial planningElaboration create the architecture build skeleton systemdetailed planningConstructionbuild the rest of the systemTransitionCS427 2-14Iteration PlanWhat are we going to do this iteration?Who is going to do it?What order are we going to do it?Do we have enough resources?CS427 2-15An iteration workflowEach iteration uses some of the standard workflowsRequirements, design, implementation, testWorkflows can run in parallelEarly iterationsMuch project managementMuch business modelingLittle implentationCS427 2-16ArchitectureDescribes components and how they are connected.Component is system/subsystemArchitect responsible for architectureDevelopers responsible for componentsElaboration phase writes code for the architectureCS427 2-17ManagerArchitect (technical lead)Business experts(systems analysis, use case specifier)Developers(designer, developer, tester, CMM manager)CS427 2-18Summary of RUPDevelop software iteratively Manage requirementsUse component-based architecturesVisually model software Verify software quality Control changes to softwareCS427 2-19Summary of RUPComplicated processFramework - you are not expected to do everythingDon’t focus so much on the process that you forget the product!CS427 2-20Keys to good softwareGood peopleUnderstand the problemUnderstand the solutionEnough timeGood processCS427 2-21eXtreme ProgrammingSpend two hours reading “Extreme Programming Explained” or readinghttp://c2.com/cgi/ wiki?ExtremeProgrammingRoadmaphttp://c2.com/cgi/ wiki?ExtremeProgrammingSummaryhttp://www.xProgramming.com/and