Model mapping using formalism extensions

The Object Management Group's model driven architecture defines a system development approach that formally separates system specification from platform implementations - in platform-independent models and platform-specific models, respectively. According to MDA, software development involves a...

Full description

Saved in:
Bibliographic Details
Published in:IEEE software 2005-03, Vol.22 (2), p.44-51
Main Authors: Caplat, G., Sourrouille, J.-L.
Format: Article
Language:English
Subjects:
Computer architecture
Computer programs
Concrete
Context modeling
design tools and techniques
Formalism
Inheritances
Language
Mapping
Model Driven Architecture
model mapping
Modeling languages
Platforms
Powder injection molding
Power system modeling
Programming
Semantics
Software design
Software development
Software engineering
Specifications
Translations
Unified modeling language
Citations: Items that cite this one
Online Access:Get full text
Tags: Add Tag
No Tags, Be the first to tag this record!
Description
Summary:The Object Management Group's model driven architecture defines a system development approach that formally separates system specification from platform implementations - in platform-independent models and platform-specific models, respectively. According to MDA, software development involves a sequence of model mappings that transform an initial PIM to a final PSM that is precise enough for direct translation into an executable program. A mapping is a set of rules and techniques for translating one model into another. When the starting and final models are expressed in the same formalism, the mapping is said to be intralanguage; otherwise, it is interlanguage. We focus here on interlanguage mapping, showing the central role of formalism extension mechanisms in managing the abstraction-level gap between languages as well as the platform-level details of specific implementations.
ISSN:0740-7459
1937-4194
DOI:10.1109/MS.2005.45