Registered: Sep, 2005
Re: The Real Meaning of Model-Driven Architecture
Posted: Jul 2, 2007 5:55 AM
> > The code that was generated was unreadable.
> The Model is your 'source' code while the code is
> The goal of MDA is that you may generate your business
> rules independently by the platform/application
> A class diagram will be transformed into a POJO object,
> EJB, copy cobol, xml schema etc. you may redefine you
> framework without rewrite a hundred of business rules by
> hand, you have only to change the transformer.
> Through uml paradigms static/dynamic diagrams, you trace
> the behavior of entire system.
> You give to the business unit the power of define rules
> The MDA approach is good both in small than in large
> application domain with different features of course (you
> have to justify the work of MDA development), but first
> model you application, model the data, keep MDA in mind.
> Use simple xml or your own model files definition or XMI
> or a model framework (EMF), but the concept is the same.
> Yes, the generated code will be unreadable but as the
> definition it is generated, untouchable (despite you may
> use jmerge for merging generated and hand-modified code).
Yeah, I get the theory. The problem is when you need to debug the system or realize that your MDA tool is crap, as we did.