Possible for two seperate models interact?

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   That's great, this is what we wanted.
Thank you very much! 
regards
Vegard and Christian

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
chrisrud Members Profile Send Private Message Find Members Posts Add to Buddy List Member Joined: 09.Oct.2008 Location: Norway Points: 5	Post Options Post Reply Quote chrisrud Report Post Thanks(0) Quote Reply Posted: 10.Oct.2008 at 13:38
	That's great, this is what we wanted. Thank you very much! regards Vegard and Christian

chrisrud Members Profile Send Private Message Find Members Posts Add to Buddy List Member Joined: 09.Oct.2008 Location: Norway Points: 5	Post Options Post Reply Quote chrisrud Report Post Thanks(0) Quote Reply Posted: 10.Oct.2008 at 14:19
	Hi again, not cruical, but interesting: Is it possible to refer an object that is not in the same repository and derived from a different dsl, without knowing its type? regards Vegard and Christian

stevek Members Profile Send Private Message Find Members Posts Add to Buddy List MetaCase Joined: 11.Mar.2008 Points: 643	Post Options Post Reply Quote stevek Report Post Thanks(0) Quote Reply Posted: 10.Oct.2008 at 14:31
	As I said above, you can't refer directly to an object in a different repository. Or rather, all the wonderful things MetaEdit+ can do for direct references in the same repository can't help you in making links to a different repository. You can't really update the name in one place and hope that it will be updated automatically in some other random repository :-). Since we're all used to this from source code, it's hardly a new problem. You just have to make sure you copy&paste or type the same name. Given that MetaEdit+ can solve that problem for 99% of your links, it's hopefully OK if for the last 1% you still need to do it in the old familiar way. If the figure is significantly greater than 1%, you may want to revisit your design and aim for better cohesion and lower coupling. Think what happens when you have multiple people working on multiple models in multiple repositories, with multiple versions of each repository. In that situation, UML-like solutions are terrible or require draconian rules, DSM solutions work just fine: a large part of the difference is in having direct references and good modularization.

jpt Members Profile Send Private Message Find Members Posts Add to Buddy List MetaCase Joined: 25.Mar.2008 Points: 253	Post Options Post Reply Quote jpt Report Post Thanks(0) Quote Reply Posted: 10.Oct.2008 at 15:12
	Hi, I don’t know your requirements for the language support and its use case, but I would define an integrated metamodel rather than try to develop a solution consisting of multiple disconnected models that need to be updated and kept connected with extra effort. In database world we define a schema to store the data and keep it updated and consistent. This is opposite to having multiple different kind of files that then refer to each other via some mechanisms for creation, update and deletion of their individual items. By defining a metamodel that allows to integrate design data based on different languages makes modeling work . I would also argue that the actual language definition becames then easier for you too. Yours, Juha-Pekka