| Model Driven Architecture |
Article Index for Model |
Website Links For Architecture |
Information AboutModel Driven Architecture |
| CATEGORIES ABOUT MODEL-DRIVEN ARCHITECTURE | |
| software engineering | |
| systems engineering | |
| domain-specific programming languages | |
| unified modeling language | |
| design | |
|
Using the MDA methodology, system functionality is defined as a Platform-independent Model (PIM), using an appropriate Domain Specific Language and then translated to one or more Platform-specific Model s (PSMs) for the actual implementation, using different Domain Specific Language or even a General Purpose Language like Java, C#, Python, etc. To accomplish this goal, the MDA defines an architecture that provides a set of guidelines for structuring specifications expressed as models. The translations between the PIM and PSMs are normally performed using automated tools. The MDA model architecture relates multiple standards, including Unified Modeling Language (UML), the Meta-Object Facility (MOF), the XML Metadata Interchange (XMI), and the Common Warehouse Metamodel (CWM). Note that the term “architecture” in Meta-modeling does not refer to the architecture of the system being modeled, but rather to the architecture of the various standards and model forms that serve as the technology basis for MDA. or Model Driven Engineering . SEPARATING DESIGN FROM ARCHITECTURE AND REALIZATION TECHNOLOGIES One of the main aims of the MDA is to separate design from architecture and realization technologies facilitating that design and architecture can alter independently. The design addresses the functional ( Use Case ) requirements while architecture provides the infrastructure through which non-functional requirements like scaleability, reliability and performance are realized. MDA envisages that the platform independent model (PIM), which represents a conceptual design realizing the functional requirements, will survive changes in realization technologies and Software Architecture s. MDA TOOLS A range of MDA-supporting tools are being developed by vendors and open source projects. These tools typically enable one to provide a rudimentary architecture specification. Simple examples of architecture specifications include
MODEL TRANSFORMATIONS Of particular importance to Model Driven Architecture is the notion of model transformation. A specific standard for model transformation has been defined called QVT . One example of a QVT language for model transformation is ATL :
MDA BEYOND SOFTWARE DESIGN The principles of MDA can be applied to other areas like business process modeling where the architecture and technology neutral PIM is mapped onto either system or manual processes. DESIGN METHODOLOGIES FOR MDA URDAD , the ''Use-case, Responsibility Driven Analysis and Design'', provides a design methodology which is meant to be used within an MDA framework. It aims to generate MDA's PIM in such a way that the methodology itself enforces accepted criteria for ''good design''. SEE ALSO
REFERENCES
EXTERNAL LINKS
|
|
|