Hi Matthias, On 10/27/05, Matthias Bohlen <[EMAIL PROTECTED]> wrote: > just a flash update of the status of the work on model to model > transformations: Thanks for the update.
> * I am writing an ATL adapter for AndroMDA's configuration so that ATL > will be able to understand the AndroMDA configuration (namespace > properties and mappings) as a model with a defined metamodel, the > "Config" metamodel. For this, I extend the ASMModel class in ATL. > (While working on the derived class, I see some urgent need for > refactoring in ASMModel itself, a fact that is already known in the > ATL team). This will allow me to access AndroMDA's configuration from > inside an ATL script. Are you trying to stick to models in MDR (MOF) or are you already using EMF (ECORE) models? I hoped you would stick to MDR since our MoTMoT tool currently only supports MOF based models... Future versions of MoTMoT will probably support ECORE as well but it's not a high priority for us at the moment. > * After the tests run fine (sort of "proof of concept"), I'll describe > all this in a session at OOP 2006 (see www.oopconference.com) and in > an article for ObjektSpektrum 2/2006. Please keep us updated on that as well. > * Then, I want to design a "pipes and filters" architecture for > transformations in AndroMDA. One aspect will be the configuration of > such graphs (not only chains) of transformations as XML files. One > transformation will be able to accept many input models and will > produce one output model. So, the nodes of the directed graph will > have many incoming edges and one outgoing edge. Why only one outgoing edge? Why XML? I have found activity diagrams a useful notation for describing the control flow of such a transformation chain. You basically use activity diagrams with data flow semantics (Yourdon and Coad, Gane and Sarson). Regular states represent DFD sinks (repository extents, conforming to a metamodel) and object flow states represent DFD processes (model transformations, written in ATL, SDM, ...). Transitions (and synchronization bars) between these states allow you to define sequentially or concurrently running model transformations. A brief example can be found in http://www.lore.ua.ac.be/refactoringProject/publications/VanGorp2004EDOC.pdf, Figure 6. Best regards, Pieter. ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information
