Explore chapters and articles related to this topic
Embedded Software Modeling and Design
Published in Louis Scheffer, Luciano Lavagno, Grant Martin, EDA for IC System Design, Verification, and Testing, 2018
After revision 2.0, the UML specification consists of four parts: UML 2.0 infrastructure, defining the foundational language constructs and the language semantics in a more formal way than they were in the past.UML 2.0 superstructure, which defines the user level constructs.OCL 2.0 object constraint language (OCL), which is used to describe expressions (constraints) on UML models.UML 2.0 diagram interchange, including the definition of the XML-based XMI format, for model interchange among tools.
Assessing construction interoperability using a MDA and SOA architecture from an e-business perspective
Published in Manuel Martínez, Raimar Scherer, eWork and eBusiness in Architecture, Engineering and Construction, 2020
A. Grilo, R. Jardim-Gonçalves, A. Steiger-Garção
The middle layer is the PIM (Platform Independent Model), and defines the conceptual model based on visual diagrams, use-case diagrams and metadata. For that it uses the standards UML (Unified Modelling Language), OCL (Object Constraint Language), XMI (XML Metadata Interchange), MOF (Meta Object Facility) and CWM (Common Warehouse Metamodel). Thus, the PIM defines an application protocol in its full scope of functionality, without platform dependencies and constraints. For a unambiguous and complete definition, the formal description of the PIM should concern using the correct business vocabulary, choosing the proper use-cases and interface specifications.
Models and Tools for Complex Embedded Software and Systems
Published in Luciano Lavagno, Igor L. Markov, Grant Martin, Louis K. Scheffer, Electronic Design Automation for IC System Design, Verification, and Testing, 2017
The object constraint language (OCL) [88] is a formal language used to describe constraint expressions on UML models. An OCL expression is typically used to specify invariants or other type of constraint conditions that must hold for the system. OCL expressions refer to the contextual instance, that is, the model element to which the expression applies, such as classifiers, for example, types, classes, interfaces, associations (acting as types), and datatypes. Also all attributes, association ends, methods, and operations without side effects that are defined on these types can be used.
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.
SysML-based compositional verification and safety analysis for safety-critical cyber-physical systems
Published in Connection Science, 2022
Jian Xie, Wenan Tan, Zhibin Yang, Shuming Li, Linquan Xing, Zhiqiu Huang
Model checking is a popular way to ensure the verification of SysML models. Ando et al. (2013) propose to formalise SysML state machines with CSP. Calvino and Apvrille (2021) propose a new model-checker that can be applied (almost) directly to the SysML model. Rahim et al. (2015) propose a model-to-model transformation of SysML activity diagrams into modular Petri nets to support the formal verification of SysML specifications. Nevertheless, doing so, often faces the so-called state explosion problem. An approach to deal with the state-explosion problem is the use of compositional verification which leverages the structure of the system. In these techniques, the verification of a composite system is reduced to the verification of its parts. Compositional verification (de Oliveira et al., 2019) has been widely used in model-driven development in recent years. The model constraint language used in the UML OCL. Burgueño and Gogolla (2017) verified and analysed by setting various functional or non-functional constraints to each model element, behaviour and interaction. The model basis of the HRC model as the SPEEDS framework in the EU SPEEDS project (Badouel et al., 2006), according to the HRC model, the theory and tool support including design, model construction, combined components and verification analysis are put forward. OCRA (Cimatti & Tonetta, 2016) the contract-based architecture model modelling combination verification and analysis, Yu et al. (2015) propose the contract-based architecture model design and verification method, Zhan et al. (2019) proposed to use the combination of AGREE and Simulink to verify complex systems. So, The Compositional verification based on contract can verify and analyse the architecture model of the complex system.