170 likes | 583 Views
Rational Unified Process Key Concepts. Mike Woodard. Outline. The Spirit of RUP Risk Value Executable Going Through the Four Phases Inception Elaboration Construction Transition Iterative & Incremental. The Spirit of RUP - RISK.
E N D
Rational Unified ProcessKey Concepts Mike Woodard Mike Woodard
Outline • The Spirit of RUP • Risk • Value • Executable • Going Through the Four Phases • Inception • Elaboration • Construction • Transition • Iterative & Incremental Mike Woodard
The Spirit of RUP - RISK • Attack Major Risks Early and Continuously, or They Will Attack You • Risk Management begins before the project begins and continues beyond the life of the project. • Prioritize risk, dealing with the major/most difficult risk first. Combine both the business and technical view for prioritization. • Prioritize work based on risk. Mike Woodard
Spirit of RUP - VALUE • Ensure That You Deliver Value to Your Customer • Everything you produce should be focused on delivering value to the customer • Artifacts and documents have very little, if any, value to the customer. Executable code has value. Mike Woodard
Spirit of RUP - EXECUTABLE • Stay Focused on Executable Software • Deliver executable code as early as possible on your architecture where the customer can use it • Build your system with components • Test early and test often • Work as one team: business and technical together Mike Woodard
The Four Phases A RUP project has four phase each of which focuses on specific risks: • Inception: business risks • Elaboration: technical risk • Construction: integration risk • Transition: delivery risk Mike Woodard
Inception Phase • Understand what to build • Identify key system functionality • Determine at least one possible solution • Understand the Costs, Schedule, and Risks • Decide what process to follow and what tools to use • Should the Project Move Forward Mike Woodard
Elaboration Phase • Get a more detailed understanding of the requirements • Design, implement, validate, and baseline the architecture • Mitigate essential risk, and produce accurate schedule and cost estimates • Refine the development case, and put the development environment in place • Should the Project Move Forward Mike Woodard
Construction Phase • Minimize development costs and achieve some degree of parallelism • Iteratively develop a complete product that is ready to transition to its user community • Should the Project Move Forward Mike Woodard
Transition Phase • Beta test to validate that user expectations are met • Train users and maintainers to achieve user self-reliability • Prepare deployment site and convert operational databases • Prepare for launch: packaging, production, and marketing rollout • Achieve stakeholder concurrence that deployment is complete • Improve future project performance through lessons learned • The Project is Complete Mike Woodard
Iterative & Incremental • Iterative – a repeatable process – a set of task that are repeatedly applied within a process – doing the same steps repeatedly (iterations are typically 4 to 8 weeks) • Incremental – part of a whole – a piece of a product – a partial delivery (typically a piece of executable software that the customer can begin evaluating) Mike Woodard
Parallel not Sequential • Sample Iteration Activities Mike Woodard
References • Eclipse OpenUp http://epf.eclipse.org/wikis/openup/ • IBM Rational Development Works. http://www-128.ibm.com/developerworks/rational/ • Kroll, P & Kruchten, P. (2003). The Rational Unified Process Made Easy – A Practitioner’s Guide to the RUP. Addison-Wesley, New York, NY Mike Woodard