Legacy Issue Number: 16855
Source: Adelard LLP ( Luke Emmet)
we need a common route to support instance packaging. Proposal is to use “Assurance
repository” as the main packaging element.
Reported: SACM 1.0b1 — Thu, 1 Dec 2011 05:00 GMT
Disposition: Resolved — SACM 1.0b2
Add Figure Administration to chapter 8 SACM Assurance Case as follows: << diagram on p 117 of ptc/2012-06-04>> Add section Administration
This section describes the common elements of SACM that are involved in managing
assurance cases, exchanging assurance cases and related concerns. The elements
described in this chapter organize instances of SACM. In particular, this section defines
the root object of an assurance case - the AssuranceCase element. This element contains
other objects in the assurance case, such as the Argumentation objects and
EvidenceContainer objects and constitutes a unit of exchange using the SACM as the
In addition, the SACM Argumentation Metamodel and the SACM Evidence Metamodel
constitute two independent protocols within SACM, so Argumentation packages can be
developed and exchanged using the Argumentation elements, and also the
EvidenceContainers can be developed, managed and exchanged independently of the
Argumentation elements or in combination with them. Independently developed
Argumentation packages and EvidenceContainer packages can be later assembled into
complete assurance cases. Specifications of the Evidence Metamodel can be used to
develop an evidence repository that can be used to store and manage evidence in support
of multiple assurance cases.
Add sub section AssuranceCase
AssuranceCase element Superclass
name:String the name of the assurance case
gid:String the globally unique identifier assigned to the current assurance case
argument:Argumentation::Argumentation[0..*] the argument component of the assurance
evidence:Evidence::EvidenceContainer[0..*] the evidence component of the assurance
An AssuranceCase element represents assurance cases as defined in ISO/IEC 15206.
Argument and Evidence components of an AssuranceCase are optional which allows
representing incomplete assurance cases.
An AssuranceCase element involves both a globally unique "gid" and a locally unique
"id". The global referencing scheme may involve gid+id combination, while a local
scheme may use id component.
Updated: Fri, 6 Mar 2015 20:58 GMT