SACM2 — 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.

Because all the significant classes of the argumentation and artefact package inherit from ModelElement, and ModelElement must use the Description class to provide content (e.g. the text of a Claim), and Descriptions must (given the current multiplicity) contain an Expression object, both argumentation and artefact packages must use the terminology package.

Fix model to allow Terminology Package to be optional as intended

The multiplicity from TaggedValue to Expression and UtilityElement to Expression must be changed from ‘1’ to ‘0..1’ to allow this to be optional. In addition, a new attribute called “sExpression: String” (referring to ‘simple expression’) should be added to UtilityElement, and an additional attribute called “sKey: String” (referring to ‘simple Key’) should be added to TaggedValue.

In Section 8.4 (The description of UtilityElement) the following text needs to be added:

“Attributes
sExpression: String – the text that describes the value of the UtilityElement”

and

“Constraints
If an Expression class is associated (through the expression association) with UtilityElement then sExpression should be null”

In Section 8.8 (The description of TaggedValue) the following text needs to be added to the current ‘Attributes’ section:

“sKey: Expression – the text that describes the key of the tagged value”

and the following text to the existing ‘Constraints’ section:

“If an Expression class is associated (through the key association) with TaggedValue then sKey should be null”

See the pdf “The SACM 2.0 meta-model requires implementation of the Terminology Package.pdf” for markup of proposed changes to figures and “Terminology Package Implementation-8.4 and 8.8.pdf” for text changes.