${taskforce.name} Avatar
  1. OMG Task Force

SACM 2.1 RTF — All Issues

  • Key: SACM21
  • Issues Count: 54
Open Closed All
All Issues

Issues Summary

Key Issue Reported Fixed Disposition Status
SACM21-109 New notations for asserted context and asserted artifact context SACM 2.0 SACM 2.1 Resolved closed
SACM21-84 http -> https in MOF file SACM 2.0 SACM 2.1 Closed; No Change closed
SACM21-83 Why MOF 2.0 SACM 2.0 SACM 2.1 Closed; No Change closed
SACM21-82 PNG images SACM 2.0 SACM 2.1 Resolved closed
SACM21-81 !!.14 or 11.14 SACM 2.0 SACM 2.1 Closed; No Change closed
SACM21-80 SACM21-1 through 13 were unnecessary SACM 2.0 SACM 2.1 Closed; No Change closed
SACM21-79 Issue 55 material includes Issue 30 changes SACM 2.0 SACM 2.1 Resolved closed
SACM21-78 multiplicity change missing figures SACM 2.0 SACM 2.1 Resolved closed
SACM21-77 Missing Concrete Syntax in 11.10 SACM 2.0 SACM 2.1 Resolved closed
SACM21-76 Date or date in 12.11 SACM 2.0 SACM 2.1 Resolved closed
SACM21-72 newline SACM 2.0 SACM 2.1 Resolved closed
SACM21-71 multiplicity in figure and text do not match SACM 2.0 SACM 2.1 Resolved closed
SACM21-70 trailing bullet SACM 2.0 SACM 2.1 Resolved closed
SACM21-69 SPMS version SACM 2.0 SACM 2.1 Resolved closed
SACM21-68 Typo on pdf pg 10 SACM 2.0 SACM 2.1 Resolved closed
SACM21-67 http -> https SACM 2.0 SACM 2.1 Resolved closed
SACM21-65 SACM21-20 the changes are inconsistent with pdf SACM 2.0 SACM 2.1 Resolved closed
SACM21-64 SACM21-14 and SACM21-16 bad urls SACM 2.0 SACM 2.1 Closed; No Change closed
SACM21-13 Address missing elements of first 12 issues and address style consistency SACM 2.0b2 SACM 2.1 Closed; No Change closed
SACM21-12 Need for the ability to group SACMElements SACM 2.0b2 SACM 2.1 Closed; No Change closed
SACM21-11 Better support for patterns is needed SACM 2.0b2 SACM 2.1 Closed; No Change closed
SACM21-10 Simplification of ArtifactAssetRelationship SACM 2.0b2 SACM 2.1 Closed; No Change closed
SACM21-9 Need to simplify the citation classes of SACM SACM 2.0b2 SACM 2.1 Closed; No Change closed
SACM21-8 Elements in all parts of SACM need to be considered as artifacts and appropriate context and support relationships captured. SACM 2.0b2 SACM 2.1 Closed; No Change closed
SACM21-7 Need more consistency in packages, interfaces and binding SACM 2.0b2 SACM 2.1 Closed; No Change closed
SACM21-6 SACM needs support for Internationalization SACM 2.0b2 SACM 2.1 Closed; No Change closed
SACM21-5 Simplification of elements contained in packages SACM 2.0b2 SACM 2.1 Closed; No Change closed
SACM21-4 Need to simplify internationalization support in Expressions. SACM 2.0b2 SACM 2.1 Closed; No Change closed
SACM21-3 Alow AssertedRelationship to express if it is a counter relationship SACM 2.0b2 SACM 2.1 Closed; No Change closed
SACM21-2 Simplify ArtifactElement and its sub-types SACM 2.0b2 SACM 2.1 Closed; No Change closed
SACM21-1 Align with American English to support use of SACM by The Open Group SACM 2.0b2 SACM 2.1 Closed; No Change closed
SACM21-31 B and A or A and B SACM 2.0 SACM 2.1 Resolved closed
SACM21-30 Replace "that" with "whether"? SACM 2.0 SACM 2.1 Resolved closed
SACM21-25 Spelling mistake in 11.8 SACM 2.0 SACM 2.1 Closed; No Change closed
SACM21-22 Spelling mistake in 2.5 SACM 2.0 SACM 2.1 Closed; No Change closed
SACM21-21 Mistake in element name in 2.3 text SACM 2.0 SACM 2.1 Resolved closed
SACM21-20 Concepts in SACM 2 have no direct graphical notation SACM 2.0 SACM 2.1 Resolved closed
SACM21-19 Missing role discription for terminology model SACM 2.0 SACM 2.1 Resolved closed
SACM21-18 Misleading section title for 1.3 Artifact SACM 2.0 SACM 2.1 Closed; No Change closed
SACM21-62 Outdated constraints for class Claim SACM 2.0 SACM 2.1 Duplicate or Merged closed
SACM21-58 In 11.13 the +target should have multiplicity of 1 SACM 2.0 SACM 2.1 Resolved closed
SACM21-55 Unnecessary constraint statement in 11.11 SACM 2.0 SACM 2.1 Resolved closed
SACM21-107 Graphical notation for SACM Argumentation concepts SACM 2.0 SACM 2.1 Resolved closed
SACM21-75 Date or date in 12.9 SACM 2.0 SACM 2.1 Resolved closed
SACM21-74 Date or date in 12.7 SACM 2.0 SACM 2.1 Resolved closed
SACM21-73 text and figure mismatch ArgumentPackage<-->ArgumentPackageInterface SACM 2.0 SACM 2.1 Resolved closed
SACM21-66 Confirm URI on title page SACM 2.0 SACM 2.1 Resolved closed
SACM21-17 Incorrect description of package SACM 2.0 SACM 2.1 Resolved closed
SACM21-16 Invalid URL SACM 2.0 SACM 2.1 Closed; No Change closed
SACM21-15 Association is inconsistent with semantics SACM 2.0 SACM 2.1 Resolved closed
SACM21-14 Broken Link SACM 2.0 SACM 2.1 Closed; No Change closed
SACM21-29 Duplicative paragraphs? SACM 2.0 SACM 2.1 Resolved closed
SACM21-24 Punctuation and spacing errors SACM 2.0 SACM 2.1 Resolved closed
SACM21-23 Spelling mistake in 9.1 SACM 2.0 SACM 2.1 Closed; No Change closed

