Model weaving
The separation of concerns in software system modeling avoids the construction of large and monolithic models which could be difficult to handle, maintain and reuse. At the same time, having different models (each one describing a certain concern) requires their integration into
a final model representing the entire domain [1]. Model weaving can be used in this scenario. Although there is no accepted definition of model weaving, in [2] it is considered as the operation for setting fine-grained relationships between models or metamodels and executing operations on them based on the semantics of the weaving associations specifically defined for the considered application domain.
The concept of weaving is not new. Adhering to the “everything is a model” principle [2], model weaving offers a number of advantages. All the information, relationships and correspondences between the considered models, could be described by specialized weaving models avoiding to have large metamodels for capturing all the aspects of a system. Furthermore, metamodels focusing on their own domain can be individually maintained, and at the same time interconnected into a “lattice of metamodels” [2]. In other words, each meta-model could represent a domain-specific language dealing with a particular view of a system, while weaving links permit describing the aspects both separately and in combination.
References
[1] T. Reiter, E. Kapsammer,W. Retschitzegger, andW. Schwinger. Model Integration Through Mega Operations. 2005. accepted for publication at the Workshop on Model-driven Web Engineering (MDWE2005).
[2] J. Bézivin. On the Unification Power of Models. Jour. on Software and Systems Modeling (SoSyM), 4(2):171–188, 2005.
Subscribe to RSS feed.
Rien ne se perd,
rien ne se crée, tout se transforme
