User Tools

Site Tools


dido:public:ra:xapend:xapend.b_stds:tech:omg:sacm

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
dido:public:ra:xapend:xapend.b_stds:tech:omg:sacm [2019/06/07 14:21]
nick
dido:public:ra:xapend:xapend.b_stds:tech:omg:sacm [2021/08/17 15:04] (current)
murphy [Scope]
Line 1: Line 1:
-======= OMG: Structured Assurance Case Metamodel (SACM) ​======= +===== OMG: Structured Assurance Case Metamodel (SACM) ===== 
-[[dido:​public:​stds:tech:omg| return to the OMG Standards ]]+[[dido:​public:​ra:​xapend:​xapend.b_stds:tech:omg:start| return to the OMG Standards ]]
  
 <​table>​ <​table>​
Line 6: Line 6:
 | Title                      |Structured Assurance Case Metamodel | | Title                      |Structured Assurance Case Metamodel |
 | Acronym ​                   | SACM | | Acronym ​                   | SACM |
-| Version ​                   | 2.1 beta +| Version ​                   | 2.1 | 
-| OMG Document Number ​       |  +| OMG Document Number ​       | formal/​20-04-01 ​
-| Publication Date           ​| ​March 2019  |+| Publication Date           ​| ​April 2020  |
 | About Specification ​       | [[https://​www.omg.org/​spec/​SACM]] | | About Specification ​       | [[https://​www.omg.org/​spec/​SACM]] |
-| Document ​                  | [[https://​www.omg.org/​spec/​SACM/​2.1/Beta1/PDF]]|+| Document ​                  | [[https://​www.omg.org/​spec/​SACM/​2.1/​PDF]]|
 </​table>​ </​table>​
  
-  : **Note**: The following is an excerpt from the actual document. It is provided here as a connivence ​and is not authoritative. Refer to the original document as the authoritative reference.+  : **Note**: The following is an excerpt from the actual document. It is provided here as a convenience ​and is not authoritative. Refer to the original document as the authoritative reference.
  
-====== Scope ====== +==== Scope ==== 
-===== General =====+  : //This specification defines a metamodel for representing structured assurance cases. An [[dido:​public:​ra:​xapend:​xapend.a_glossary:​a:​assurance|Assurance]] Case is a set of auditable [[dido:​public:​ra:​xapend:​xapend.a_glossary:​c:​claim|claims]],​ [[dido:​public:​ra:​xapend:​xapend.a_glossary:​a:​argument|arguments]],​ and [[dido:​public:​ra:​xapend:​xapend.a_glossary:​e:​evidence|evidence]] created to support the claim that a defined system/​service will satisfy the particular requirements. An Assurance Case is a document that facilitates information exchange between various system [[dido:​public:​ra:​xapend:​xapend.a_glossary:​s:​stakeholder|stakeholder]] such as suppliers and acquirers, and between the operator and regulator, where the knowledge related to the safety and security of the system is communicated in a clear and defendable way. Each assurance case should communicate the scope of the system, the operational context, the claims, the safety and/or security arguments, along with the corresponding evidence.//
  
-  : //This specification defines a metamodel for representing structured assurance cases. An Assurance ​Case is a set of auditable claimsarguments, and evidence created to support ​the claim that a defined system/​service will satisfy the particular requirementsAn Assurance ​Case is a document ​that facilitates information exchange between various system stakeholder such as suppliers ​and acquirers, and between the operator and regulator, where the knowledge related to the safety and security of the system ​is communicated in clear and defendable wayEach assurance case should ​communicate the scope of the system, the operational context, ​the claims, ​the safety ​and/or security arguments, along with the corresponding evidence.//+  : //Systems ​Assurance is the process ​of building clearcomprehensive, and defensible arguments regarding ​the safety and security properties of systemsThe vital element of Systems ​Assurance is that it makes clear and well-defined claims about the safety and security of systems. Certain claims are supported through reasoning. Reasoning ​is expressed by explicit annotated links between claims, where one or more claims (called [[dido:​public:​ra:​xapend:​xapend.a_glossary:​s:​subclaim|sub-claims]]) when combined provide inferential support to larger claim. Certain associations (recorded as assertions) between claims ​and subclaims can require supporting arguments of their own (e.g., justification of an asserted inference). Claims are propositions which are expressed by statements in some natural language. The degree of precision in formulation of the claims may contribute to the comprehensiveness of an assurance case. The context is important to communicate the scope of the claimand to clarify ​the language used by the claim by providing necessary definition and explanations. Context involves assumptions made about the system ​and its environment. Explicit statement of the assumptions contributes to the comprehensiveness of the argument. Argumentation flow between claims is structured to facilitate communication of the entire assurance case.//
  
-  : //Systems Assurance is the process of building clear, comprehensive,​ and defensible arguments regarding the safety and security properties of systems. The vital element of Systems Assurance is that it makes clear and well-defined claims about the safety and security of systems. Certain claims are supported through reasoning. Reasoning is expressed by explicit annotated links between claims, where one or more claims (called sub-claims) when combined provide inferential support to larger claim. Certain associations (recorded as assertions) between claims and subclaims can require supporting arguments of their own (e.g., justification of an asserted inference). Claims are propositions which are expressed by statements in some natural language. The degree of precision in formulation of the claims may contribute ​to the comprehensiveness of an assurance case. The context is important to communicate the scope of the claimand to clarify the language used by the claim by providing necessary definition and explanations. Context involves assumptions made about the system and its environment. Explicit statement of the assumptions contributes to the comprehensiveness of the argument. Argumentation flow between claims is structured to facilitate communication of the entire assurance case.//+/**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 
 +/* To add discussion page to this pagecomment out the line that says  
 +  ~~DISCUSSION:​off~~ 
 +*/ 
 +~~DISCUSSION:​on|Outstanding Issues~~ 
 +~~DISCUSSION:​off~~
dido/public/ra/xapend/xapend.b_stds/tech/omg/sacm.1559931696.txt.gz · Last modified: 2019/06/07 14:21 by nick