1. OMG Mailing List
  2. SACM 2.0 Finalization Task Force

All Issues

  • All Issues
  • Name: sacm2-ftf
  • Issues Count: 20

Issues Summary

Key Issue Reported Fixed Disposition Status
SACM2_-26 Address missing elements of first 12 issues and address style consistency SACM 2.0b2 open
SACM2_-11 Need for the ability to group SACMElements SACM 2.0b2 open
SACM2_-24 Need more consistency in packages, interfaces and binding SACM 2.0b2 open
SACM2_-1 Need to simplify the citation classes of SACM SACM 2.0b2 open
SACM2_-9 Elements in all parts of SACM need to be considered as artifacts and appropriate context and support relationships captured. SACM 2.0b2 open
SACM2_-10 Better support for patterns is needed SACM 2.0b2 open
SACM2_-6 Simplify ArtifactElement and its sub-types SACM 2.0b2 open
SACM2_-7 Simplification of ArtifactAssetRelationship SACM 2.0b2 open
SACM2_-5 Alow AssertedRelationship to express if it is a counter relationship SACM 2.0b2 open
SACM2_-3 Simplification of elements contained in packages SACM 2.0b2 open
SACM2_-4 Need to simplify internationalization support in Expressions. SACM 2.0b2 open
SACM2_-2 SACM needs support for Internationalization SACM 2.0b2 open
SACM2_-8 Align with American English to support use of SACM by The Open Group SACM 2.0b2 open
SACM2-68 The SACM 2.0 meta-model requires implementation of the Terminology Package in spite of the text of Chapter 2 on compliance points saying it is optional. SACM 2.0b1 open
SACM2-67 Inconsistent use of the word “Model” in describing the three compliance points SACM 2.0b1 open
SACM2-73 There is no compliance point for those that support/use the Terminology Package specified in SACM 2.0’s metamodel. SACM 2.0b1 open
SACM2-71 In the classes related to Citations, the terms Element and Asset are inconsistently used. SACM 2.0b1 open
SACM2-72 Model uses undefined ‘date’ type. SACM 2.0b1 open
SACM2-70 Section 2 doesn’t make it clear that AssuranceCase compliance point is mandatory. SACM 2.0b1 open
SACM2-69 Incorrect description of the Argumentation compliance point. SACM 2.0b1 open

Issues Descriptions

Address missing elements of first 12 issues and address style consistency

  • Key: SACM2_-26
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    There are several areas where the work packages for addressing issues 1, 2, 3, 5, 6, 7, 9, 11, or 12 missed changes, additions, and deletions to support internationalization and package simplification. Additionally, there are several style issues in the text that need to be made consistent.

  • Reported: SACM 2.0b2 — Fri, 25 Aug 2017 18:13 GMT
  • Updated: Mon, 28 Aug 2017 21:05 GMT
  • Attachments:

Need for the ability to group SACMElements

  • Key: SACM2_-11
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    To support multiple stakeholder views and purposes a mechanism for associating SACMElements is needed.

  • Reported: SACM 2.0b2 — Tue, 22 Aug 2017 15:44 GMT
  • Updated: Mon, 28 Aug 2017 20:26 GMT
  • Attachments:

Need more consistency in packages, interfaces and binding

  • Key: SACM2_-24
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    There are unnecessary differences between the Assurance Case, Terminology, Argument, and Artifact package definitions, interfaces, and bindings.

  • Reported: SACM 2.0b2 — Thu, 24 Aug 2017 20:03 GMT
  • Updated: Mon, 28 Aug 2017 20:26 GMT
  • Attachments:

Need to simplify the citation classes of SACM

  • Key: SACM2_-1
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    Citations can be simplified by removing them from Argumentataion, Artifact and Terminology classes and replacing them with +isCitation and +citedElement properties in SACMElement in the Base classes.

  • Reported: SACM 2.0b2 — Thu, 3 Aug 2017 19:13 GMT
  • Updated: Mon, 28 Aug 2017 20:26 GMT
  • Attachments:

Elements in all parts of SACM need to be considered as artifacts and appropriate context and support relationships captured.

  • Key: SACM2_-9
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    If all elements in Argumentation, Terminology, Artifact and AssuranceCase can be considered as artifacts the assertion that one or more artifact provide context for another artifact; and the assertion that one or more artifact support another artifact needs to be captured.

  • Reported: SACM 2.0b2 — Tue, 22 Aug 2017 15:41 GMT
  • Updated: Mon, 28 Aug 2017 20:26 GMT

Better support for patterns is needed

  • Key: SACM2_-10
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    The ability to create patterns (e.g. AssuranceCase patterns, ArgumentPackage patterns, etc) that contain only abstract SACMElements is needed and the patterns should be re-usable.

  • Reported: SACM 2.0b2 — Tue, 22 Aug 2017 15:42 GMT
  • Updated: Mon, 28 Aug 2017 20:26 GMT

