Presentation
How to Fail with the
Rational Unified Process:
Seven Steps to Pain and
Suffering
1
2
Unified Process (UP)
VS
Rational Unified Process (RUP)
UP
is generally used to describe the generic process, including those elements which are common to most refinements
UP is also used to avoid potential issues of copyright infringement since Rational
Unified Process and RUP are trademarks of IBM
3
Waterfall Approaches
VS
Unified Process
Waterfall Approaches
Unified Process
Prescriptive
• Insist on all steps being followed exactly
Adaptive
• Allows for change within certain guidelines
Sequential
• Completes each phase one after another and only once.
Iterative
• Completes the entire information system in successive iterations.
Leaves testing to the end of project lifecycle
Early iterations focus on requirements, later iterations on implementation and testing 4
Main Points
If you want to have a Spectacular Failure with the
RUP, there are seven steps that you can follow.
Step 1: Superimpose “Waterfall” thinking
Step 2: Apply the RUP as a Heavy, Predictive
Process
Step 3: Avoid Object Technology Skills
Step 4: Undervalue Adaptive Iterative
Development
Step 5: Avoid Mentors Who Understand Iterative
Development
Step 6: Adopt the RUP in a Big Bang
Step 7: Take Advice from Misinformed Sources
5
Step 1: Superimpose “Waterfall”
Thinking (1)
What
is “Waterfall” Thinking?
Follows a fixed order and only start next phase when current phase is completed
Waterfall
approach drew inspiration from what was known and familiar, such as engineering and construction in other domains, such as building
Do the Requirements, then do the Design, then Construct
6
7
8
Step 1: Superimpose “Waterfall”
Thinking (2)
Creeping
Requirements
Requirements that are not anticipated near the start
Very