Riskbased RUP Tailoring

1
Risk-based RUP Tailoring

• By Vu Nguyen
• CSCI577b Spring 05

2
Agenda

• Introduction
• Detail of risk-based RUP tailoring method
• Example applying the method to tailor test
  workflow
• Conclusion

3
Objective

• Propose a method for tailoring RUP using risk

4
Introduction
Project X Team size 5 Schedule6
months Process RUP
5
Introduction (cont)

• RUP covers almost all aspects of software
  development projects. But
• Not all aspects fit every project
• All artifacts are considered equally important
• Risk management is a important part of the
  process
• But it is unclear on how risk strategies are
  associated with artifacts and activities

6
Method Overview

• Basing on project risks to tailor RUP
• Artifacts
• Artifacts content
• Activities
• Time when to do things
• Input
• Risk management plan
• RUP-based organizational process templates
• Output
• Development case, tailoring spreadsheet
• Project specific process including templates,
  activities and times
• Consist of 2 steps

7
Step 1

• Tailor artifacts, activities and time
• Associate risk items with artifacts, activities
• Provide alternatives and rationale for tailoring

8
Step 2

• Update/Add templates
• Based on the tailoring in step 1, update
  corresponding templates
• Create new templates if they are not available in
  the organizational process
• The tailoring is performed at the end of each
  iteration when risks and risk plan are refined

9
Example Tailoring test workflow

• Project Data Mining of Digital Archive Usage
  Data, Team 7b
• Major risks related to testing
• RI001 - Scalability and performance support up
  to 130,000 objects
• RI002 - Personal shortfall 4 developers, 3
  IVVers
• RI003 - Analysis Report should reflect the usage
  patterns of Digital Archive

10
Tailoring artifacts

• Results
• 5 test artifacts are necessary (instead of 10
  artifacts)
• Focus on Section 5.x and 10.x of Test Plan
  Section 2.x of Test Evaluation Summary

11
Conclusion

• The method helps customize the process to better
  address risks
• It provides basis for evaluating the completeness
  of artifacts
• It helps focus on high-risk activities, artifacts
  and even sections of artifacts
• Challenge quality of the tailoring depends on
  goodness of risk assessment and planning

12
References

• 1 IBM, Rational Unified Process, Version
  2002.05.01.01, IBM
• 2 Barry W. Boehm, R. Turner, Using Risk to
  Balance Agile and Plan-Driven Methods, IEEE
  Computer, IEEE Computer Society, June 2003 (Vol.
  36, No.6), pp. 57-66
• 3 Barry W. Boehm, Tutorial Software Risk
  Management, IEEE Computer Society Press, 1989
• 4 Barry W. Boehm, Spiral Development
  Experience, Principles and Refinements, Special
  Report, CMU/SEI-2000-SR-008
• 5 Gary Pollice, Liz Augustine, Chris Lowe, Jas
  Madhur, Software Development for Small Teams A
  RUP-Centric Approach, Addison-Wesley, 2004.
• 6 John Cameron, Configurable Development
  Process, Communications of the ACM, March 2002,
  pp. 72-77

13
QA
14
Thanks!