-
Key: SACM2-20
-
Legacy Issue Number: 16506
-
Status: closed
-
Source: MITRE ( Mr. Samuel Redwine)
-
Summary:
Obviously, properties that apply to Model Elements must be distinguishable from Properties of what they represent. Both these kinds of properties appear in SACM models. The issues titled “Property Inherence Hierarchy” states a way of doing this.
-
Reported: ARM 1.0b1 — Thu, 25 Aug 2011 04:00 GMT
-
Disposition: Closed; No Change — SACM 2.0
-
Disposition Summary:
Addressed by harmonization to create SACM 2.0.
In SACM 2.0 we have a clear ArtefactProperty class to capture properties of an Artefact. This, for example, is separate from the ability to attach UtilityElements to an Model Element (that can be used to capture Model Element Properties, e.g. using TaggedValue). Standardised vocabularies and expressions for domain properties can be captured using a Terminology package (which supports inheritance).
-
Updated: Tue, 19 Dec 2017 20:05 GMT
SACM2 — Properties of Model Elements must be Distinguished from Properties of what they Represent
- Key: SACM2-20
- OMG Task Force: SACM 2.0 FTF