Issues Descriptions

New notations for asserted context and asserted artifact context

  • Key: SACM21-109
  • Status: closed  
  • Source: MITRE ( Mr. Robert Martin)
  • Summary:

    The notation previously selected for these concepts could cause confusion when viewed by those familiar with UML notations or when viewing UML notations in proximity to these SACM concepts.

  • Reported: SACM 2.0 — Wed, 20 Mar 2019 20:54 GMT
  • Disposition: Resolved — SACM 2.1
  • Disposition Summary:

    New notations for asserted context and asserted artifact context

    Replace diamond line heads with squares with small line at end to distinguish them from UML notations in the 19 figures that used diamond line heads.

  • Updated: Tue, 8 Oct 2019 17:58 GMT
  • Attachments:

http -> https in MOF file

  • Key: SACM21-84
  • Status: closed  
  • Source: MITRE ( Mr. Robert Martin)
  • Summary:

    JS18 - http -> https throughout for omg.org (all URIs)

  • Reported: SACM 2.0 — Mon, 18 Mar 2019 15:34 GMT
  • Disposition: Closed; No Change — SACM 2.1
  • Disposition Summary:

    http -> https in MOF file

    https is not supported in MOF 2.0 and we can not generate MOF 2.5.1 from the version of MagicDraw we have available.

  • Updated: Tue, 8 Oct 2019 17:58 GMT

Why MOF 2.0

  • Key: SACM21-83
  • Status: closed  
  • Source: MITRE ( Mr. Robert Martin)
  • Summary:

    JS19 - Why MOF 2.0, and not 2.5.1?  If no technical reason, update to 2.5.1.

  • Reported: SACM 2.0 — Mon, 18 Mar 2019 15:33 GMT
  • Disposition: Closed; No Change — SACM 2.1
  • Disposition Summary:

    Why MOF 2.0

    The MagicDraw version University of York has does not support exporting to MOF any more. We are trying to find any alternatives, but in the meantime we are stuck to this version.

  • Updated: Tue, 8 Oct 2019 17:58 GMT

PNG images

  • Key: SACM21-82
  • Status: closed  
  • Source: MITRE ( Mr. Robert Martin)
  • Summary:

    JS17 - The PNG images are less than optimal, and fuzzy throughout Section 11 and Annex C in both clean and changebar docs.  SVG preferred in general.  Can these be regenerated appropriately?

  • Reported: SACM 2.0 — Mon, 18 Mar 2019 15:33 GMT
  • Disposition: Resolved — SACM 2.1
  • Disposition Summary:

    PNG images

    new figures were generated for previous png figures - will be attached to the new report and used in the updated specification.

  • Updated: Tue, 8 Oct 2019 17:58 GMT
  • Attachments:

!!.14 or 11.14

  • Key: SACM21-81
  • Status: closed  
  • Source: MITRE ( Mr. Robert Martin)
  • Summary:

    JS16 - Filename for SACM21-31/!!.14 - A2B.pdf  - I assume this should be 11.14… that’s going to wreak havoc with some filesystems.

  • Reported: SACM 2.0 — Mon, 18 Mar 2019 15:32 GMT
  • Disposition: Closed; No Change — SACM 2.1
  • Disposition Summary:

    JIRA file names for files included in Report

    Passed on to Mariano for resolution - no change in specification or issue resolution materials.

  • Updated: Tue, 8 Oct 2019 17:58 GMT

SACM21-1 through 13 were unnecessary

  • Key: SACM21-80
  • Status: closed  
  • Source: MITRE ( Mr. Robert Martin)
  • Summary:

    JS15 - SACM21-1 through 13 were unnecessary to add to archive and muddied the waters.  One for Mariano?

  • Reported: SACM 2.0 — Mon, 18 Mar 2019 15:31 GMT
  • Disposition: Closed; No Change — SACM 2.1
  • Disposition Summary:

    SACM21-1 through 13 were unnecessary

    When finishing the previous Report - 14 issues that were resolved in that Report were incorrectly passed to this RTF. Referred to Mariano to resolve.

  • Updated: Tue, 8 Oct 2019 17:58 GMT

