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.
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.
A risk taxonomy proposal for software maintenance2 時間
What is Risk? A taxonomy document1 時間
What is a Risk? |Cut-Set Trees - Slides30 分
2の練習問題
Module 2 Practice Quiz6 分
Dealing with Risk30 分
週
3
2時間で修了
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.
Software risk management: principles and practices1 時間
Risk Assessment | Risk Control and Countermeasures - Slides30 分
2の練習問題
Module 3 Practice Quiz6 分
Controlling Risk30 分
週
4
5時間で修了
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.
The University of Colorado is a recognized leader in higher education on the national and global stage. We collaborate to meet the diverse needs of our students and communities. We promote innovation, encourage discovery and support the extension of knowledge in ways unique to the state of Colorado and beyond....
This specialization is intended for software engineers, development and product managers, testers, QA analysts, product analysts, tech writers, and security engineers. Even if you have experience in the requirements realm, this course will expand your knowledge to include new viewpoints, development styles, techniques and tools.
For anyone seeking a graduate degree, certificate, or professional degree in computer science, these courses will additionally give you a broad understanding of how requirements engineering is performed and help you get a first foot forward into your upcoming careers.
The Software Requirements specialization focuses on traditional software requirements elicitation and writing techniques, while also looking at requirements from a security standpoint. In traditional methods, non-functional requirements, such as security, are often ignored overall. In this specialization, students will be introduced to ways of eliciting requirements from stakeholders, how to analyze these requirements, conduct risk mitigation and analysis, prioritize requirements, document, and bring security concerns into the software lifecycle early on....