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.

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.

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.

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.