Hi Shailesh,
There's no such thing as a silly question ;-)
What's interesting is to see which questions are being asked and how people receive the book, and the MDA concept!
I think the most common association people make when they hear the
word "architecture" is with the technical (ie. platform-specific) configuration of any particular software solution. This is a common understanding of what IT architecture is about.
Written in plain language: what MDA is talking about, and hence a common theme throughout Richard's book, is approaching architectural modeling from a higher level of abstraction - totally platform-independent - and modeling to as high a degree of functionality as possible before considering any specific implementation technologies. Clearly, what is then needed is to be able to translate the modeled architecture 100%, or as close to 100% as possible, to a high quality platform-specific infrastructure, capable of meeting the requirements laid down at the beginning.
The real value behind MDA then comes to light - the ability to re-deploy on other platforms with the same models, the ability to migrate from one app. server version to the next without having to remodel and rewrite large chunks of a system and being able to extend the resultant IT archictecture to satisfy future requirements with minimum effort and cost savings over previous methods.
I know it sounds like a dream come true but that's actually what the OMG MDA initiative is about and what Richard is describing in his book. A coming-together of many of the principles we all know under the control of an end-to-end set of standards which facilitate the enforcing of an architectural style throughout the whole cycle. It is also, by the way, what ArcStyler is designed to do, and has done in practice in various projects so far.
(I hope that wasn't too "evangelistic"?)
Robert