Software Development is a Risky Business - PowerPoint PPT Presentation

1 / 20
About This Presentation
Title:

Software Development is a Risky Business

Description:

Are the needs of the customer really understood? ... grossly expensive. Acceptable region. Negligible Risk. ALARP. Region. Risk Reduction ... – PowerPoint PPT presentation

Number of Views:41
Avg rating:3.0/5.0
Slides: 21
Provided by: helenek8
Category:

less

Transcript and Presenter's Notes

Title: Software Development is a Risky Business


1
Software Development is a Risky Business!
  • Whenever a computer program is to be built, there
    are areas of uncertainty..

2
Software is a Risky Business!
  • Why Uncertainty?

3
Why Uncertainty?
  • Are the needs of the customer really understood?
  • Can the functions that must be implemented be
    accomplished before the project deadline?
  • Will there be difficult, hidden technical
    problems?
  • Will the changes that invariably occur cause the
    schedule to slip badly?

4
What is risk?
  • Risk recognized the reality of change.
  • Risk concerns future happenings.

5
  • Risks are the consequences
  • of
  • Inadequate Information!

6
Risk analysis
  • - risk identification
  • - risk assessment
  • - risk management

7
Risk identification --
  • Identify ALL the risks that are OBVIOUS to both
    managers and practitioners.

8
Categories of risk
  • Technical risk
  • Business risk
  • Product risk
  • Project risk

9
Categories of risk Technical risk
10
Categories of risk Business risk
11
Categories of risk
  • Product risk
  • Project risk

12
What is the BEST way to deal with Risk?
13
What is the BEST way to deal with Risk?
  • Expect the unexpected, it invariably occurs!

14
Risk Assessment
  • Rate each risk in two ways
  • 1) What is the likelihood that the risk is real?
  • 2) What is the consequence of the problem if the
    risk does occur?

15
Risk Reduction ALARP?
  • ALARP As Low As Reasonably Practical
  • Once potential hazards and their causes have been
    identified, the system specification should be
    formalized in such a way that these hazards are
    unlikely to result in an accident!

16
Risk Reduction
Unacceptable region Risk cannot be
tolerated Risk tolerated only if risk
reduction is impractical or grossly
expensive. Acceptable region
ALARP Region
Negligible Risk
17
Risk Reduction
  • 1) Hazard avoidance
  • 2) Hazard Probability Reduction
  • 3) Accident Prevention

18
Risk Reduction Hazard avoidance
  • Design system so that hazards CANNOT arise.

19
Risk Reduction Hazard Probability Reduction
  • Design system so that the likelihood of hazard
    occurring is reduced.
  • Design system so that risk cannot occur as the
    result of any single action or error.

20
Risk Reduction Accident Prevention
  • Design system so that risks can be detected and
    recognized.
  • Design an accident monitoring system.
Write a Comment
User Comments (0)
About PowerShow.com