DOC PREVIEW
WVU CS 430 - Software Risk Analysis and Management

This preview shows page 1-2-3-4 out of 11 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 11 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 11 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 11 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 11 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 11 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

3/18/20111Software Risk Analysis andSoftware Risk Analysis and ManagementBojan CukicBojan [email protected] Is Risk Analysis?•Steps that help manage uncertainty•Steps that help manage uncertainty.•A risk is a potential problem.–It might happen.• Identify it.• Assess its occurrence probability.• Estimate its impact.• Establish contingency plans, should it occur.3/18/20112Why Is It Important?•Be prepared!•Be prepared!• Because, if things can go wrong, they will.– Simplified: Things will go wrong.• Understanding risks and taking proactive measures to avoid and manage them is themeasures to avoid and manage them is the KEY element of good software engineering.Steps?•Risk identification•Risk identification.• Analyze occurrence likelihood and impact/damage.• Rank risks by probability and/or impact.• Develop a plan to manage high probability/impact risks.• Product?– Risk mitigation, monitoring and management plan (RMMM).3/18/20113Fundamentals•Can we by changing our actions today•Can we, by changing our actions today, create an opportunity for a better situation tomorrow?• Risk mitigation always involves a change.• Risk involves a choice, which brings tituncertainty– But the risk itself is very certain!• On a software project, choose the “right risks” to tackle. Strategies•Reactive•Reactive.– Indiana Jones:”Don’t worry, I’ll think of something.”– Not every software engineer is Indiana Jones. – If reactive, set resources aside for firefighters.• Proactive strategies based on risk identification, ranking and contingency planning.3/18/20114Software Risks•Involve uncertainty and loss•Involve uncertainty and loss.• Project risks: threaten project plans. – Schedule, cost, personnel, resource, customer, requirements, complexity, size, structural uncertainty. • Technical risks: quality and timeliness.–Design implementation interface verification–Design, implementation, interface, verification, maintenance problems.– (B)leading edge technologies. Software Risks (2)•Business risks•Business risks.– Does anyone want the product?– Does the product fit business strategy?– Do salespeople understand the product?– Loosing support of senior management.– Loosing budgetary of personnel commitment.3/18/20115Risk Management ParadigmcontrolcontrolRISKidentifyidentifylltracktrackanalyzeanalyzeplanplanRisk Identification•Generic vs product specific risks•Generic vs. product specific risks.• Risk checklists.– Product size, business impact, customer characteristics, process definition, development environment, technology to be built, staff size diand experience.3/18/20116Assessing Overall Software Risk•Questions ordered by relative importance•Questions ordered by relative importance.– Have top software and customer managers formally committed to support the project?– Are end-users enthusiastic?– Are requirements fully understood?– Have customers participated in requirements definition?– Do end-users have realistic expectations?– Does SE team have the right mix of skills?Risk Components and Drivers•Components•Components.– Performance risks, meeting requirements and fitting intended use.–Cost risks– Support risk.– Schedule risk.3/18/20117Risk Projection•The same as risk estimation•The same as risk estimation.• Rates each risk in two ways:– Likelihood (probability) that the risk is real.– Consequences of the problem, should it occur.• Procedure.–Establish the scale for likelihood, delineate consequences, estimate the impact, note the overall accuracy of estimation.3/18/20118Risk Impact•Consequences determined by the nature the•Consequences determined by the nature, the scope and the timing of the risk occurrence. • Nature: the problems likely to occur.• Scope: severity and the overall distribution of the effect.• Timing: how long will the impact be felt.3/18/20119Risk assessment•Define risk reference level•Define risk reference level.– Performance, cost, support, schedule.– Some degradation is acceptable, but how much?– Define the referent point, or the break point.3/18/201110Risk Mitigation•Avoidance monitoring management and•Avoidance, monitoring, management and contingency planning.– Meet with current staff.– Mitigate causes for the problem (personnel turnover, for example).–Disperse information about developmentDisperse information about development activities.– Conduct peer reviews. – Assign a back-up staff member(s)3/18/201111Assess Performance RisksIdentify critical use casesSelect key performance scenariossce a osEstablish performance objectivesConstruct performance modelsAdd software resource requirementsAdd computer resource Modify/create scenariosrequirementsEvaluate performance model(s)Modify product conceptRevise performanceobjectivesV&V of performance


View Full Document

WVU CS 430 - Software Risk Analysis and Management

Documents in this Course
Lecture

Lecture

28 pages

Design

Design

27 pages

Load more
Download Software Risk Analysis and Management
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view Software Risk Analysis and Management and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view Software Risk Analysis and Management 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?