1. Requirements Engineering Lecture 13
Jerzy Nawrocki
Requirements Engineering
Lecture 13
Risk Management
Copyright, 2000 © Jerzy R. Nawrocki
Requirements Eng., Lecture 13

2. J. Nawrocki, Requirements Eng.., Lecture 13
Jerzy Nawrocki
Plan of the lecture
Introduction
Selected risk factors
J. Nawrocki, Requirements Eng.., Lecture 13
Requirements Eng., Lecture 13

3. J. Nawrocki, Requirements Eng.., Lecture 13
Introduction
What is a risk?
J. Nawrocki, Requirements Eng.., Lecture 13

4. J. Nawrocki, Requirements Eng.., Lecture 13
Introduction
Two approaches to risk
Proactive
Reactive
J. Nawrocki, Requirements Eng.., Lecture 13

5. J. Nawrocki, Requirements Eng.., Lecture 13
Introduction
Risk description
Probability
Impact
catastrophic
critical
marginal
negligible
J. Nawrocki, Requirements Eng.., Lecture 13

6. J. Nawrocki, Requirements Eng.., Lecture 13
Introduction
RMMM
RMMM = Risk Mitigation, Monitoring, and Management
Mitigation= minimising the probability
Monitoring= observing factors/indicators
Management= if it happens ..
J. Nawrocki, Requirements Eng.., Lecture 13

7. J. Nawrocki, Requirements Eng.., Lecture 13
Introduction
Risk analysis
IBM: > 100 risk factors
For each risk factor an MMM plan.
Risk management becomes a project in itself!
Pareto analysis: the principle
J. Nawrocki, Requirements Eng.., Lecture 13

8. J. Nawrocki, Requirements Eng.., Lecture 13
Jerzy Nawrocki
Selected risk factors
Risk areas
General
Poor planning
Poor configuration control
Poor progress tracking
Poor quality assurance
Poor requirements
Poor development
J. Nawrocki, Requirements Eng.., Lecture 13
Requirements Eng., Lecture 13

9. J. Nawrocki, Requirements Eng.., Lecture 13
Jerzy Nawrocki
Selected risk factors
General
Corporate politics (at client side)
Crowded office conditions (< 9 m2)
Excessive paperwork (> 50 docs, > 6 pages/FP)
Friction with client or senior management
Lack of specialisation
Low productivity (?)
Low quality ( -> Poor QA)
Low user satisfaction
Malpractice (Management)
J. Nawrocki, Requirements Eng.., Lecture 13
Requirements Eng., Lecture 13

10. J. Nawrocki, Requirements Eng.., Lecture 13
Jerzy Nawrocki
Selected risk factors
Poor planning
Inaccurate sizing of software deliverables
Inadequate risk analysis
Inadequate tools and methods
Lack of reusable estimates
Lack of reusable project plans
Missed schedules (unrealistic schedules; schedules not updated after changes; inadequate planning methods; lack of historical data from past projects)
Partial life-cycle definitions
J. Nawrocki, Requirements Eng.., Lecture 13
Requirements Eng., Lecture 13

11. Poor configuration control
Jerzy Nawrocki
Selected risk factors
Poor configuration control
Inadequate configuration control
Schedules not updated after changes
J. Nawrocki, Requirements Eng.., Lecture 13
Requirements Eng., Lecture 13

12. Poor progress tracking
Jerzy Nawrocki
Selected risk factors
Poor progress tracking
Inadequate measurement
Inadequate tools and methods
J. Nawrocki, Requirements Eng.., Lecture 13
Requirements Eng., Lecture 13

13. Poor quality assurance
Jerzy Nawrocki
Selected risk factors
Poor quality assurance
Inadequate software policies and standards
Inadequate tools and methods (QA)
Lack of reusable test plans and test cases
J. Nawrocki, Requirements Eng.., Lecture 13
Requirements Eng., Lecture 13

14. J. Nawrocki, Requirements Eng.., Lecture 13
Jerzy Nawrocki
Selected risk factors
Poor requirements
Creeping requirements
Lack of reusable requirements
J. Nawrocki, Requirements Eng.., Lecture 13
Requirements Eng., Lecture 13

15. J. Nawrocki, Requirements Eng.., Lecture 13
Jerzy Nawrocki
Selected risk factors
Poor development
Inadequate tools and methods (Soft.Eng., Tech. Documentation)
Lack of reusable components (architecture, code, design, doc, human interfaces)
Malpractice (technical staff)
J. Nawrocki, Requirements Eng.., Lecture 13
Requirements Eng., Lecture 13

16. J. Nawrocki, Requirements Eng.., Lecture 13
Jerzy Nawrocki
Selected risk factors
SDS specific risks
A team member stops his studies
A team member passes his exams in April
A team member is late is project tasks (e.g. he is ill)
Customer representative is not available
The tools are not available or not working
There is a computer/disk crash
Team members are not satisfied (e.g. The work is boring)
The acceptance criteria are not clear
J. Nawrocki, Requirements Eng.., Lecture 13
Requirements Eng., Lecture 13

17. J. Nawrocki, Requirements Eng.., Lecture 13
Jerzy Nawrocki
Risk Management
mse\sds\Templat\Risk0.html
J. Nawrocki, Requirements Eng.., Lecture 13
Requirements Eng., Lecture 13

18. J. Nawrocki, Requirements Eng.., Lecture 13
Summary
Risk is described by three elements:
name,
probability,
impact.
Selected risk factors (SDS specific risk factors)
At last!
J. Nawrocki, Requirements Eng.., Lecture 13

19. J. Nawrocki, Requirements Eng.., Lecture 13
Jerzy Nawrocki
Further readings
[Jon] Capers Jones, Assessment and control of software risks, Prentice Hall, Englewood Cliffs, NJ, 1994.
[Pres] Roger Pressman, Software Engineering. A Practitioner’s Approach, McGraw Hill, 1997. 
J. Nawrocki, Requirements Eng.., Lecture 13
Requirements Eng., Lecture 13

20. J. Nawrocki, Requirements Eng.., Lecture 13
Jerzy Nawrocki
Homework
Find more SDS specific risk factors
J. Nawrocki, Requirements Eng.., Lecture 13
Requirements Eng., Lecture 13

21. J. Nawrocki, Requirements Eng.., Lecture 13
Quality assessment
1. What is your general impression? (1 - 6)
2. Was it too slow or too fast?
3. What important did you learn during the lecture?
4. What to improve and how?
J. Nawrocki, Requirements Eng.., Lecture 13