Simplify ArtifactElement and its sub-types

  • Key: SACM2_-6
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    In SACM, all elements in the Argumentation package, Artifact package, Terminology package, and AssuranceCase package are considered to be Artifacts.

    Consequently ArtifactElement needs to be moved to the Base classes and be a direct sub-type of ModelElement. All elements in other packages then will sub-type ArtifactElement.

  • Reported: SACM 2.0b2 — Thu, 3 Aug 2017 19:19 GMT
  • Updated: Mon, 28 Aug 2017 20:26 GMT
  • Attachments:

Simplification of ArtifactAssetRelationship

  • Key: SACM2_-7
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    ArtifactAssetRelationship can be simplified by removing all its sub-classes. The purpose of an ArtifactAssetRelationship can then be recorded by the property +property:Property in the ArtifactAsset class.

  • Reported: SACM 2.0b2 — Thu, 3 Aug 2017 19:19 GMT
  • Updated: Mon, 28 Aug 2017 20:26 GMT
  • Attachments:

Alow AssertedRelationship to express if it is a counter relationship

  • Key: SACM2_-5
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    In Argumentation package, AssertedRelationship should directly express if it is a counter relationship.

  • Reported: SACM 2.0b2 — Thu, 3 Aug 2017 19:18 GMT
  • Updated: Mon, 28 Aug 2017 20:26 GMT
  • Attachments:

Simplification of elements contained in packages


Need to simplify internationalization support in Expressions.

  • Key: SACM2_-4
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    There is currently no direct mechanism to support internationalization in SACM content.

  • Reported: SACM 2.0b2 — Thu, 3 Aug 2017 19:16 GMT
  • Updated: Mon, 28 Aug 2017 20:26 GMT

SACM needs support for Internationalization


Align with American English to support use of SACM by The Open Group

  • Key: SACM2_-8
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    Use “artifact” instead of “artefact” is needed to make incorporation of SACM into The Open Group standards more practical.

  • Reported: SACM 2.0b2 — Thu, 3 Aug 2017 19:21 GMT
  • Updated: Mon, 28 Aug 2017 20:26 GMT
  • Attachments:

The SACM 2.0 meta-model requires implementation of the Terminology Package in spite of the text of Chapter 2 on compliance points saying it is optional.


Inconsistent use of the word “Model” in describing the three compliance points

  • Key: SACM2-67
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    Of the three compliance points, one is referred to with the word “Model” while the other two are not. All three should consistently use this word in describing the compliance points. Additionally, two times “model” is used instead of “Model”.

  • Reported: SACM 2.0b1 — Thu, 29 Dec 2016 19:00 GMT
  • Updated: Thu, 6 Apr 2017 13:57 GMT
  • Attachments:

There is no compliance point for those that support/use the Terminology Package specified in SACM 2.0’s metamodel.

  • Key: SACM2-73
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    In making support for the Terminology Package optional a compliance point for those that want to support the Terminology Package was mistakenly left out.

  • Reported: SACM 2.0b1 — Thu, 29 Dec 2016 19:04 GMT
  • Updated: Thu, 6 Apr 2017 13:57 GMT
  • Attachments:

In the classes related to Citations, the terms Element and Asset are inconsistently used.

  • Key: SACM2-71
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    The 31 uses of the class name “ArtefactElementCitation” and the 10 uses of the class name “ArgumentElementCitation” are inconsistent with the 20 uses of the class name “ArtefactAssetCitation” and 7 uses of the class name “ArgumentAssetCitation”.

  • Reported: SACM 2.0b1 — Thu, 29 Dec 2016 19:02 GMT
  • Updated: Thu, 6 Apr 2017 13:57 GMT

Model uses undefined ‘date’ type.

  • Key: SACM2-72
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    Currently, the Artefact, and Activity classes use the type ‘date’ for some of their attributes, and the ‘date’ attribute is missing from the model and diagrams for ActivityEvent, despite appearing in the text of the specification.

  • Reported: SACM 2.0b1 — Thu, 29 Dec 2016 19:03 GMT
  • Updated: Thu, 6 Apr 2017 13:57 GMT
  • Attachments:

Section 2 doesn’t make it clear that AssuranceCase compliance point is mandatory.

  • Key: SACM2-70
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    Section 2 doesn’t make it clear that AssuranceCase compliance point is mandatory. Also, some text in section 2.4 should be moved to precede all the compliance point descriptions.

  • Reported: SACM 2.0b1 — Thu, 29 Dec 2016 19:01 GMT
  • Updated: Thu, 6 Apr 2017 13:57 GMT
  • Attachments:

Incorrect description of the Argumentation compliance point.

  • Key: SACM2-69
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    In the second paragraph of Section 2.1 there is currently the text, “The ‘ArtefactElementCitation’ class shall not be used.” This is incorrect. The ArtefactElementCitation class is still necessary for the use of Argumentation compliance point.

  • Reported: SACM 2.0b1 — Thu, 29 Dec 2016 19:01 GMT
  • Updated: Thu, 6 Apr 2017 13:57 GMT