Welcome to weblogs.com.pk Sign in | Join | Help

Model Driven Architecture

In response to Oxymoron’s post about MDA book:


In the current state, there is a need of lot of work and improvement in the Model Driven Architecture. Before writing anything further, let me clear, that I myself is a big fan of MDA! Its just what I wish!


Need of new Models and/or model objects


The current standards yet have to cover many widely used techniques and approaches, is there any MDA approach for web applications? Yes? Common get serious, we need something to denote server side logics, client side scripts, style sheets, templates, portlets. We also need support for Events, Exceptions, Enumerations, Delegates etc (Excuse me if I am mistaken, I checked UML few months back)




The MDA approach often failed in the product cycle, when we need versioning support. They say, we need model first, and code second, but what about second iteration. The models start getting out of synch as soon as second iteration start, and sometime even in first iteration, especially when the architect is not closely involved with the development team. The coder in the team may adopt slightly different approach, and he might not update the model accordingly.


Storage Mechanism/Import-Export


There is a need of standardized storage mechanism (may be XML). So that models do not get out of synch, architects can store the models at some central place, from where coders can get the models and covert the models into code. Using import-export mechanism, it will be much easier, that architects can view the model visually using the tools of their choice, and coders can integrate them into their IDEs using code generators or manual approach.


IDE Integration


This is the key to success take for example Visual Studio. How it helped in Visual C++ success. IDEs are no longer an environment to write code, they are becoming the centre of software development universe. This is the main reason of Eclipse success for Java, and Visual Studio .Net success for Microsoft.Net platforms.


The IDEs also play important role, not only in success of any platform, or any language, but also the concepts associated. See how Visual C# has made its roots as strong as Java. This has become only possible due to the availability of super cool IDE, Visual Studio .Net.


The MDA vendors has also realized that along offering separate tools, they should also offer IDE integrated solutions, like Rational XDE series and Borland’s Together series.


For Java, unfortunately, for some unknown reasons, instead of having native to operating system, the vendors opted to develop IDE on Java and this is a reality, Java has failed in desktop applications, and so are its IDEs, no offence! Eclipse is different, and that is why its usage is increasing.


Visual Studio .NET is ultimate, see, it is not developed in VB, but VB users use it to develop things using VB!


Coming back to MDA, I think, there is a need of strong IDE integration, I am looking forward for Microsoft’s Whitehorse, but it has long way to go. Rational XDE should be made native to the platform, i-e its VS.NET version should be native to Windows, and its Java version can be what it is now, heavy, and slow :) Has anyone worked with Borland’s Together? Is it as heavy and slow as XDE?

Published Monday, April 5, 2004 12:26 PM by khurram
Filed under:


# re: Model Driven Architecture

Monday, April 5, 2004 7:57 PM by FarazTruehttp
Personally, I havent read enough about MDA to have an opinion about it. But speaking of skeptics, here's what Martin Fowler thinks about MDA:

New Comments to this post are disabled