Decision is an issue, which is also an aim, i.e. endeavors, such as issues, and other aims such as other decisions may be aligned to it.

Decision chaining can be done via alignment or via requires dependency. Alignment indicates that the “premise” decision affects the aligned decision, but the aligned decision can be in effect if the premise decision is not in effect. Requirement dependency indicates that the requiring decision can be in effect only when the required decision is in effect.

Decisions can have effective dates and can be superceded by other decisions.

This class does not specify the decision making process. Future releases or extensions may provide decision subclasses which support different decision analysis methodologies, e.g. Multiple-criteria decision analysis methodologies such as Analytic Hierarchy Process or Weighted Sum Model.

Supertypes

Referrers

  • Decision

Date when decision stops being in effect if it was in effect before. If not set, the decision is effective indefinitely if it is in a done status.

Type EDate
Cardinality 0..1
Changeable true
Derived false

Date when this decision goes into effect once it is available (done). If not set, decision goes into effect once it is in a done status.

Type EDate
Cardinality 0..1
Changeable true
Derived false

Documentation of what has been decided (decision process outcome).

Type EString
Cardinality 0..1
Changeable true
Derived false

Decisions which (will) supercede this decision when (if ever) they are effective.

Type Decision
Cardinality 0..*
Changeable false
Derived true
Opposite supercedes

Decisions which this decision supercedes once (if ever) it goes into effect.

Type Decision
Cardinality 0..*
Changeable true
Derived false
Opposite supercededBy