KDM14 — Change specification to allow stereotyping of Audit elements

Currently the KDM doesn’t allow for the stereotyping of Audit elements since those inherit from Element and not ModelElement.

We believe that this is an oversight, as a reading of the specification uses the Audit element by name as one of the possible owner of a stereotype (10.5.1 constraint #5: KDM

meta-elements (for example, “KDMEntity,” or “Audit”)) or the endpoint to a TaggedRef (10.5.2 constraint #4: KDM meta-element (for example, “KDMEntity,” or

“Audit”))

We are proposing the following changes to restore this capability that was clearly intended to exist in the first place:

· Move the stereotype relation from ModelElement to Element

· Change the endpoint of the reference relation in TaggedRef to now point to Element instead of ModelElement

· Change all text that refers to ModelElement as being subject to extension in favor of Element

Another possible approach that might be simpler is to derived the Audit from ModelElement instead of Element. Probably the only issue at hand is if it fits the definition given in 9.3.2 as being an element of the existing software system or not. That is a bit of a stretch here, but we could see this as being argued either way in the case of Audit.

Introduce Core class ExtendableElement and change subclass of Audit

in core package: Add class diagram Element to Core. Introduce abstract Core classes AnnotatableElement, AnnotationElement, ExtendableElement and ExtensionElement. Make ModelElement a subclass of ExtendableElement.
in kdm package: Make Audit a subclass of ExtendableElement.
Make Attribute, Annotation subclasses of AnnotationElement
Make ExtendedValue, Stereotype, TagDefinition, ExtensionFamily subclasses of ExtensionElement.
Then on Figure 10.3 we could have ExtendableElement instead of ModelElement.
Clarify descriptions.