Legacy Issue Number: 16510
Source: MITRE ( Samuel Redwine)
Not just exhibits have events that affect them or otherwise relate to them. This is also relavent to what the elements represent.
An event might be associated with more than one element
For example, one bug fix that simultaneously change several code exhibits/artifacts.
Reported: ARM 1.0b1 — Thu, 25 Aug 2011 04:00 GMT
Disposition: Closed; No Change — SACM 2.0
Addressed by harmonization to create SACM 2.0.
In SACM 2.0 ArtefactEvents are optionally recorded as part of an Artefact’s description. They are intended to describe events relating to the artefact rather than events relating to the Artefact model element.
Versioning of all of the other model elements lies outside the scope of the exchange model. Versioning information could be added to every model element (if required) using TaggedValue (which could use a community consensus vocabulary established using the Terminology package). However, because there are many ways to maintain version information, we decided to not standardize this.
The relationship of an Activity (e.g. fixing a bug) to multiple Artefacts can be recorded in SACM 2.0 as a many-to-one ArtefactActivityRelationship.
Updated: Tue, 19 Dec 2017 20:05 GMT
SACM2 — Events should be able to be Associated with all Kinds of ModelElements
- Key: SACM2-22
- OMG Task Force: SACM 2.0 FTF