1. Risk Management Managing the Software Process - Risk Management Advanced Software Engineering COM360 University of Sunderland © 1998

2. Risk Management What is Risk? A risk is a possible occurrence - comprising: –The probability that it will occur. –Size of loss resulting from occurrence

3. Risk Management The SEI Risk Management Paradigm ControlIdentify Analyze Plan Track Communicate

4. Risk Management step 1 - Identify Locate risks before they become problems and adversely affect the project. “It’s harder to ignore if it’s written down”

5. Risk Management step 2 - Analyze Turn the raw risk data into decision making information –i.e. understanding the risk Allows managers to work on the right risks

6. Risk Management step 3 - Plan Turn risk information into decisions and actions (both present and future) to : –develop a contingency plan –avoid risk by changing design –accept risk and take consequences –study risk further

7. Risk Management step 4 - Track Monitor the status of risks and action taken against risks Develop risk metrics and triggering events

8. Risk Management step 5 - Control Correct for deviations from the planned risk actions

9. Risk Management Communication Provide feedback on the active risk activities among the paradigm elements and within the project i.e. TELL both developers and customers about the risks yiu’ve found and what your doing to manage them.

10. Risk Management Risk Identification Three major classes of risk: –Product Engineering Technical aspects of the work to be accomplished –Development Environment Methods, procedures & tools used –Program Constraints Contractual, organisational and operational factors

11. Risk Management Software Development Risk Development EnvironmentProgram ConstraintsProduct Engineering Requirements…. …… Development Process..Resources... Schedule….Facilities...

12. Risk Management Product Engineering Class Requirements Design Code and Unit Test Integaration and Test Engineering Specialities (e.g. Safety)

13. Risk Management Development Environment Class Development Process –e.g. Planning the product development Development System –e.g. CASE tools Management Process –e.g. Budgets & Schedules Management Methods –e.g. Personnel Management Work Environment –e.g. Morale!

14. Risk Management Program Constraint Class Resources –e.g. staff, budget etc. Contract –terms and conditions Program Interfaces –customers, contractors, etc.

15. Risk Management Taxonomy of Software Development Risks A. Product Engineering –1. Requirements a. Stability b. Completeness c. Clarity d. Validity e. Feasibility f. Precedent g. Scale