70 likes | 174 Views
Unified Process. A summary based on the book “Applying UML and Patterns” by Craig Larman. UP Phases*. Inception – approximate vision, business case, scope, vague estimates Should we continue with this?
E N D
Unified Process A summary based on the book “Applying UML and Patterns” by Craig Larman
UP Phases* • Inception – approximate vision, business case, scope, vague estimates • Should we continue with this? • Elaboration – refined vision, iterative implementation of the core architecture, resolution of high risks, identification of most requirements and scope, more realistic estimates • Construction – iterative implementation of the remaining lower risk and easier elements, and preparation for deployment • Transition – beta test, deployment *Larman, page 33
Inception • Analysis of approximately 10% of use cases • Creation of business case • Preparation of the development environment “…the idea is to do just enough investigation to form a rational, justifiable opinion of the overall purpose and feasibility of the potential new system, and decide if it is worthwhile to invest in deeper exploration.” - Larman
Inception Artifacts • Vision and Business Case • High-level goals • Business Case • Use-Case Model • 10% of use cases in detail • Most use cases identified • Supplementary Specification • Non-functional requirements • Glossary • Domain and data dictionary • Risk List & Risk Management Plan • Risks and ideas for their mitigation • Prototypes and proof-of-concepts • Might include actual code • Validate technical ideas • Iteration Plan • Iteration plan for first iteration in the Elaboration phase • Phase Plan & Software development plan • Low-precision guess for elaboration phase duration and effort • Development Case • Description of customized UP steps and artifacts for this project
Elaboration • Summary – • Build the core architecture, resolve the high-risk elements, define most requirements, and estimate overall schedule and resources • Core, risky software is programmed and tested. (not prototypes) • Majority of requirements are discovered • Risks are mitigated or retired • Often two or more iterations (two to six weeks each (timeboxed))
Elaboration best Practices • Do short timeboxed risk-driven iterations • Start programming early • Design, implement and test core risky parts • Test early, often, realistically • Adapt based on feedback from tests, users, developers • Write most of the use cases and other requirements in detail, through a series of workshops, once per elaboration iteration
Artifacts Started in Elaboration • Domain Model • Visualization of the domain concepts • Design Model • Set of diagrams that describe the logical design • Software class diagrams • Object interaction diagrams • Package diagrams • Software Architecture Document • Learning aid that summarizes the key architectural issues and their resolution in the design • Use-Case Storyboards • UI Prototypes http://ribler_r.web.lynchburg.edu/cs350/UserInterfaceDesign.pptx