Model-driven architecture (MDA) is a potential next level of abstraction in the production of software. The principle is that the solution to the problem is expressed using a modeling language, which is then translated by a model compiler into source code. That source code is then converted into executable code. The potential for increased efficiency is obviously enormous. The ability to express solutions in a high- level abstract language alone will provide substantial benefits. Once it is possible to mechanically convert the solution into an executable form, one middle step in the software development process will be eliminated.
While there are many legitimate doubts that can be expressed about the current state of MDA implementation, it has progressed to the point where all development teams should perform an initial investigation. When that point is reached, you should reach for this book. As the name implies, this is a primer/overview of what MDA is, how it is organized and the notations used to express the various elements of MDA.
I found the book to be an excellent introduction to what MDA is, how it will be implemented and the advantages that it offers. It starts with a chapter on the basic terminology, which is followed by chapters on building models, building metamodels, building marking models, building languages and building executable models. I found the chapters on building marking models and building languages the most interesting. Marks are additional inputs used in the transformation of the model into source code. They are needed to represent the problem specific features of the current solution. Since there are so many different ways in which software is used, area specific modeling languages are needed. The description of how languages for this can be built was very interesting.
At this point, no one knows how effective MDA will be in software development. However, there is no question that it will have an impact and this book will teach you the how and why.