IBM Systems Journal - Model-driven software development
Defining domain-specific modeling languages to automate product derivation: collected experiences
SPLC'05 Proceedings of the 9th international conference on Software Product Lines
A canonical scheme for model composition
ECMDA-FA'06 Proceedings of the Second European conference on Model Driven Architecture: foundations and Applications
Realizing Model Transformation Chain interoperability
Software and Systems Modeling (SoSyM)
Deriving correspondence relationships to guide a multi-view heterogeneous composition
MODELS'09 Proceedings of the 2009 international conference on Models in Software Engineering
Hi-index | 0.00 |
A transformation chain (TC ) generates applications from high-level models that are defined in terms of problem domain concepts. The result is a low-level model that is rooted in the solution domain. The evolution of a TC is a complex and expensive endeavor since there are intricate dependencies between all its constituent parts. More specific, an evolution problem arises when we need to add an unanticipated concern (e.g., security) that does not fit the expressiveness of the high-level metamodel, because such an addition forces us to adapt existing assets (i.e., metamodels, models, and transformations). We present a solution that adds a new concern model to the TC, in an independent way.