CSC302H1 Lecture Notes - Lecture 7: Vital Signs
Document Summary
Risk = the possibility of suffering loss: risk itself is not bad essential to progress, challenge: manage the amount of risk. Risk exposure= p e p probability of risk occurring. Units can be in dollars, hours, etc. Shows the reduction of re per dollar spent on cost of (r ebefore r eafter) Measure risk exposure using standard cost & probability measures. Top software engineering risks: personnel shortfalls. Prevention: use top talent, team building, more training: unrealistic schedules/budgets. Prevention: use multisource estimation, designing to cost, requirements scrubbing. Prevention: better requirements analysis: developing the wrong software functions, developing the wrong user interface, gold plating. Prevention: requirements scrubbing, cost benefit analysis: continuing stream of requirements changes. Prevention: high change threshold, information hiding, incremental development: shortfalls in externally furnished components. Prevention: early benchmarking, inspections, compatibility analysis: shortfalls in externally performed tasks. Prevention: pre-award audits, competitive designs: real-time performance shortfalls. Prevention: target analysis, simulations, benchmarks: straining computer science capabilities.