Issue 55 material includes Issue 30 changes

  • Key: SACM21-79
  • Status: closed  
  • Source: MITRE ( Mr. Robert Martin)
  • Summary:

    JS14 - Issue 55 (ptc-19-02-33/SACM21-55/11.11-deletion.pdf) includes editorial ‘that’ to ‘whether’ that is listed in changebar as Issue 30.

  • Reported: SACM 2.0 — Mon, 18 Mar 2019 15:31 GMT
  • Disposition: Resolved — SACM 2.1
  • Disposition Summary:

    showing changes from different issue

    removed edit notations from a different issue from 11.11-deletion pdf

  • Updated: Tue, 8 Oct 2019 17:58 GMT
  • Attachments:

multiplicity change missing figures

  • Key: SACM21-78
  • Status: closed  
  • Source: MITRE ( Mr. Robert Martin)
  • Summary:

    JS13 - Issue 58 (ptc-19-02-33/SACM21-58/11.13 multiplicity.pdf) does not include the graphic for Figure 7.2 on pg 12 and changes on pg 37 11.14 marked as Issue 31, 20 - should not have been in this file.

  • Reported: SACM 2.0 — Mon, 18 Mar 2019 15:30 GMT
  • Disposition: Resolved — SACM 2.1
  • Disposition Summary:

    multiplicity change missing figures

    included figures in pdf of changes

  • Updated: Tue, 8 Oct 2019 17:58 GMT
  • Attachments:

Missing Concrete Syntax in 11.10

  • Key: SACM21-77
  • Status: closed  
  • Source: MITRE ( Mr. Robert Martin)
  • Summary:

    JS12 - Issue 20 (ptc-19-02-33/SACM21-20/Concrete Syntax.pdf) does not include the Concrete Syntax added to Section 11.10 Assertion (abstract) and includes an editorial change (‘that’ to ‘whether’) on page 38 Sec 11.13 under Attributes that is not in the changebar or clean documents for issue 20. 

  • Reported: SACM 2.0 — Mon, 18 Mar 2019 15:29 GMT
  • Disposition: Resolved — SACM 2.1
  • Disposition Summary:

    Missing Concrete Syntax in 11.10

    Added note of insertion in early pages of Concrete Syntax pdf for missing Concrete Syntax in 11.10. Change in word ”that” to “whether” is correctly marked as Issue 30 (not 20) in the clean and changebar pdfs. Removed from Issue 20’s Concrete Syntax pdf.

  • Updated: Tue, 8 Oct 2019 17:58 GMT
  • Attachments:

Date or date in 12.11

  • Key: SACM21-76
  • Status: closed  
  • Source: MITRE ( Mr. Robert Martin)
  • Summary:

    JS11 – In 12.11 Activity, under Attributes, startDate:Date[0..1] does not match naming of type in Figure 12.1, which is startDate:date[0..1] and under Attributes, endDate:Date[0..1] does not match naming of type in Figure 12.1, which is endDate:date[0..1]

  • Reported: SACM 2.0 — Mon, 18 Mar 2019 15:28 GMT
  • Disposition: Resolved — SACM 2.1
  • Disposition Summary:

    Date or date in 12.11

    resolve difference

  • Updated: Tue, 8 Oct 2019 17:58 GMT
  • Attachments:

newline

  • Key: SACM21-72
  • Status: closed  
  • Source: MITRE ( Mr. Robert Martin)
  • Summary:

    JS7 – In 8.6 ModelElement (abstract), under Associations, need a newline between implementationConstraint and description.

  • Reported: SACM 2.0 — Mon, 18 Mar 2019 15:24 GMT
  • Disposition: Resolved — SACM 2.1
  • Disposition Summary:

    missing newline

    added newline to address comment

  • Updated: Tue, 8 Oct 2019 17:58 GMT
  • Attachments:

multiplicity in figure and text do not match

  • Key: SACM21-71
  • Status: closed  
  • Source: MITRE ( Mr. Robert Martin)
  • Summary:

    JS6 – In 8.2 SACMElement (abstract), under Attributes, isCitation and isAbstract do not match multiplicity in Figure 8.1

  • Reported: SACM 2.0 — Mon, 18 Mar 2019 15:24 GMT
  • Disposition: Resolved — SACM 2.1
  • Disposition Summary:

    multiplicity in figure and text do not match

    figure is correct - fix text

  • Updated: Tue, 8 Oct 2019 17:58 GMT
  • Attachments:

trailing bullet

  • Key: SACM21-70
  • Status: closed  
  • Source: MITRE ( Mr. Robert Martin)
  • Summary:

    JS5 - In 6.2 Acknowledgements, there is an extra trailing bullet.

  • Reported: SACM 2.0 — Mon, 18 Mar 2019 15:23 GMT
  • Disposition: Resolved — SACM 2.1
  • Disposition Summary:

    fix trailing bullet

    line after bulleted list has an empty bullet - removed.

  • Updated: Tue, 8 Oct 2019 17:58 GMT
  • Attachments:

SPMS version

  • Key: SACM21-69
  • Status: closed  
  • Source: MITRE ( Mr. Robert Martin)
  • Summary:

    JS4 - In 3.2 Non-normative References, SPMS is at 1.2, update doc number to formal/17-11-01.

  • Reported: SACM 2.0 — Mon, 18 Mar 2019 15:23 GMT
  • Disposition: Resolved — SACM 2.1
  • Disposition Summary:

    updating SPMS version reference

    In 3.2 Non-normative References, SPMS reference updated.

  • Updated: Tue, 8 Oct 2019 17:58 GMT
  • Attachments:

