Legacy Issue Number: 16289
Source: MITRE ( Samuel Redwine)
SACM standard must accommodate assurance cases under development as this is expected to be a common usage transferring assurance cases among their developers or maintainers. This includes those incomplete.
In addition to incompleteness, decisions may yet to be concerning option options including the type of certain relations e.g. does an inference relation challenge or not. As the relative distinctions are not always known, particularly early in assurance cases construction, which currently abstract classes should be concrete classes should be reviewed and changed as required to accommodate this.
Recording explicit options yet to be decided among (and optionally their effects) could be useful (and also relevant to patterns).
More elements similar in name to the UnknownSubject might be included if required to meet this need.
Reported: ARM 1.0b1 — Fri, 27 May 2011 04:00 GMT
Disposition: Deferred — SACM 1.1
Deferred as still valid for SACM
The validity of this issue is still recognized. Providing full support for the issue as described requires support for exchanging assurance case patterns / templates. It has not been possible to implement this support in the current revision.
Updated: Tue, 21 Apr 2015 01:16 GMT
SACM11 — Assurance Cases under development or Incomplete
- Key: SACM11-4
- OMG Task Force: SACM 1.1 RTF