Relating Marks and Model Elements
We've elegantly avoided one critical issue so far: How do we connect the marks to the model elements to which they may pertain?
In the remote/local example, the mark only applies to actions that read, write, or clear an attribute. In the UML metamodel, those actions are modeled as a supertype StructuralFeatureAction, and each attribute action can be local or remote. The result is that the mark AccessorType is somehow associated with StructuralFeatureAction.
After all this ranting about keeping the marks separate from models, it would be pathological now to pollute the metamodel with marking model concepts. Just as we viewed marks as lightweight, nonintrusive extensions added to the developer model, so too we ...
Get MDA Distilled: Principles of Model-Driven Architecture now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
