China
Africa
Explore chapters and articles related to this topic
Introduction to IT Transformation of Safety and Risk Management Systems
Published in Qamar Mahboob, Enrico Zio, Handbook of RAMS in Railway Systems, 2018
Coen van Gulijk, Miguel Figueres-Esteban, Peter Hughes, Andrei Loukianov
Metamodels are the bridge between the Zachman enterprise architecture and operational railway systems. Metamodel platforms provide an environment for the framework in which goals, models, rules, and constraints are formulated. In IT, they are used in a narrower sense: the metamodel entails a method to design ontologies and UML relationship charts, selection of programming languages, and development of semantic networks. In some respects, this is the bottom–up approach where designers try to capture all relevant knowledge to serve the enterprise architecture.
Enterprise Modeling
Published in Vivek Kale, Enterprise Process Management Systems, 2018
Depending on need, there have been approaches to support the development of new modeling languages (the so-called metamodeling) rather than the use of existing, defined languages. In particular, this is exploited in domain-specific modeling and domain-specific languages. The term “meta” indicates that something is after something; that is, a metamodel is a model after (of) a model. In principle, it is possible to apply an infinite number of meta-levels.
Human–Computer Interaction and Software Engineering for User Interface Plasticity
Published in Julie A. Jacko, The Human–Computer Interaction Handbook, 2012
A meta-model is a model of a set of models that comply with it. It sets the rules for producing models. It does not represent models. Models and meta-models form a tree: a model complies with a single meta-model, whereas a meta-model may have multiple compliant models.
A model-based systems engineering approach for developing modular system architectures
Published in Journal of Engineering Design, 2022
Benjamin W. Stirgwolt, Thomas A. Mazzuchi, Shahram Sarkani
Part of the motivation for these standardisation and harmonisation efforts stems from the recognition that communication amongst a diverse set of stakeholders and system developers tends to be imprecise and ambiguous. The use of MBSE – and its associated formal modelling languages, like UML/SysML – is beginning to address the incompatible and inconsistent semantics used in systems engineering and other domains (Madni and Sievers 2018). This is accomplished using ontologies and metamodels, which are foundational to MBSE. An ontology is ‘an explicit representation of a shared understanding of the important concepts in some domain of interest’ (Kalfoglou 2001). The objective of the ontology is to turn tacit knowledge into explicit knowledge. A metamodel provides the syntax and constraints for the modelling language and consists of ‘object types, attributes of object types, and the rules that enable combining object types and relationships’ (Madni and Sievers 2018). SysML was developed in context of the Object Management Group’s (OMG) four-layer meta-modelling architecture called the Meta-Object Facility (MOF). This four-layer approach enables the addition of domain-specific modelling concepts in the different layers. Domain-specific concepts may be integrated in the user model (M1) level or at the meta-model (M2) level through language extensions called profiling (McGinnis et al. 2012). To address domain-specific concerns, including the concern of creating modular architectures, appropriate language extensions are needed.
Towards the integration of organisational culture models into model-based systems engineering approaches for enterprise systems transformation
Published in Australian Journal of Multi-Disciplinary Engineering, 2020
G.A.L. Kennedy, F. Shirvani, W. Scott, A.P. Campbell
The OCMM was developed in conjunction with the rail operator participants from ACRI. Feedback from these stakeholders during demonstrations has been positive with stakeholders appreciating the benefits of the holistic view, traceability and consistency of information. At this stage, the research has explored the feasibility for a subset of models of organisational culture to be integrated with enterprise system models for transformation. The models and tool developed from this research require further validation through population with the organisation’s real data and improvements to design with SMEs to improve the concepts to be fit for purpose. The paper has described how organisational culture models and use cases for managing culture for enterprise system transformation can be considered. Future development of more complete metamodels and the full set of use cases (and user requirements) is needed to create a truly integrated tool that will enable the models and analyses created to reflect the complexity of the enterprise system.
Service-Oriented Computing for intelligent train maintenance
Published in Enterprise Information Systems, 2019
Boukaye Boubacar Traore, Bernard Kamsu Foguem, Fana Tangara, Xavier Desforges
A transformation specification (which may also be a model) specifies how a PIM is transformed into a PSM based on parameters provided by developers (OMG MDA, 2014). The MDA Metamodel Description is presented in Figure 3 (adapted from (OMG MDA, 2001)) with PIM, PSM and mapping techniques that are based on metamodel articulated preferably with OMG core technologies like Meta-Object Facility (MOF), Common Warehouse Metamodel (CWM) or Unified Modeling Language (UML). A metamodel defines the structure and not the semantics of models conforming to this metamodel. A metamodel is a class diagram that defines the model’s features, as well as the properties of their connections and their consistency rules. To be valid, each model must conform to its metamodel. This relation of conformity is essential in the MDA approach, it is thus possible to build tools able to handle the models (Figure 4).