CS4272-1 Rational Unified Process zThe Unified Software Development Process by Ivar Jacobson, Grady...
Embed Size (px)
Transcript of CS4272-1 Rational Unified Process zThe Unified Software Development Process by Ivar Jacobson, Grady...
- Slide 1
CS4272-1 Rational Unified Process zThe Unified Software Development Process by Ivar Jacobson, Grady Booch, and James Rumbaugh zThe Rational Unified Process: An Introduction, by Philippe Kruchten zThe Rational Unified Process Made Easy, by Per Kroll and Philippe Kruchten Slide 2 CS4272-2 SEI Capability Maturity Model 1. Initial - anything goes 2. Repeatable - SCM, QA, planning, tracking, requirements 3. Defined - process defined and followed 4. Managed - measure and act on it 5. Optimizing - keep improving process Slide 3 3 Best Practices: z Develop software iteratively z Manage requirements 3Use component-based architectures 3Visually model software z Verify software quality z Control changes to software Slide 4 CS4272-4 Develop Iteratively zWaterfall yRequirements yHigh level design yLow level design yImplementation yTesting zIterative development all activities at the same time Slide 5 CS4272-5 Components of RUP Artifacts - what (things people make) Roles - who (roles people play) Activities - how (things people do) Workflows - when Slide 6 CS4272-6 Artifacts zVision statement zIteration plan zUse-case model (UML) zSoftware architecture document (UML) zDesign model (UML) zComponent zIntegration build plan Slide 7 CS4272-7 Roles zProject manager zArchitect zSystem analyst zUse-case specifier zDesigner zImplementor zTester zCM manager Slide 8 CS4272-8 Activities zPlan subsystem integration zImplement classes zFix a defect zPerform a unit test zReview code zIntegrate subsystem Slide 9 CS4272-9 Workflows zProject management zBusiness modeling zRequirements zAnalysis and design zImplementation Slide 10 CS4272-10 Workflows zTest zConfiguration and change management zDeployment zEnvironment Slide 11 CS4272-11 Implementation Workflow Slide 12 CS4272-12 Iterations Preliminary It.Iter. 1Iter. 2Iter. 3Iter. 7Iter. 8Iter. 9 ElaborationInceptionConstructionTransition Slide 13 CS4272-13 Four phases zInception yget the idea, initial planning zElaboration ycreate the architecture ybuild skeleton system ydetailed planning zConstruction ybuild the rest of the system zTransition Slide 14 CS4272-14 Iteration Plan zWhat are we going to do this iteration? zWho is going to do it? zWhat order are we going to do it? zDo we have enough resources? Slide 15 CS4272-15 An iteration workflow zEach iteration uses some of the standard workflows yRequirements, design, implementation, test zWorkflows can run in parallel zEarly iterations yMuch project management yMuch business modeling yLittle implentation Slide 16 CS4272-16 Architecture zDescribes components and how they are connected. zComponent is system/subsystem zArchitect responsible for architecture zDevelopers responsible for components zElaboration phase writes code for the architecture Slide 17 CS4272-17 zManager zArchitect (technical lead) zBusiness experts y(systems analysis, use case specifier) zDevelopers y(designer, developer, tester, CMM manager) Slide 18 CS4272-18 Summary of RUP zDevelop software iteratively z Manage requirements 3Use component-based architectures 3Visually model software z Verify software quality z Control changes to software Slide 19 CS4272-19 Summary of RUP zComplicated process zFramework - you are not expected to do everything zDont focus so much on the process that you forget the product! Slide 20 CS4272-20 Keys to good software zGood people zUnderstand the problem zUnderstand the solution zEnough time zGood process Slide 21 CS4272-21 eXtreme Programming Spend two hours reading Extreme Programming Explained or reading http://c2.com/cgi/ wiki?ExtremeProgrammingRoadmap http://c2.com/cgi/ wiki?ExtremeProgrammingSummary http://www.xProgramming.com/ and http://www.extremeprogramming.org/