why use the model driven architecture to design and build distributed applications? omg's model driven architecture® (mda®)[1] unifies and simplifies modeling, design, implementation, and integration of applications -- including large and complex ones -- by defining software fundamentally at the model level, expressed in omg's standard unified modeling language® (uml®)[2]. an mda-based development goes through three steps -- two producing models, one producing code -- and typically iterates through these several times.an mda application's base model specifies every detail of its business functionality and behavior in a technology-neutral way; in mda terminology this is the application's platform-independent model (pim). use of well-known patterns, imported into the model from a library and parameterized to suit the application, speeds development and reduces error while still producing a complete and detailed pim. technology independence allows domain experts to concentrate on getting the business process correct, and preserves the model's usefulness beyond the technology churn cycle.working from the pim, mda tools follow an omg-standard mapping to generate an intermediate model tailored to the target middleware implementation platform. (omg is standardizing mappings to all popular middleware platforms; several have already been adopted.) termed a platform-specific model (psm), this intermediate product adds non-business, computing-related details (typically affecting performance and resource usage), possibly following "markup" inserted on the pim by your architects, and the version produced by the mda tool will probably require some hand-tuning before it can be used for the next step. (the amount of hand-tuning required will vary depending on the sophistication of the tool, the complexity of the application, and the maturity of the mda in your application domain.in the final development step, working from the psm, mda tools generate interface definitions, application code, makefiles, and configuration files for the psm's middleware platform. because the industry has been working on this transformation for years already, and the model is tailored specifically for this transformation, the automated conversion in this step is typically 100% or nearly so. performing a "build" on these artifacts yields a deployable application.because the pim is middleware-neutral and conversion to the psm and then to the implementation is mostly automatic, it is practical to produce equivalent implementations of mda-based applications on multiple target platforms. in addition, tools can generate cross-platform invocations, allowing easy interworking among suites of mda-based applications wherever they reside. another benefit of the mda: because industry standards defined as an mda pim are platform-independent, they can be implemented on multiple targets and then used by every enterprise even in industries that haven't converged on a single middleware platform.based on uml, automation, and sound architectural principles, the mda supports applications over their full lifecycle starting with design and moving on to coding, testing, and deployment, through maintenance, and eventually to evolution to a new platform when an application's existing platform becomes obsolete. the mda became the base architecture for omg standards in september 2001.