China
Africa
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.
Unified Modeling Language
Published in Praveen Kumar, Jay Alameda, Peter Bajcsy, Mike Folk, Momcilo Markus, Hydroinformatics: Data Integrative Approaches in Computation, Analysis, and Modeling, 2005
Benjamin L. Ruddell, Praveen Kumar
In the specific context of geodatabase design, Visio has been the tool of choice for ESRI and other developers working to store geospatial data in database repositories. The ArcHydro data model is available as a Visio project file, and it may be easily modified and expanded. ESRI provides a “semantics checker” with its Visio geodatabase template. This checker will scan a static class structure diagram to ensure that the diagram is well formed and compatible with the ArcObjects. Then Visio can export the structure of a data model using the XML Metadata Interchange (XMI) format. XMI is a format for the communication of an XML schema (metadata) between UML-based modeling tools and object-based metadata repositories. This XMI file contains the schema of the data model, and may be applied to a data/metadata repository by other tools.
System of Systems Process Model
Published in Larry B. Rainey, Mo Jamshidi, Engineering Emergence, 2018
Several approaches to formulating requirements for systems of systems have been developed. Notably, data modeling and various modeling languages have been devised to structure artifacts for or to support the formulation and management of requirements, e.g., object management, the unified-modeling-language (UML), object-oriented methods, rational unified processes, object-process methodologies, eXtensible Markup Language (XML) metadata-interchange specification, and System Markup Language (SysML), to mention a few of the methods and tools. Additionally, formal methods and mathematical approaches and analytical techniques are used to verify requirements and address conflicts with requirements.
Architecture and Governance of Digital Business Ecosystems: A Systematic Literature Review
Published in Information Systems Management, 2023
Abide Coskun-Setirek, Maria Carmela Annosi, William Hurst, Wilfred Dolfsma, Bedir Tekinerdogan
The integration and transmission strategy of an MDA model is related to multiple standards, such as meta-object facility (MOF), EXPRESS language, UML, Extensible Markup Language (XML), XML metadata interchange (XMI), the Web Ontology Language (OWL), and ATLAS Transformation Language (ATL) (Jardim-Goncalves et al., 2013). The integration strategy of SOA architectures is traditionally based on ESB, (Adi & Heripracoyo, 2018; Appio et al., 2018; Figay et al., 2012; Kuk & Janssen, 2013; Lombardi et al., 2020; Reforgiato Recupero et al., 2016). For web services, application program interfaces like Representational State Transfer Application Programming Interface (REST API), Simple Object Access Protocol (SOAP) interface, and Hypertext Transfer Protocol (HTTP)/WEB API are implemented. As the SLR authors also reported, these are supported by the architectural styles, and communication protocols and standards, such as REST (Aulkemeier et al., 2019; Autiosalo et al., 2021; Reforgiato Recupero et al., 2016), SOAP (Adi & Heripracoyo, 2018), HTTP (Adi & Heripracoyo, 2018; Autiosalo et al., 2021), Message Queuing Telemetry Transport (MQTT) (Lombardi et al., 2020), Open Messaging Interface (O-MI)/Open Data Format (O-DF) (Javed et al., 2020), Open Platform Communications Unified Architecture (OPC UA) (Autiosalo et al., 2021; Marmolejo-Saucedo, 2020), Security Assertion Markup Language (SAML) and OpenID Connect (Bazarhanova et al., 2020), XML (Adi & Heripracoyo, 2018; Jardim-Goncalves et al., 2013; Kannisto et al., 2018), Extensible Messaging and Presence Protocol (XMPP) (Shamsuzzoha et al., 2017), and OWL (Jardim-Goncalves et al., 2013). The most common protocols are SOAP and HTTP for Client/Server, MQTT for Pub/Sub, and O-MI/O-DF for both Pub/Sub and Client/Server architectural patterns.