Model driven arcitecture is ready for prime time

The reason weʹre on the brink of moving toward the Object Management Groupʹs Model Driven Architecture (MDA) is that the technologies we use have grown significantly more complex over the last few years. Moreover, technology changes faster than the businesses weʹre trying to support with this technology. Why would I bother to implement a bidirectionally navigable association between two Enterprise JavaBean components if I can just draw an association between two classifiers in a Unified Modeling Language diagram? Moreover, why would I go to the trouble of creating all the technical detail involved in implementing an association manually if the result of doing so is not portable? It turns out that you can employ 3GLs to specify these platformsʹ use as well as you might use assembly language to create a Web-based customer relationship management system; theyʹre simply not the most appropriate way to express the systemʹs structure and behavior.