Typo on pdf pg 10

  • Key: SACM21-68
  • Status: closed  
  • Source: MITRE ( Mr. Robert Martin)
  • Summary:

    JS3 - Typo on pdf pg 10: Issues: hhttp in URI -> https

  • Reported: SACM 2.0 — Mon, 18 Mar 2019 15:22 GMT
  • Disposition: Resolved — SACM 2.1
  • Disposition Summary:

    hhttp to https

    typo in url and need to move to https

  • Updated: Tue, 8 Oct 2019 17:58 GMT
  • Attachments:

http -> https

  • Key: SACM21-67
  • Status: closed  
  • Source: MITRE ( Mr. Robert Martin)
  • Summary:

    JS2 - http -> https throughout for omg.org, please check other sites and changeover as possible for futureproofing ( on omg.org: pdf pgs 1, 3, 4, 9, 10, 16 and pdf pgs 16, 65, 67).

  • Reported: SACM 2.0 — Mon, 18 Mar 2019 15:22 GMT
  • Disposition: Resolved — SACM 2.1
  • Disposition Summary:

    http -> https for document urls?

    Reviewed pdf pgs 1, 3, 4, 9, 10, 16 and pdf pgs 16, 65, 67 and updated urls for https were applicable and resolved broken url for fda document.

  • Updated: Tue, 8 Oct 2019 17:58 GMT
  • Attachments:

SACM21-20 the changes are inconsistent with pdf

  • Key: SACM21-65
  • Status: closed  
  • Source: MITRE ( Mr. Robert Martin)
  • Summary:

    RB2 – For SACM21-20 the changes are inconsistent with the changes specified in the associated PDF file. In Concrete Syntax.pdf, Figure 11.2 contains the title "Concrete Syntax for ArguementPackage" whereas "ArgumentPackage" is used in the actual text. The misspelled version is still present in the table of contents.

  • Reported: SACM 2.0 — Mon, 18 Mar 2019 15:20 GMT
  • Disposition: Resolved — SACM 2.1
  • Disposition Summary:

    Arguement-Argument

    Correct spelling now shown in the track changes and clean specifications - see RB2-Arguement-Argument.pdf

  • Updated: Tue, 8 Oct 2019 17:58 GMT
  • Attachments:

SACM21-14 and SACM21-16 bad urls

  • Key: SACM21-64
  • Status: closed  
  • Source: MITRE ( Mr. Robert Martin)
  • Summary:

    RB1 – Two of the issues, SACM21-14 and SACM21-16, referred to bad urls and were marked as “Closed; No Change,” but the resolution was not specified – what was done to resolve these two issues?

  • Reported: SACM 2.0 — Mon, 18 Mar 2019 15:20 GMT
  • Disposition: Closed; No Change — SACM 2.1
  • Disposition Summary:

    URL reactivated

    The web site behind the urls had lost its registration on the University of York DSN system – that was fixed in a day or so.

  • Updated: Tue, 8 Oct 2019 17:58 GMT

