What is it about?
This paper describes how materialization of risks that may affect fulfillment of a requirement may propagate to other requirements within a given level of abstraction due to requirement connectivity.
Featured Image
Why is it important?
Most research on requirements connectivity address dependencies (traceability) across the various levels of abstraction, given a system decomposition. In this paper though, the emphasis is placed on connectivity of requirements within a given level of abstraction. This is important because an effect on a given requirement may endanger the fulfillment of other requirements within a given set of requirements.
Perspectives
A key aspect of this paper is the treatment of requirements within a given set, i.e. within a given level of abstraction and allocated to a given component, instead of looking at cross-effects across various levels of abstraction (product tree, architecture decomposition, etc.). The paper shows how risks that materialize and endanger the fulfillment of one requirement can actually propagate within a given set of requirements endangering the fulfillment of other requirements too.
Dr Alejandro Salado
Virginia Polytechnic Institute and State University
Read the Original
This page is a summary of: 11.4.2 Assessing the Impacts of Uncertainty Propagation to System Requirements by Evaluating Requirement Connectivity, INCOSE International Symposium, June 2013, Wiley,
DOI: 10.1002/j.2334-5837.2013.tb03045.x.
You can read the full text:
Resources
Contributors
The following have contributed to this page
