Apr 21.risk - Risk and Risk Management Risk Risk? What is...

Info iconThis preview shows pages 1–8. Sign up to view the full content.

View Full Document Right Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: Risk and Risk Management Risk Risk? What is risk? How likely? How painful? Risk Management Identify what is the source of the risk Quantify what is the scope of the likely impact Mitigate what can be done to minimize The Top Ten Software Risk Items Risk Item Risk Management Techniques 1. Personnel Shortfalls Staffing with top talent; key personnel agreements; incentives; team-building; training; tailoring process to skill mix; peer reviews 2. Unrealistic schedules and budgets Business case analysis; design to cost; incremental development; software reuse; requirements descoping; adding more budget and schedule 4. Requirements mismatch; gold plating Stakeholder win-win negotiation; business case analysis; mission analysis; ops-concept formulation; user surveys; prototyping; early users manual; design/develop to cost 5. User interface mismatch Prototyping; scenarios; user characterization (functionality, style, workload) 3. COTS; external components Qualification testing; benchmarking; prototyping; reference checking; compatibility analysis; vendor analysis; evolution support analysis Courtesy of the USC Center for Software Engineering The Top Ten Software Risk Items (cont.) 6. Architecture, performance, quality Architecture tradeoff analysis and review boards; simulation; benchmarking; modeling; prototyping; instrumentation; tuning 7. Requirements changes High change threshold; information hiding; incremental development (defer changes to later increments) 8. Legacy software Design recovery; phaseout options analysis; wrappers/mediators; restructuring 9. Externally-performed tasks Reference checking; pre-award audits; award-fee contracts; competitive design or prototyping; team-building 10. Straining Computer Science capabilities Technical analysis; cost-benefit analysis; prototyping; reference checking Courtesy of the USC Center for Software Engineering Software Risk at your level now Anything, any attribute, that is not considered when a piece of software is initially designed is not likely to be present when that software finished. Adding things to software that is already written requires effort far beyond what it would have taken to put it in in the first place. Adding things to software already written often breaks fundamental assumptions made when the software was first written causing formerly good code to break in strange and mysterious ways. More on Software Risk Design Risk: I dont know how to make it do that. I dont know if this method will solve the problem Platform Risk: How many I/Os does the handy board have? Floats vs. integer math RAM footprint The ilities list (a partial list) What should be done to minimize risk? Focus on: Visibility Testability Survivability Adaptability Work Top-down and Bottom-up Design top-down To make sure that nothing in the big picture gets left out (all those -ilities)...
View Full Document

This note was uploaded on 04/30/2008 for the course EE 361 taught by Professor Conry during the Spring '08 term at Clarkson University .

Page1 / 27

Apr 21.risk - Risk and Risk Management Risk Risk? What is...

This preview shows document pages 1 - 8. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online