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
While UML1 and UML2 lack many properties required for modeling embedded systems, there are several OMG developments that try to address such issues, complementing the UML2 norm. One way to deal with such extensions is to define a UML2 profile using the available extension mechanisms of the UML. The EAST-ADL effort is one example where the UML2 language is being tailored to a particular domain and more formalized, by the use of UML2 extension mechanisms. A current OMG request for proposal, MARTE, is addressing this, in order to define a new UML profile for real-time embedded systems, adding properties for specifying timing requirements and component behavior, for example [101]. Another OMG effort is that of the recent SysML standard—a visual modeling language for systems engineering applications [111]. SysML supports the specification, analysis, design, and V&V of a broad range of systems and systems-of-systems. It is implemented as a UML2 profile, adding some diagrams and constructs to UML2 (mainly regarding requirements and parametric associations). SysML provides an interesting framework that still needs to be proven for the area of embedded systems.
Modeling with UML and Its Real-Time Profiles
Published in Katalin Popovici, Pieter J. Mosterman, Real-Time Simulation Technologies, 2017
Emilia Farcas, Ingolf H. Krüger, Massimiliano Menarini
OMG also provides the standard for the Systems Modeling Language™ (OMG SysMLTM) [42]. SysML reuses a subset of UML 2 (called UML4SysML) and provides additional extensions to address the concerns for systems engineering applications (called the SysML Profile). Therefore, SysML uses both UML extension mechanisms: the first-class extension via MOF is used to define the UML4SysML subset and then the profile extension mechanism is used not on UML but on UML4SysML. SysML does not use all of the UML diagram types and, thus, it is smaller and easier to learn than UML. In particular, SysML strictly reuses the UML use case, sequence, state machine, and package diagrams. SysML also modifies some of the UML diagrams. The SysML block definition diagram, internal block definition diagram, and activity diagrams extend the UML class diagram, composite structure diagram, and activity diagram, respectively. The SysML “block” is a significant extension in the direction of modeling complex systems. Blocks can be used to decompose the system into individual parts, with dedicated ports for accessing their internals. A block can represent almost any other type of structural entity. Furthermore, SysML allows the description of more general interactions than in software, for example, physical flows such as liquids, energy, or electricity. SysML activity diagrams add support for modeling continuous flows of material, energy, or information. By specifying a continuous rate, the increment of time between tokens approaches zero to simulate continuous flow. Nevertheless, SysML does not extend the time model of UML.
Principle and method of integrating reliability design in the MBSE process
Published in Vladimír. Socha, Lenka Hanáková, Andrej Lališ, New Trends in Civil Aviation, 2018
SysML is a kind of graphical modeling language common for system engineering application. The common graphic expression is the direct reuse of some elements of UML2.0 and the use of the stereotype mechanism to extend some elements of UML: as shown in Figure 5, SysML includes nine types of diagrams, among which, Use Case Diagram, Sequence Diagram, State Machine Diagram, and Package Diagram are consistent with UML; Requirement Diagram and Parametric Diagram are completely new diagrams defined by SysML; and Block Definition Diagram, Internal Block Diagram, and Activity Diagram are obtained by extension of UML’s similar diagram, combined structure diagrams, and activity diagram, respectively.
A system modeling process based on SysML to support data consistency across system requirement, function, and solution model layers
Published in Journal of Engineering Design, 2023
Yizhe Zhang, Georg Jacobs, Wei Yu, Gregor Hoepfner, Joerg Berroth
The MBSE approach is emerging as an important practice in the development of complex technical systems to enhance productivity and improve communication among the system development teams (Beery 2019; Stirgwolt, Mazzuchi, and Sarkani 2022). Ideally, MBSE should formalise the application of modeling to support the system requirements definition, design, analysis, and verification & validation activities throughout the system development process and among all stakeholders (Walden et al. 2015). SysML is a general-purpose graphical modeling language that defines and represents system elements such as system requirements, functions, physical structure, and behaviours throughout the development process. The system model is the artifact of modeling and serves as a central platform that enables these abstract system elements to be linked with each other (Friedenthal, Moore, and Steiner 2015).
A multi-level modelling and fidelity evaluation method of digital twins for creating smart production equipment in Industry 4.0
Published in International Journal of Production Research, 2023
Chao Zhang, Jingjing Li, Guanghui Zhou, Qian Huang, Min Zhang, Yifan Zhi, Zhibo Wei
Behaviour modelling defines the detailed requirements, structures, behaviour and parametric of the physical production equipment via semantic models. Systems Modelling Language (SysML) is a general-purpose graphical modelling language for specifying, analysing, designing, and verifying a complex equipment (Rahman et al. 2013). SysML provides graphical representations with a semantic foundation for modelling equipment requirements, behaviour, structure and parametrics, which could be used to integrate with other engineering analysis models, e.g. geometric models and mechanism models. Consequently, SysML could be used for behaviour modelling of a physical equipment, where elements of the physical equipment are represented by block definition diagrams (BDD) and internal block diagrams (IBD). BDD describes the hierarchy and classification relationship of the equipment. IBD describes the internal behaviour of the equipment in terms of its parts, ports, and connectors. Figure 4(b) illustrates an example of behaviour modelling of a machine tool, where the left BDD model indicates the requirements and hierarchy relationship of the machine tool and the right IBD model defines the internal behaviour of the drivetrain of the machine tool.
Object-oriented systems engineering for networked infrastructure projects
Published in Australian Journal of Multi-Disciplinary Engineering, 2020
Object-oriented systems engineering emerged in the late 1990s through a desire to extend the advances made in object-oriented software development to general system design. Although object-oriented concepts were sometimes applied to socio-technical systems (Bharathan, Poe, and Bahill 1995), the main motivation was to develop a common approach on software-intensive projects between software engineers and systems engineers. For this reason, object-oriented systems engineering is often associated with the OMG1 Systems Modeling Language (SysML) which was first released in 2007. SysML is useful when developing complex projects because it helps to specify system components which can then be designed using other domain-specific languages such as UML2 for software components and VHDL3 for hardware design (Friedenthal, Moore, and Steiner 2015). Due to its association with the software community, SysML was designed from inception as an object-oriented modelling language.