Unified ProcessOutlinePrefaceReasons for UPPrecursor of UPWhat does UP do?Slide 7History of UP 1History of UP 2About authorsSlide 113 Key Aspects of UPI. Use-Case Driven 3 Terminologies Initiate AND bindII. Architecture-Centric Simplified Process Use case & ArchitectureIII. Iterative and Incremental ?? Benefits to controlled iterationRelationship of 3 conceptsSlide 22Lifecycle of UPPhases within the cycleEnd of a CycleFor New CycleSlide 27Phase I --> InceptionPhase II --> ElaborationPhase III --> ConstructionPhase IV --> TransitionModeling Disciplines of UPSlide 33RUP and UPRational Corporate IntroductionUML and RUPSuccessful CasesRUP view IRUP view IIBuild Web Solutions with RUPPowerPoint PresentationSlide 42RUP DemosRUP strengthsRUP weaknessesSlide 46Extend RUP to EUPThe Lifecycle for the EUPTailored RUPAugmented lifecycle for the EUPMilestones & PhasePhase V --> ProductionPhase VI --> RetirementSlide 54ConclusionSlide 561Unified ProcessUnified ProcessPresented by Jing Zou May 9, 2003An Introduction2Outline Outline • UP INTRODUCTION(what and why)• UP HISTORY• THREE KEY ASPECTS• LIFECYCLE OF UP• RUP• EUP• CONCLUSION3PrefacePrefaceGood Start  Unified Process (UP) is a de facto standard development process within the object-oriented andcomponent-based software communities.Product  Rational Unified Process (RUP) More Needed  Enterprise Unified Process (EUP) is a software process that reflects the full lifecycle of software-based systems.4Reasons for UPReasons for UP1) Software becomes more complex and is updated fast2) Software developers uses methods that are as old as 25 years ago.3) Development process is diverse5Precursor of UPPrecursor of UPSet of activities to transform a user’s requirements into a software.Software development Process (diversity)User’s RequirementSoftware SystemUP6What does UP do?What does UP do?1) Provides guidance to the order of team’s activities2) Integrates team’s work and individual’s work3) Specifies artifacts4) Offers criteria for monitoring and measuring7Outline Outline • UP INTRODUCTION(what and why)• UP HISTORY• THREE KEY ASPECTS• LIFECYCLE OF UP• RUP• EUP• CONCLUSION8History of UP 1History of UP 19History of UP 2History of UP 210About authors About authors Ivar JacobsonGrady BoochJames Rumbaugh11Outline Outline • UP INTRODUCTION(what and why)• UP HISTORY• THREE KEY ASPECTS• LIFECYCLE OF UP• RUP• EUP• CONCLUSION123 Key Aspects of UP3 Key Aspects of UP1) Use-case driven2) Architecture-centric3) Iterative and incremental13I. Use-Case DrivenI. Use-Case DrivenUse-Case driven means:Development process proceeds through aseries of workflows that derive from use cases.14 3 Terminologies3 TerminologiesUsers: someone or something that interact with system.Use Case: interaction between users and system,---what is the system supposed to do for each user?Use Case Model: collection of use cases; description of complete functionality15 Initiate AND bindInitiate AND bind1) Tool for specifying requirements 2) Driving design3) Source for testing16II. Architecture-CentricII. Architecture-CentricArchitecture is the view of the whole design with key Characteristics and without too many details  Only 5-10% use cases  growth with use case in parallel (structure and function)17 Simplified ProcessSimplified Process1) Rough outline (use case independent)2) Subset of the identified use cases (5-10%)3) More use cases specified, more architecture discovered18 Use case & ArchitectureUse case & ArchitectureUse caseSystem architecturedrive influence19III. Iterative and Incremental ??III. Iterative and Incremental ??Iteration: Steps in the workflow (mini-project)  Create a design for relevant use cases  Implement with components  Required iteration in logical order for economyIncrements: Growth in the product (might not be additive)20 Benefits to controlled iterationBenefits to controlled iteration1) Reduce the cost risk to the expenditures on a single increment2) Reduce the risk of delayed product delivery (find the risks earlier)3) Speed up the tempo of the whole development effort 4) Easier to adapt to the requirement modification21Relationship of 3 conceptsRelationship of 3 conceptsGoalsdefinedriveguideUSE CASEITERATIONARCHITECTUREdriveinfluence22Outline Outline • UP INTRODUCTION(what and why)• UP HISTORY• THREE KEY ASPECTS• LIFECYCLE OF UP• RUP• EUP• CONCLUSION23Lifecycle of UPLifecycle of UP• Each cycle concludes with a product release to customers.• Each cycle consists of 4 phases:1) Inception 2) Elaboration3) Construction4) Transition24Phases within the cyclePhases within the cycleX-abscissaY-ordinate25End of a CycleEnd of a CycleAt the end, a software product is releasableFinished product includes 1) requirements2) use cases3) nonfunctional requirements4) test cases5) artifacts modeled by the UML26For New CycleFor New CycleFor every new cycle, we need• Use-case model• Analysis model• Design model• Implementation Model• Deployment model• Test model• Representation of the architecture27Phases within the cyclePhases within the cycleX-abscissaY-ordinate28Phase I --> Inception Phase I --> Inception -Establish goals-Build business case-Identify essential system requirement-Initiate risk management(cost, time, political environment )• Develop a good idea into a vision of the end product• Business case for the product is presented29Phase II --> ElaborationPhase II --> ElaborationHere, architecture is expressed as a view of different models- Develop architecture- Capture functional requirements as use cases- Identify non-functional requirements- Plan the construction- Continue risk management30Phase III --> ConstructionPhase III --> ConstructionMuscle built : software added to the architecture- Build the System- Maintain architectural integrity(Architecture is stable but might has minor changes)- Iterative, Incremental-However, is it sufficient to take early delivery?31Phase IV --> TransitionPhase IV --> TransitionProducts move to beta release. Trial Defects and deficiencies are reported. Corrections and improvements- Final testing( system, acceptance, beta )- Training customer personnel- Documentation, installation and consultation- Perform postmortem