DEV475 Mastering Object-Oriented Analysis and Design with UML ...
Share Embed Flag
Download ePaper

DEV475 Mastering Object-Oriented Analysis and Design with UML ...

DEV475 Mastering Object-Oriented Analysis and Design with UML ... DEV475 Mastering Object-Oriented Analysis and Design with UML ...

crnarupa.singidunum.ac.rs
from crnarupa.singidunum.ac.rs More from this publisher
12.07.2015 Views

DEV475 Mastering Object-Oriented Analysis and Design with UMLProcess Structure - Lifecycle PhasesProcess Structure - Lifecycle PhasesInception Elaboration Construction TransitiontimeRational Unified Process has four phases:• Inception - Define the scope of project• Elaboration - Plan project, specify features andbaseline architecture• Construction - Build the product• Transition - Transition the product into end-usercommunityMastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved36During Inception, we define the scope of the project: what is included and what isnot. We do this by identifying all the actors and use cases, and by drafting the mostessential use cases (typically 20% of the complete model). A business plan isdeveloped to determine whether resources should be committed to the project.During Elaboration, we focus on two things: getting a good grasp of the requirements(80% complete) and establishing an architectural baseline. If we have a good grasp ofthe requirements and the architecture, we can eliminate a lot of the risks, and we willhave a good idea of how much work remains to be done. We can make detailedcost/resource estimations at the end of Elaboration.During Construction, we build the product in several iterations up to a beta release.During Transition, we move the product to the end user and focus on end-usertraining, installation, and support.The amount of time spent in each phase varies. For a complex project with manytechnical unknowns and unclear requirements, Elaboration may include three-to-fiveiterations. For a simple project, where requirements are known and the architectureis simple, Elaboration may include only a single iteration.1 - 36

Module 1 - Best Practices of Software EngineeringPhase Boundaries Mark Major MilestonesPhase Boundaries Mark Major MilestonesInception Elaboration Construction TransitiontimeLifecycleObjectiveMilestone(LCO)LifecycleArchitectureMilestone(LCA)Initial OperationalCapabilityMilestone(IOC)ProductReleaseMastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved37At each of the major milestones, we review the project and decide whether toproceed with it as planned, to cancel the it, or to revise it. The criteria used to makethese decisions vary by phase.LCO: scope is agreed upon and risks are understood and reasonableLCA: high risks are addressed and architecture is stableIOC: product is complete and quality is acceptableThe evaluation criteria for the Inception phase (LCO) include: stakeholderconcurrence on scope definition and cost/schedule estimates; requirementsunderstanding as evidenced by the fidelity of the primary use cases; credibility ofcost/schedule estimates, priorities, risks, and development process; depth andbreadth of any architectural prototype; actual expenditures versus plannedexpenditures.The evaluation criteria for the Elaboration phase (LCA) include: stability of theproduct vision and architecture; resolution of major risk elements; adequate planningand reasonable estimates for project completion; stakeholder acceptance of theproduct vision and project plan; and acceptable expenditure level.The evaluation criteria for the Construction phase (IOC) include: stability andmaturity of the product release (that is, is it ready to be deployed?); readiness of thestakeholders for the transition; and acceptable expenditure level.At the end of the Transition phase, we decide whether to release the product. Webase this primarily on the level of user satisfaction achieved during the Transitionphase. Often this milestone coincides with the initiation of another developmentcycle to improve or enhance the product. In many cases, this new development cyclemay already be underway.1 - 37

Module 1 - Best Practices of Software EngineeringPhase Boundaries Mark Major MilestonesPhase Boundaries Mark Major MilestonesInception Elaboration Construction TransitiontimeLifecycle<strong>Object</strong>iveMilestone(LCO)LifecycleArchitectureMilestone(LCA)Initial OperationalCapabilityMilestone(IOC)ProductRelease<strong>Mastering</strong> <strong>Object</strong> <strong>Oriented</strong> <strong>Analysis</strong> <strong>and</strong> <strong>Design</strong> <strong>with</strong> <strong>UML</strong>Copyright © 2003 Rational Software, all rights reserved37At each of the major milestones, we review the project <strong>and</strong> decide whether toproceed <strong>with</strong> it as planned, to cancel the it, or to revise it. The criteria used to makethese decisions vary by phase.LCO: scope is agreed upon <strong>and</strong> risks are understood <strong>and</strong> reasonableLCA: high risks are addressed <strong>and</strong> architecture is stableIOC: product is complete <strong>and</strong> quality is acceptableThe evaluation criteria for the Inception phase (LCO) include: stakeholderconcurrence on scope definition <strong>and</strong> cost/schedule estimates; requirementsunderst<strong>and</strong>ing as evidenced by the fidelity of the primary use cases; credibility ofcost/schedule estimates, priorities, risks, <strong>and</strong> development process; depth <strong>and</strong>breadth of any architectural prototype; actual expenditures versus plannedexpenditures.The evaluation criteria for the Elaboration phase (LCA) include: stability of theproduct vision <strong>and</strong> architecture; resolution of major risk elements; adequate planning<strong>and</strong> reasonable estimates for project completion; stakeholder acceptance of theproduct vision <strong>and</strong> project plan; <strong>and</strong> acceptable expenditure level.The evaluation criteria for the Construction phase (IOC) include: stability <strong>and</strong>maturity of the product release (that is, is it ready to be deployed?); readiness of thestakeholders for the transition; <strong>and</strong> acceptable expenditure level.At the end of the Transition phase, we decide whether to release the product. Webase this primarily on the level of user satisfaction achieved during the Transitionphase. Often this milestone coincides <strong>with</strong> the initiation of another developmentcycle to improve or enhance the product. In many cases, this new development cyclemay already be underway.1 - 37

logo

products

Resources

Company

Terms of service
Privacy policy
Cookie policy
Cookie settings
Imprint
Change language
Made with love in Switzerland
© 2024 Yumpu.com all rights reserved

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!