Explore chapters and articles related to this topic
Model-Based Development of Automotive Embedded Systems
Published in Nicolas Navet, Françoise Simonot-Lion, Automotive Embedded Systems Handbook, 2017
Martin Törngren, DeJiu Chen, Diana Malvius, Jakob Axelsson
Examples of languages for defining information content include ISO 10303-11 EXPRESS, a part of the STEP standard [110] and document type definitions (DTDs) and eXtensible markup language (XML)* schemas, both standardized by W3C. Examples of exchange formats include various ISO standards as part of STEP and the XML. The XML metadata interchange (XMI) [118], is an OMG standard based on XML. It is used to exchange any metadata whose metamodel is compatible with MOF. The most common use of XMI is as an interchange format for UML models, although it can also be used for serialization of models of other languages. For UML diagrams, the diagram interchange standard is intended to support the exchange of graphical information. Unfortunately, contemporary tools rarely implement this standard, meaning that the support for exchange of UML models between tools—while retaining the graphical information—is currently inadequate.
A systematic mapping study on enterprise architecture mining
Published in Enterprise Information Systems, 2019
Ricardo Perez-Castillo, Francisco Ruiz-Gonzalez, Marcela Genero, Mario Piattini
Owing to the amount of EA concerns at different layers (as demonstrated by the ArchiMate overview), EA concerns are sometimes represented using the modelling languages from other knowledge areas. This is because some researchers and practitioners from other areas have converged into the EA field. For example, some researchers have used the ‘UML (Unified Modelling Language)’ and ‘OCL (Object Constraint Language)’ to model application concerns. They have also used MOF (Meta-Object Facility) in some MDE modelling techniques and OWL (Ontology Web Language) in application and technology layer concerns. Others have employed languages such as Sparql together with OWL in order to query OWL elements, while SoaML (SOA Modelling Language) has been used to model services in business and application layers. The process concern in the business layer has been modelled with some specific languages such as BPMN (Business Process Model Notation), SPEM (Software & Systems Process Engineering Metamodel) or even PetriNet. Other general-purpose languages have also been used to model different concerns, such as SysML (Systems Modelling Language) or XML plain files. Even more, algebraic structures may provide interesting results for modelling enterprise ontologies (Suga et al. 2018).
Using Distributable User Interfaces in CSCL In-Situ Classrooms
Published in International Journal of Human–Computer Interaction, 2018
Ricardo Tesoriero, Abdulrahman H Altalhi
The technology employed to define the UI distribution metamodel follows OMG standards, which ensures the interoperability with third party tools. Reflexive (tree-based) and graphical model editors were implemented as Eclipse plugins based on the Eclipse Modeling Framework (EMF) (Eclipse Foundation, 2017) (https://www.eclipse.org/modeling/emf/) and Graphical Modeling Project (GMP) (http://www.eclipse.org/modeling/gmp/) (Eclipse Foundation, 2017d) facilities. The metamodel is defined in OclInEcore (Eclipse Foundation, 2017b), which is dialect of the Meta-Object Facility (MOF) (Object Management Group, 2014) that supports the definition of model constraints defined in the Object Constraint Language (OCL) (Object Management Group, 2014). These constraints are defined to perform model validations and derive UI states and capabilities.