China 
Africa 
Explore chapters and articles related to this topic
Engineering of Process-Centric Application Systems
Published in Vivek Kale, Enterprise Process Management Systems, 2018
MDA describes three main layers of architectural abstraction or viewpoints (Figure 13.2): A computation-independent model (CIM) describes a system environment and its requirements using terminology that is familiar to practitioners in the system domain.A platform-independent model (PIM) describes a system’s structure and functions formally, yet without specifying platform-specific implementation details.A platform-specific model (PSM) includes details that are important to the implementation of a system on a given platform. By platform, MDA means a cohesive set of subsystems and technologies on which a system can execute (such as Sun’s Java EE or Microsoft’s .NET platforms).
Interoperability
Published in Vivek Kale, Digital Transformation of Enterprise Architecture, 2019
Platform specific model (PSM): includes details that are important to the implementation of a system on a given platform. By platform, MDA means a cohesive set of subsystems and technologies on which a system can execute (such as Sun’s Java EE or Microsoft’s.NET platforms).
Cyber-Physical Systems: a multi-criteria assessment for Internet-of-Things (IoT) systems
Published in Enterprise Information Systems, 2021
Edgar M. Silva, Ricardo Jardim-Goncalves
Model-driven Architecture (MDA) (Miller et al. 2003) was initially designed for software development, but it has been widely applied in system/enterprise interoperability and in business process management areas. To cover the entire system development process, the architecture presents three abstraction layers, the platform-specific model (PSM), platform-independent model (PIM) and computation independent model (CIM) (Miller et al. 2003; Singh and Sood 2009). Supported by two types of transformations, horizontal and vertical, in which a variety of possible transformation categories can be established, such as, marking, meta-model transformation, model transformation or model merging (Singh and Sood 2009). These transformations assist in the development process (more automatic) of new system functionalities and can also be used to perform system/enterprise interoperability by matching process phases or data descriptions from one company/system to another. Between the two top levels, CIM and PIM, MDA does not specify any transformations, presenting instead the use of Meta-Object Framework, an OMG standard that gives the basis for the definition of meta-models.
Service-Oriented Computing for intelligent train maintenance
Published in Enterprise Information Systems, 2019
Boukaye Boubacar Traore, Bernard Kamsu Foguem, Fana Tangara, Xavier Desforges
The methodology adopted focuses on the distinction between the specification of correspondences and the definition of transformations; this is considered particularly important for the implementation of the MDA approach to a SOA platform. The specification of correspondences is to specify the mappings between the elements of two meta-models and the definition of transformations to describe in detail and perform the steps of transforming a model into another one in accordance with the specification of correspondences. MDA automates the production of a ‘Platform Specific Model’ (PSM) model (that is closer to the technology) from a ‘Platform Independent Model’ (PIM), which is nearer to business concepts and requirements The basic principle of the MDA is the development of different models, starting from an Independent Computer Model (CIM), transforming it into a Platform Independent Model (PIM) and finally the transformation of the latter into a specific Platform-Specific Model (PSM) for the concrete implementation of the system (Figure 3). The second level of translation from PIM to PSM is automate process by applying mapping technique (for instance: ATL – Atlas Transformation Language). However, this transformation can be enriched by refinement which consists in adding other technical information relating to the target execution platform and in specifying their content (OMG MDA, 2014). The PSM are thus refined and the information they contain is specified by successive enrichments. A PSM provides useful information for generating application code and is dependent on the execution platform. It is possible to create as many PSM as there are target platforms.