Definition:
Concept Number: *412
English Master: Impacted-By
Synonyms, Variations & Acronyms: none
Detailing
none
Illustrations
Illustration: none
Type
[Impacted-By *412]: Parameter [Relationship].
Examples
A:
Danger List [A]:
Impacted-By: {Help Desk Capacity, User Motivation, User Training, Bug Frequency}.
Notes
Notes:
1. The purpose of “Impacted-By” is to help in Risk identification and analysis. We are trying to explicitly identify and Document factors, which we believe influence the results. This will hopefully Result in specific Action or design to keep those Impacts from threatening our planned results.
2. The more general purpose of Impacted-By, and many other Planguage relationship mechanisms, is to build a “web of connections” between specifications (that is, between System components). This web of connections serves many purposes. Risk management was mentioned above. Other uses are configuration management, System familiarization, Quality-Control, estimation, contracting, prioritization, and reviewing.
3. “Impacted-By” is differs from considerations of Risk/Threat in that both good and bad Impacts are considered. With Risk/Threat, we are primarily concerned with the potential for negative Impacts.
4. For strong primary intended Impacts, the “Supports” icon can be used, A ->> B. meaning A is primarily the way we intend to achieve the Requirement/value B.
Keyed-Icons
Keyed-Icon [Impacted-By *412]: ->
Note: Used in the same way as for Impacts *334. B is Impacted-By A is written A -> B.
Example:
A -> B “B is Impacted-By A = A Impacts B.”
Drawn-Icons
none
Related-Concepts
Risk *309
Threat *309
Dependency *189
Impacts *334
Supports *415
History-of-Concept
none
This Concept entered by Kay Dudman