Address missing elements of first 12 issues and address style consistency

  • Key: SACM21-13
  • Status: closed  
  • Source: MITRE ( Mr. Robert 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
  • Disposition: Closed; No Change — SACM 2.1
  • Disposition Summary:

    Mistakenly rolled from SACM 2.0 FTF to SACM 2.1 RTF even though addressed/closed

    SACM 2.1 RTF Issues 1-13 were mistakenly rolled over from the SACM 2.0 FTF even though they were addressed and closed in that FTF.

  • Updated: Tue, 8 Oct 2019 17:58 GMT
  • Attachments:

Need for the ability to group SACMElements

  • Key: SACM21-12
  • Status: closed  
  • Source: MITRE ( Mr. Robert 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
  • Disposition: Closed; No Change — SACM 2.1
  • Disposition Summary:

    Mistakenly rolled from SACM 2.0 FTF to SACM 2.1 RTF even though addressed/closed

    SACM 2.1 RTF Issues 1-13 were mistakenly rolled over from the SACM 2.0 FTF even though they were addressed and closed in that FTF.

  • Updated: Tue, 8 Oct 2019 17:58 GMT
  • Attachments:

Better support for patterns is needed

  • Key: SACM21-11
  • Status: closed  
  • Source: MITRE ( Mr. Robert 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
  • Disposition: Closed; No Change — SACM 2.1
  • Disposition Summary:

    Mistakenly rolled from SACM 2.0 FTF to SACM 2.1 RTF even though addressed/closed

    SACM 2.1 RTF Issues 1-13 were mistakenly rolled over from the SACM 2.0 FTF even though they were addressed and closed in that FTF.

  • Updated: Tue, 8 Oct 2019 17:58 GMT

Simplification of ArtifactAssetRelationship

  • Key: SACM21-10
  • Status: closed  
  • Source: MITRE ( Mr. Robert 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
  • Disposition: Closed; No Change — SACM 2.1
  • Disposition Summary:

    Mistakenly rolled from SACM 2.0 FTF to SACM 2.1 RTF even though addressed/closed

    SACM 2.1 RTF Issues 1-13 were mistakenly rolled over from the SACM 2.0 FTF even though they were addressed and closed in that FTF.

  • Updated: Tue, 8 Oct 2019 17:58 GMT
  • Attachments:

Need to simplify the citation classes of SACM

  • Key: SACM21-9
  • Status: closed  
  • Source: MITRE ( Mr. Robert 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
  • Disposition: Closed; No Change — SACM 2.1
  • Disposition Summary:

    Mistakenly rolled from SACM 2.0 FTF to SACM 2.1 RTF even though addressed/closed

    SACM 2.1 RTF Issues 1-13 were mistakenly rolled over from the SACM 2.0 FTF even though they were addressed and closed in that FTF.

  • Updated: Tue, 8 Oct 2019 17:58 GMT
  • Attachments:

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

  • Key: SACM21-8
  • Status: closed  
  • Source: MITRE ( Mr. Robert 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
  • Disposition: Closed; No Change — SACM 2.1
  • Disposition Summary:

    Mistakenly rolled from SACM 2.0 FTF to SACM 2.1 RTF even though addressed/closed

    SACM 2.1 RTF Issues 1-13 were mistakenly rolled over from the SACM 2.0 FTF even though they were addressed and closed in that FTF.

  • Updated: Tue, 8 Oct 2019 17:58 GMT

Need more consistency in packages, interfaces and binding

  • Key: SACM21-7
  • Status: closed  
  • Source: MITRE ( Mr. Robert 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
  • Disposition: Closed; No Change — SACM 2.1
  • Disposition Summary:

    Mistakenly rolled from SACM 2.0 FTF to SACM 2.1 RTF even though addressed/closed

    SACM 2.1 RTF Issues 1-13 were mistakenly rolled over from the SACM 2.0 FTF even though they were addressed and closed in that FTF.

  • Updated: Tue, 8 Oct 2019 17:58 GMT
  • Attachments:

SACM needs support for Internationalization

  • Key: SACM21-6
  • Status: closed  
  • Source: MITRE ( Mr. Robert Martin)
  • Summary:

    Need to add internationalization of the languages used so that elements can be described using multiple languages

  • Reported: SACM 2.0b2 — Thu, 3 Aug 2017 19:14 GMT
  • Disposition: Closed; No Change — SACM 2.1
  • Disposition Summary:

    Mistakenly rolled from SACM 2.0 FTF to SACM 2.1 RTF even though addressed/closed

    SACM 2.1 RTF Issues 1-13 were mistakenly rolled over from the SACM 2.0 FTF even though they were addressed and closed in that FTF.

  • Updated: Tue, 8 Oct 2019 17:58 GMT
  • Attachments:

Simplification of elements contained in packages

  • Key: SACM21-5
  • Status: closed  
  • Source: MITRE ( Mr. Robert Martin)
  • Summary:

    In packages (e.g. ArgumentPackage, TerminologyPackage), atomic references are too complicated.

  • Reported: SACM 2.0b2 — Thu, 3 Aug 2017 19:16 GMT
  • Disposition: Closed; No Change — SACM 2.1
  • Disposition Summary:

    Mistakenly rolled from SACM 2.0 FTF to SACM 2.1 RTF even though addressed/closed

    SACM 2.1 RTF Issues 1-13 were mistakenly rolled over from the SACM 2.0 FTF even though they were addressed and closed in that FTF.

  • Updated: Tue, 8 Oct 2019 17:58 GMT
  • Attachments:

Need to simplify internationalization support in Expressions.

  • Key: SACM21-4
  • Status: closed  
  • Source: MITRE ( Mr. Robert 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
  • Disposition: Closed; No Change — SACM 2.1
  • Disposition Summary:

    Mistakenly rolled from SACM 2.0 FTF to SACM 2.1 RTF even though addressed/closed

    SACM 2.1 RTF Issues 1-13 were mistakenly rolled over from the SACM 2.0 FTF even though they were addressed and closed in that FTF.

  • Updated: Tue, 8 Oct 2019 17:58 GMT

Alow AssertedRelationship to express if it is a counter relationship

  • Key: SACM21-3
  • Status: closed  
  • Source: MITRE ( Mr. Robert 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
  • Disposition: Closed; No Change — SACM 2.1
  • Disposition Summary:

    Mistakenly rolled from SACM 2.0 FTF to SACM 2.1 RTF even though addressed/closed

    SACM 2.1 RTF Issues 1-13 were mistakenly rolled over from the SACM 2.0 FTF even though they were addressed and closed in that FTF.

  • Updated: Tue, 8 Oct 2019 17:58 GMT
  • Attachments:

Simplify ArtifactElement and its sub-types

  • Key: SACM21-2
  • Status: closed  
  • Source: MITRE ( Mr. Robert 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
  • Disposition: Closed; No Change — SACM 2.1
  • Disposition Summary:

    Mistakenly rolled from SACM 2.0 FTF to SACM 2.1 RTF even though addressed/closed

    SACM 2.1 RTF Issues 1-13 were mistakenly rolled over from the SACM 2.0 FTF even though they were addressed and closed in that FTF.

  • Updated: Tue, 8 Oct 2019 17:58 GMT
  • Attachments:

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

  • Key: SACM21-1
  • Status: closed  
  • Source: MITRE ( Mr. Robert 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
  • Disposition: Closed; No Change — SACM 2.1
  • Disposition Summary:

    Mistakenly rolled from SACM 2.0 FTF to SACM 2.1 RTF even though addressed/closed

    SACM 2.1 RTF Issues 1-13 were mistakenly rolled over from the SACM 2.0 FTF even though they were addressed and closed in that FTF.

  • Updated: Tue, 8 Oct 2019 17:58 GMT
  • Attachments:

B and A or A and B

  • Key: SACM21-31
  • Status: closed  
  • Source: MITRE ( Mr. Robert Martin)
  • Summary:

    p39:Last sentences of 11.13 and 11.14: Is A and B intentionally exchange in "the truth of" parts of the two sentences?

    11.13: "An inference asserted between two claims (A � the source � and B � the target) denotes that the truth of Claim A is said to infer the truth of Claim B."

    11.14: "An AssertedInference between two claims (A � the source � and B � the target) denotes that the truth of Claim B is said to infer the truth of Claim A."

    I would expect that the inference of truth comes from the source and is asserted for the target so the other way than 11.14 Semantics part defines. [Remark: I am not a native English speaker so it might be strange just for me why the "said to infer" expression is used instead of "inferred from". I interpret "The truth of X is said to infer the truth of Y." as "Truth of Y can be inferred from the truth of X." or "The truth of X logically necessitates the truth of Y."- is it correct?]

  • Reported: SACM 2.0 — Sun, 17 Feb 2019 04:03 GMT
  • Disposition: Resolved — SACM 2.1
  • Disposition Summary:

    A and B are mistakenly swapped in the specification text

    Need to revise labels in section 11.14 to correctly describe the functionality.

  • Updated: Tue, 8 Oct 2019 17:58 GMT
  • Attachments:

Replace "that" with "whether"?

  • Key: SACM21-30
  • Status: closed  
  • Source: MITRE ( Mr. Robert Martin)
  • Summary:

    p38, 11.13, Attributes: If "isCounter" seems to be set to false then stating that "a flag indicating that the AssertedRelationship counters its declared purposes" seems to be controversial, although I understand that the "false" is a default value. I think, adding "that whether the AssertedRelationship counters" is more clear. E.g. in 11.10 at a similar case, it writes "indicating the state ..." which was more clear.

  • Reported: SACM 2.0 — Sun, 17 Feb 2019 04:03 GMT
  • Disposition: Resolved — SACM 2.1
  • Disposition Summary:

    Whether for that

    The observation is correct - replacing "That" with "Whether" in Section 11.13

  • Updated: Tue, 8 Oct 2019 17:58 GMT
  • Attachments:

Spelling mistake in 11.8

  • Key: SACM21-25
  • Status: closed  
  • Source: MITRE ( Mr. Robert Martin)
  • Summary:

    The section title "Literals" is misspelled.

  • Reported: SACM 2.0 — Sat, 16 Feb 2019 19:26 GMT
  • Disposition: Closed; No Change — SACM 2.1
  • Disposition Summary:

    Mistakenly opened issue on spelling mistake.

    This is correct in specification - was looking at wrong version.

  • Updated: Tue, 8 Oct 2019 17:58 GMT

Spelling mistake in 2.5

  • Key: SACM21-22
  • Status: closed  
  • Source: MITRE ( Mr. Robert Martin)
  • Summary:

    Terminology misspelled as "Termonology" in Section 2.5

  • Reported: SACM 2.0 — Sat, 16 Feb 2019 18:58 GMT
  • Disposition: Closed; No Change — SACM 2.1
  • Disposition Summary:

    Again was looking at the wrong version of the SACM file

    The term is correctly spelled - no change needed.

  • Updated: Tue, 8 Oct 2019 17:58 GMT

Mistake in element name in 2.3 text

  • Key: SACM21-21
  • Status: closed  
  • Source: MITRE ( Mr. Robert Martin)
  • Summary:

    Mistake in element name – remove “Model” from ArtifactModel::ArtifactPackage

  • Reported: SACM 2.0 — Sat, 16 Feb 2019 18:56 GMT
  • Disposition: Resolved — SACM 2.1
  • Disposition Summary:

    Name of element in compliance point mistakenly has "Model" in it

    Revise in specification section 2.3 - SACM 2.0 metamodel is not impacted.
    ArtifactModel::ArtifactPackage should be Artifact::ArtifactPackage

  • Updated: Tue, 8 Oct 2019 17:58 GMT
  • Attachments:

Concepts in SACM 2 have no direct graphical notation

  • Key: SACM21-20
  • Status: closed  
  • Source: MITRE ( Mr. Robert Martin)
  • Summary:

    Need a concrete syntax for the Argumentation metamodel that can represent the semantic definitions of the elements for semantic transparency, easing the burden of learning the elements and allowing them to be perceived directly from the notation.

  • Reported: SACM 2.0 — Sat, 16 Feb 2019 18:54 GMT
  • Disposition: Resolved — SACM 2.1
  • Disposition Summary:

    Concrete Syntax and Graphical notation

    As a result of the work by a graduate student at University of York - which was presented in draft at the March and September meetings we now have a proposed graphical notation for the Argumentation portions of SACM. The proposed revisions to the last part of Section 1 to add this to the history of SACM, along with a new compliance point (2.6) for those choosing to support the notation, update to section 5 on symbols, and the specific notations in many parts of section 11, as well as examples in the new Annex C are provided.

  • Updated: Tue, 8 Oct 2019 17:58 GMT
  • Attachments:

Missing role discription for terminology model

  • Key: SACM21-19
  • Status: closed  
  • Source: MITRE ( Mr. Robert Martin)
  • Summary:

    There is no discussion of the terminology model’s role in SACM.

  • Reported: SACM 2.0 — Sat, 16 Feb 2019 18:32 GMT
  • Disposition: Resolved — SACM 2.1
  • Disposition Summary:

    No discussion of the role of the terminology model

    In the scope of SACM we should include a discussion of vocabulary and the role of the terminology model at a high level.

  • Updated: Tue, 8 Oct 2019 17:58 GMT
  • Attachments:

Misleading section title for 1.3 Artifact

  • Key: SACM21-18
  • Status: closed  
  • Source: MITRE ( Mr. Robert Martin)
  • Summary:

    The Artifact title is misleading label for this portion of the scope description, this section is actually is about Evidence.

  • Reported: SACM 2.0 — Sat, 16 Feb 2019 18:30 GMT
  • Disposition: Closed; No Change — SACM 2.1
  • Disposition Summary:

    Mistakenly opened issue on Section number name.

    Thought section was named "Artifact" and wanted to change it to "Evidence" but in fact it was already named that way. Had looked at earlier version of specification.

  • Updated: Tue, 8 Oct 2019 17:58 GMT

Outdated constraints for class Claim

  • Key: SACM21-62
  • Status: closed  
  • Source: LogicalHacking.com ( Achim D. Brucker)
  • Summary:

    The constraint section of the class Claims revers to two attributes ("assumed" and "toBeSupported") that are not part of the SACM 2.0 metamodel (they are replaced by the attribute "assertionDeclaration" of type "AssertionDeclaration).

    Proposed fix:

    Remove the constraint section. It is no longer required, as the "exclusive or"-constraint is already enforced by AssertionDeclaration being an enumeration.

  • Reported: SACM 2.0 — Tue, 19 Feb 2019 19:30 GMT
  • Disposition: Duplicate or Merged — SACM 2.1
  • Disposition Summary:

    Duplicative request for removal of constraint from 11.11

    Addressed in ballot 3.

  • Updated: Tue, 8 Oct 2019 17:58 GMT

In 11.13 the +target should have multiplicity of 1

  • Key: SACM21-58
  • Status: closed  
  • Source: MITRE ( Mr. Robert Martin)
  • Summary:

    The multiplicity of +target should be 1 (target:ArgumentAsset[1]).

  • Reported: SACM 2.0 — Mon, 18 Feb 2019 03:18 GMT
  • Disposition: Resolved — SACM 2.1
  • Disposition Summary:

    In 11.13 the +target should have multiplicity of 1

    Update text, diagrams, and emof model.

  • Updated: Tue, 8 Oct 2019 17:58 GMT
  • Attachments:

Unnecessary constraint statement in 11.11

  • Key: SACM21-55
  • Status: closed  
  • Source: MITRE ( Mr. Robert Martin)
  • Summary:

    The constraint statement in 11.11 is unnecessary since there is no longer an assumed nor a toBeSupported attribute in the standard

  • Reported: SACM 2.0 — Mon, 18 Feb 2019 02:59 GMT
  • Disposition: Resolved — SACM 2.1
  • Disposition Summary:

    remove unnecessary constraint statement in 11.11

    There is no longer an assumed nor a toBeSupported attribute in the standard, can remove the constraint.

  • Updated: Tue, 8 Oct 2019 17:58 GMT
  • Attachments:

Graphical notation for SACM Argumentation concepts

  • Key: SACM21-107
  • Status: closed  
  • Source: MITRE ( Mr. Robert Martin)
  • Summary:

    Shouldn't have a compliance point for the Concrete Syntax as part of this revision.

  • Reported: SACM 2.0 — Mon, 18 Mar 2019 20:58 GMT
  • Disposition: Resolved — SACM 2.1
  • Disposition Summary:

    Graphical notation for SACM Argumentation concepts

    Remove the compliance point and definitions for a graphical notation that maps to all of SACM Argumentation concepts from the body of the specification and putting that graphical notation into an new Annex to parallel the existing notation mappings to SACM contained in Annex A.

    Three supporting pdfs provided to 1) remove compliance point and notation definitions from main body, 2) rename Annex C examples to Annex D, and 3) create new Annex C with graphical notations that represent all SACM Argumentation concepts.

  • Updated: Tue, 8 Oct 2019 17:58 GMT
  • Attachments:

Date or date in 12.9

  • Key: SACM21-75
  • Status: closed  
  • Source: MITRE ( Mr. Robert Martin)
  • Summary:

    JS10 – In 12.9 Event, under Attributes, date:Date[0..1] does not match naming of attribute in Figure 12.1, which is occurence:date[0..1]

  • Reported: SACM 2.0 — Mon, 18 Mar 2019 15:28 GMT
  • Disposition: Resolved — SACM 2.1
  • Disposition Summary:

    Date or date in 12.9

    aligned text

  • Updated: Tue, 8 Oct 2019 17:58 GMT
  • Attachments:

Date or date in 12.7

  • Key: SACM21-74
  • Status: closed  
  • Source: MITRE ( Mr. Robert Martin)
  • Summary:

    JS9 - In 12.7 Artifact, under Attributes, date:Date[0..1] does not match naming of type in Figure 12.1, which is date:date[0..1]

  • Reported: SACM 2.0 — Mon, 18 Mar 2019 15:27 GMT
  • Disposition: Resolved — SACM 2.1
  • Disposition Summary:

    Date or date in 12.7

    align spelling

  • Updated: Tue, 8 Oct 2019 17:58 GMT
  • Attachments:

text and figure mismatch ArgumentPackage<-->ArgumentPackageInterface

  • Key: SACM21-73
  • Status: closed  
  • Source: MITRE ( Mr. Robert Martin)
  • Summary:

    JS8 – In 11.5 ArgumentPackageBinding, under Associations, participantPackage is listed as ArgumentPackageInterface, should be ArgumentPackage to match Figure 11.1.  Change type, or diagram.  The analogous Sec 12.4 ArtifactPackageBinding indicates the diagram here is likely correct.

  • Reported: SACM 2.0 — Mon, 18 Mar 2019 15:26 GMT
  • Disposition: Resolved — SACM 2.1
  • Disposition Summary:

    address discrepancy between text and figure

    Figure is correct - made text change

  • Updated: Tue, 8 Oct 2019 17:58 GMT
  • Attachments:


Incorrect description of package

  • Key: SACM21-17
  • Status: closed  
  • Source: TGR Safety Management Ltd ( Timothy G Rowe)
  • Summary:

    The specification relates to ArtifactPackage, but the description of the package describes it as ArgumentPackage.

  • Reported: SACM 2.0 — Tue, 12 Jun 2018 01:56 GMT
  • Disposition: Resolved — SACM 2.1
  • Disposition Summary:

    Element name mistake in 12.2

    In section 12.2 ArtifactPackage the element is mistakenly named ArgumentPackage - should be ArtifactPackage - correct in model.

  • Updated: Tue, 8 Oct 2019 17:58 GMT
  • Attachments:

Invalid URL

  • Key: SACM21-16
  • Status: closed   Implementation work Blocked
  • Source: gmail.com ( Timothy Rowe)
  • Summary:

    Details of the of the mapping between GSN elements and SACM are claimed to be at http://www.goalstructuringnotation.info/gsn-metamodel, but the link is invalid.

  • Reported: SACM 2.0 — Mon, 11 Jun 2018 02:00 GMT
  • Disposition: Closed; No Change — SACM 2.1
  • Disposition Summary:

    Fixed within a day of being reported

    This broken link was fixed within a few days of being reported.

  • Updated: Tue, 8 Oct 2019 17:58 GMT

Association is inconsistent with semantics

  • Key: SACM21-15
  • Status: closed  
  • Source: gmail.com ( Timothy Rowe)
  • Summary:

    The association `value` is shown as LangString[1..*], but the semantics describe it as a list of ExpressionLangString, not LangString.

  • Reported: SACM 2.0 — Sun, 10 Jun 2018 23:09 GMT
  • Disposition: Resolved — SACM 2.1
  • Disposition Summary:

    ExpressionLangString should be LangString

    Correct element name and change criteria from "must" to "should"

  • Updated: Tue, 8 Oct 2019 17:58 GMT
  • Attachments:

Broken Link

  • Key: SACM21-14
  • Status: closed   Implementation work Blocked
  • Source: gmail.com ( Timothy Rowe)
  • Summary:

    The link "http://www.goalstructuringnotation.info/sacm-examples
    Structured" leads to a "Site Unavailable" page.

  • Reported: SACM 2.0 — Fri, 8 Jun 2018 03:54 GMT
  • Disposition: Closed; No Change — SACM 2.1
  • Disposition Summary:

    Fixed within a day of being reported

    University of York had an issue with the routing to their web site - resolved shortly after it was reported.

  • Updated: Tue, 8 Oct 2019 17:58 GMT

Duplicative paragraphs?

  • Key: SACM21-29
  • Status: closed  
  • Source: MITRE ( Mr. Robert Martin)
  • Summary:

    p33: the last two paragraphs seem to be the same (from word to word) except the last words: "AssertedContext" and "ArtifactReference". I have no consistent understanding yet but it seems that the second paragraph should be removed (or something else was intended to be written there).

  • Reported: SACM 2.0 — Sun, 17 Feb 2019 04:02 GMT
  • Disposition: Resolved — SACM 2.1
  • Disposition Summary:

    Duplicative paragraphs needing revision

    The two paragraphs at the bottom of page 33 of the specification need to be rewritten and merged to remove duplicative materials.

  • Updated: Tue, 8 Oct 2019 17:58 GMT
  • Attachments:

Punctuation and spacing errors

  • Key: SACM21-24
  • Status: closed  
  • Source: MITRE ( Mr. Robert Martin)
  • Summary:

    In section 1.4 there is a missing "," after the word "Basically" at the beginning of the second sentence in the second paragraph. In section 9.2 "top level" should be hyphenated in the second sentence of the first paragraph. In the last sentence of section 11.1 the "." at the end is in the wrong place.

  • Reported: SACM 2.0 — Sat, 16 Feb 2019 19:23 GMT
  • Disposition: Resolved — SACM 2.1
  • Disposition Summary:

    Minor edits to address mistakes

    Add comma after Basically in 1.4, in 9.2 hyphenate top-level, and correctly place the period in 11.1

  • Updated: Tue, 8 Oct 2019 17:58 GMT
  • Attachments:

Spelling mistake in 9.1

  • Key: SACM21-23
  • Status: closed  
  • Source: MITRE ( Mr. Robert Martin)
  • Summary:

    The word contained is spelled as"containined"

  • Reported: SACM 2.0 — Sat, 16 Feb 2019 19:06 GMT
  • Disposition: Closed; No Change — SACM 2.1
  • Disposition Summary:

    Mistakenly opened issue on spelling mistake.

    Word correctly spelled - was looking at the wrong version of SACM.

  • Updated: Tue, 8 Oct 2019 17:58 GMT