>Now let's get a little crazy and see if people can follow what I am trying >to say ... > >If you use this approach formally there is an interesting result. Your >problem domain model that you've created turns out to be a sort >specification for a new modelling language. A modelling language that is >problem domain specific, simpler than UML and describes the domain at a >higher level than UML. > >If you wanted to take this one step more than you could use the MDR >repository to generate a JAVA API for your problem domain in exactly the >same way the MDR is used to generate the JAVA API for UML1.4. If you did >that then you could write your code generation templates for your cartridge >using only the generated JAVA API. You'd also automatically have an XML >representation for your simplified modelling lanaguage in exactly the same >way that UML1.4 has its XMI representation. > >Did that make any sense to anybody ? >
yeah, I think I get it ... so when you have an XML Schema for your new cartridge you can also validate UML models against this schema ? example: you could use this to show that the UML model that defines the car-rental-sample is syntactically correct and complete for the specific cartridges you want to use it on ? bye Wouter __________________________________________________________________ McAfee VirusScan Online from the Netscape Network. Comprehensive protection for your entire computer. Get your free trial today! http://channels.netscape.com/ns/computing/mcafee/index.jsp?promo=393397 Get AOL Instant Messenger 5.1 free of charge. Download Now! http://aim.aol.com/aimnew/Aim/register.adp?promo=380455 ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Andromda-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/andromda-devel
