This paper considers that there are two important views of Model Driven Engineering. One consists in starting with a well known standard universal modeling language like UML 2.0 and to define restrictions and extensions to this all-purpose language by the way of so-called &quot;profiles&quot;. The other possibility consists in using small, well-focused Domain Specific Languages and to deal with the coordination between these. We will not discuss here the pros and cons of both approaches but we will consider that each has many supporters while the debate is going on. UML CASE tools currently produce a significant legacy, mainly of UML profiles. Bridges between both modeling worlds will surely be most needed in the future. We consider this bridging problem to be a hard one and we propose to use some advanced modeling tools to solve it. We show how a combination of a model-transformation tool (ATL) and a model-weaving tool (AMW) may help solving this problem. We also show how to take advantage of higherorder transformations in this endeavor
To submit an update or takedown request for this paper, please submit an Update/Correction/Removal Request.