Requirements 1 Software Requirements Analysis and Specification.
07 requirements analysis - Department of Computer …Requirements analysis is about identifying this...
7
lecture 7: requirements analysis csc302h winter 2014 recap from last 4me • managing risk in the context of so7ware projects: assessment + control • risk exposure: – RE = probability × consequences (loss) • risk reducHon leverage: – RRL = (RE before – RE a7er ) ÷ cost of miHgaHng acHon – for ROI calculaHons and comparison • risk assessment – quanHtaHve (if you can) – qualitaHve (risk exposure matrix) recap from last 4me (2) • discussed some of the most common so7ware engineering risks & countermeasures • case studies (& lessons) – failed mars missions – theracP25 (from risks digest forum) – annoying oil tank with a phone! • don’t have iv&v report to the development manager (conflict of interest, that’s what the “i” is for) • principles of risk management
Transcript of 07 requirements analysis - Department of Computer …Requirements analysis is about identifying this...
lecture'7:'requirements'analysis'
!csc302h!
winter!2014!
recap'from'last'4me''
• managing!risk!in!the!context!of!so7ware!projects:!assessment!+!control!
• risk!exposure:!– RE!=!probability!×!consequences!(loss)!
• risk!reducHon!leverage:!– RRL!=!(REbefore!–!REa7er)!÷!cost!of!miHgaHng!acHon!– for!ROI!calculaHons!and!comparison!
• risk!assessment!– quanHtaHve!(if!you!can)!– qualitaHve!(risk!exposure!matrix)!
recap'from'last'4me'(2)'
• discussed!some!of!the!most!common!so7ware!engineering!risks!&!countermeasures!
• case!studies!(&!lessons)!– failed!mars!missions!– theracP25!(from!risks!digest!forum)!– annoying!oil!tank!with!a!phone!!
• don’t!have!iv&v!report!to!the!development!manager!(conflict!of!interest,!that’s!what!the!“i”!is!for)!
• principles!of!risk!management!
next%week:%%from%requirements%to%design%
