Risk Analysis, Assessment, and Prioritization looks at how you can manage conflicts at system levels, but it can also be applied to lower level assessments. How do you manage and document conflict, along with alternatives? In analyzing alternatives, you must consider risks. In this course, we'll look into how to analyze risk, evaluate risk, document risks, and use this information for prioritization of requirements. Qualitative and Quantitative approaches will be covered.
Class Deals by MOOC List - Click here and see Coursera's Active Discounts, Deals, and Promo Codes.
Course 4 of 5 in the Requirements Engineering: Secure Software Specifications Specialization.
Syllabus
WEEK 1
Risk Analysis, Assessment and Prioritization
Once requirements have been somewhat/mostly determined, we next need to go carefully through our work. This involves analyzing risk, assessing alternative plans, and prioritizing. In this module, we examine how to begin documenting conflicts and generating conflict resolution.
WEEK 2
Dealing with Risk
Risk goes far beyond security. Most non-functional requirements are part of risk analysis. In this lesson, we discuss different types of risks, how they can be identified, and how to visualize a causal linking of failures, causes, and consequences using risk trees and cut-set trees.
WEEK 3
Controlling Risk
In writing use cases and scenarios, we'll discover risk in the interactions. Interactions may happen out of order, to quickly or slowly, or not occur at all. In risk assessment, we assess the likelihood of risks and their severity, the likelihood of consequences, and thus, attempt to control high-priority risks.
WEEK 4
Incorporating Risk Management into Your Process
Many approaches can be used to incorporate risk management into your software requirements engineering process. One is Defect Detection Prevention (DDP). We can also analyze alternatives qualitatively and quantitatively. We discuss Defect Detection Prevention, Value Cost Prioritization, and the Analytic Hierarchal Process in this module and how these techniques can be scaled for every day use.
