Dfp5043 Chapter 3 A
Dfp5043 Chapter 3 A
Dfp5043 Chapter 3 A
DFP5043
Software Requirement & Design
3.1
Software Management Process
b) Risk analysis
You have to consider each identified risk and
make a judgment about the probability and
seriousness of that risk. For example:
• The probability of the risk might be assessed as
very low ( 10%), low (10–25%), moderate (25–
50%), high (50–75%), or very high ( 75%).
• The effects of the risk might be assessed as
catastrophic (threaten the survival of the
project), serious (would cause major delays),
tolerable (delays are within allowed
contingency), or insignificant.
3.1
Software Management Process
c) Risk planning
You have to think of actions that you might
take to minimize the disruption to the project
if the problem identified in the risk occurs. For
example:
• Avoidance strategies
Following these strategies means that the
probability that the risk will arise will be
reduced. An example of a risk avoidance
strategy is the strategy for dealing with
defective components shown in Figure 22.5.
3.1
Software Management Process
• Minimization strategies
Following these strategies means that the
impact of the risk will be reduced. An example
of a risk minimization strategy is the strategy
for staff illness shown in Figure 22.5.
• Contingency plans
Following these strategies means that you are
prepared for the worst and have a strategy in
place to deal with it. An example of a
contingency strategy is the strategy for
organizational financial problems that I have
shown in Figure 22.5.
3.1
Software Management Process
Figure 22.5
3.1
Software Management Process
d) Risk monitoring
Risk monitoring is the process of checking that
your assumptions about the product, process,
and business risks have not changed. You should
regularly assess each of the identified risks to
decide whether or not that risk is becoming
more or less probable. You should also think
about whether or not the effects of the risk
have changed. To do this, you have to look at
other factors, such as the number of
requirements change requests, which give you
clues about the risk probability and its effects.
3.1
Software Management Process