What Is The Model Driven Architecture (mda) And How Is It Different F

1.	What Is The Model Driven Architecture (mda) And How Is It Different From Other Architectures?
Answer» The MDA is a new way of writing specifications and developing applications, based on a platform-independent model (PIM). A complete MDA specification consists of a definitive platform-independent base UML® model, plus one or more platform-specific models (PSM) and interface DEFINITION sets, each describing how the base model is implemented on a different MIDDLEWARE platform. A complete MDA application consists of a definitive PIM, plus one or more PSMs and complete implementations, one on each platform that the application DEVELOPER decides to support. MDA development focuses FIRST on the functionality and behavior of a distributed application or system, undistorted by idiosyncrasies of the technology or technologies in which it will be implemented. MDA divorces implementation details from business functions. Thus, it is not necessary to repeat the process of modeling an application or system's functionality and behavior each time a new technology (e.g., XML/SOAP) comes ALONG. Other architectures are generally tied to a particular technology. With MDA, functionality and behavior are modeled once and only once. Mapping from a PIM through a PSM to the supported MDA platforms will be implemented by tools, easing the task of supporting new or different technologies.

What Is The Model Driven Architecture (mda) And How Is It Different From Other Architectures?

Answer»

The MDA is a new way of writing specifications and developing applications, based on a platform-independent model (PIM). A complete MDA specification consists of a definitive platform-independent base UML® model, plus one or more platform-specific models (PSM) and interface DEFINITION sets, each describing how the base model is implemented on a different MIDDLEWARE platform.
A complete MDA application consists of a definitive PIM, plus one or more PSMs and complete implementations, one on each platform that the application DEVELOPER decides to support.
MDA development focuses FIRST on the functionality and behavior of a distributed application or system, undistorted by idiosyncrasies of the technology or technologies in which it will be implemented. MDA divorces implementation details from business functions.
Thus, it is not necessary to repeat the process of modeling an application or system's functionality and behavior each time a new technology (e.g., XML/SOAP) comes ALONG. Other architectures are generally tied to a particular technology.
With MDA, functionality and behavior are modeled once and only once. Mapping from a PIM through a PSM to the supported MDA platforms will be implemented by tools, easing the task of supporting new or different technologies.