Concept Number: *189
English Master: Dependency
Synonyms, Variations & Acronyms: Depends-On
Rationale [Dependency *189]: To promote awareness of relationships, ensure more realistic Planning, and provide the ability to identify reliance, and therefore cope with any associated risks.
Z [T]: YY. “Only if T is true, does Z have a value of YY.”
A: Depends-On: B. “If B is not true then A is not true.”
Dependency: XX. “Tag A has a dependency on XX.”
Goal [Contract Beta]: 60%.
This Means that the Goal Level Requirement of “60%” is valid as a Goal, if and only if, “Contract Beta” is “in force”. The Goal has an implied dependency on the Qualifier, “Contract Beta”.
Dependency: The satellite must be operational for the phone to operate. <-Catherine.
Dependency XX: Design-Idea XX > Reliability [USA, If Patent PP].
This is a “weak” dependency statement because we have no specification of whether the dependency is trivial or critical in degree. A numeric Impact-Estimate could be used to give us that information, later, if we wanted it.
Tag: Refugee Transport.
Description: Moving refugees back to home villages.
Source: Charity Aid Manual [March, Last Year].
Depends-On: The mode of transport will be determined by safety and Cost factors.
“Or the equivalent:
Dependency: The mode of transport will be determined by safety and Cost factors.”
Contract Beta: Depends-On: Conglomerate Corp [Our Customer, USA].
This Means that if “Conglomerate Corp [Our Customer, USA]” is not true, then “Contract Beta===” is not “true”.
1. Any given Component can be part of numerous dependencies (either having one or more dependencies, and/or having one or more dependencies placed on it).
2. The reliance involved in a dependency can be of many kinds. For example, there can be dependency for operation, for success, or for failure avoidance.
3. Qualifiers specify implied dependencies.
4. The Parameter, “Dependency,” or its synonym, “Depends-On,” is used to explicitly specify a dependency.
This Concept entered by Diane O'Brien.