SysML and UML 2 support for activity modeling

Under the complex operational environment of the antimissile operation, the application of Systems Modeling Language (SysML) parametric model in weapon system effectiveness evaluation is explored. The function of parametric graph model, the construction process of the model and the optimization method of the model are researched. Using feedback mechanism to collect, collate and calculate the parameters of the model, and realize the leap from the index relationship description to the calculation of the index. Finally, the feasibility and effectiveness of the proposed method is verified by using the system of antimissile weapon system as an example.

The International Council on Systems Engineering (INCOSE) and the Object Management Group (OMG) are collaborating on an initiative to extend the Unified Modeling Language™ (UML™) to provide a general‐purpose systems modeling language. The language will support the specification, analysis, design, verification and validation of complex systems that include software‐intensive, information‐intensive, and physical systems. To achieve this goal, the OMG issued a UML for Systems Engineering Request for Proposal (UML for SE RFP) in March 2003. The modeling language that satisfies the requirements of this RFP will be a key enabler for transitioning the practice of systems engineering from a document‐centric to a model‐centric approach. This paper describes the technical approach and language features of the Systems Modeling Language (SysML), which is being proposed in response to the UML for SE RFP.

The International Council on Systems Engineering (INCOSE) Space System Working Group (SSWG) has created the CubeSat System Reference Model (CSRM), a representation of the logical architecture of a CubeSat system, intended to be used by system architects and engineers as a starting point as they develop the logical architecture of the Space and Ground components of the CubeSat mission of interest to them. The CSRM is based on Model-Based System Engineering (MBSE) principles, is System Modeling Language (SysML) compliant, is hosted in a graphical modeling tool, and is intended to introduce quality enhancements and economies associated with reusability. The CSRM has been vetted by System Engineering professionals and has been introduced to the CubeSat mission development team community with favorable results. It has been submitted to the Object Management Group (OMG) as a CubeSat specification, and is being evaluated for that role. The SSWG has created a notional outline describing how the CSRM can be applied to a specific mission development effort; and has also identified possible future efforts to expand the applicability, value, and use of the CSRM by the satellite development community.

This article compares Activity models of the Unified Modeling Language, version 2 (UML 2) [OMG (Object Management Group), UML 2.0 superstructure specification, August 2003, http://www.omg.org/cgi‐bin/doc?ptc/03‐08‐02 ], to a widely‐used systems engineering (SE) flow diagram, the Enhanced Functional Flow Block Diagram (EFFBD) [J. Long, Relationships between common graphical representations in system engineering, ViTech Corporation, 2002], and to the requirements for functional flow modeling in a systems engineering extension for UML (UML‐SE) [OMG Systems Engineering Domain Special Interest Group (SE‐DSIG), UML for systems engineering RFP, March 2003a, http://www.omg.org/cgi‐bin/doc?ad/03‐03‐41 ]. Issues are identified in applying UML 2 Activities to EFFBD and to satisfying UML‐SE functional flow requirements. Solutions are suggested to these issues that can be used to translate between the languages and to develop standards such as revisions to UML 2 or extensions in UML‐SE. * © 2003 Wiley Periodicals, Inc. Syst Eng 6, 249–265, 2003

The evolution of industry through a competitive environment resulted in a need for optimising the manufacturing processes. Many studies focalised on this topic, especially in the case of software engineering processes, which led to the definition of a standard for development processes (SPEM) by the OMG (Object Management Group) and a race to implement it through different languages and meta-models. Even if there is a huge similarity between software engineering and systems engineering, the standard and its different implementations are still insufficient to fulfil the requirements expressed through systems engineering standards such as EIA 632. In this paper a meta-model keeps the fruitful approach of the Software Process Engineering Meta-model (SPEM) combined with some useful concepts from the System Modelling Language (SysML). This model was validated through some predefined criteria, the specification of the EIA 632 standard and a sample process for systems engineering.

Integrating Analytical Models with Descriptive System Models: Implementation of the OMG SyML Standard for the Tool-specific Case of MapleSim and MagicDraw

<title>ABSTRACT</title> <p>As systems become more complicated, managing them from conceptual design through disposal has become significantly more difficult. Traditional process- and document-based methods often struggle to cope with the realities of designing and fielding modern engineered systems; relevant information can become segmented and out-of-sync, leading to costly errors.</p> <p>The International Council on Systems Engineering (INCOSE) initiated a Model-Based Systems Engineering (MBSE) initiative nearly fifteen years ago; one of the fruits of this effort is the System Modeling Language (SysML). Modern SysML tools are quite mature and have considerable capabilities to capture, characterize, and connect information.</p> <p>A number of efforts are currently underway to maximize the value of SysML models, including the development of visualization, co-simulation, and robust model integration. An entire ecosystem of adjacent tools is evolving that will significantly impact the practice of systems engineering within the next five years. This paper presents an integrated look at publically-available information about existing worldwide efforts and their implications for systems engineering practitioners.</p>

This paper examines the System Engineering processes/applications transforming from being document‐centric to being model‐centric by examining the benefits and uses of the Systems Modeling Language (SysML). This paper will look at the concept behind SysML and provide a background on existing research to address the Unified Modeling Language (UML) Systems Engineering request for proposal to generate SysML. This paper will identify benefits of using SysML in the Systems Engineering process and makes a recommendation for its use in large scale integration projects and complex hardware and software designs.

Nowadays, in software, electronics and automotive industries, it takes 1.5–2 years for a new product to appear, although it takes 3 or even more years to develop new space instruments. The update of higher education system standards is even more conservative. It takes 10 or more years. Because of this, graduates come into the industry with outdated knowledge. Thus, the problem is to synchronize the processes of updating technologies that ensure the creation of innovative products with educational programs. It can be solved by changing the paradigm of products creation based on the synthesis of deep and interdisciplinary educational, scientific, innovative and production activities with the model-based systems engineering software and methodological tools.The existing model-based systems engineering (MBSE) Software (SW) tools based on the Systems Modelling Language (SysML) are complex and expensive. This chapter raises the question, “Is it possible to make use of MBSE SW and methodological tools available to a wide audience of users?” To answer this question, the following MBSE approaches and tools were researched: Quality Function Deployment (QFD), House of Quality (HoQ), and SysML. Consequently, five methodological tools were developed for application during space instruments design and development life cycle stages. Tools are based on SysML, QFD, HoQ improvements and synthesis, and expressed in theoretical and practical algorithms.The theoretical algorithm determines “What” (input and output data) and “How” (by using which systems engineering (including MBSE) tools are methodically analysed at the certain space instruments life cycle stage. The practical algorithm automates the development of SysML diagrams by using data structured in HoQ models and widely available SW. It reduces the time to develop and update SysML requirements diagrams from several days to some minutes and enables implementation of SysML SW by many users. Altogether, the obtained results constitute the software and methodological toolkit (SMT) called “improved Quality Function Deployment for improved House of Quality”.To disseminate the obtained results, educational materials were created and validated during lectures on systems engineering. Lectures were supplemented with seminars and practicum. Practicum was focused on the design and development (D&D) of nanosatellites in the MBSE paradigm as the single project. The results showed that the developed SMT makes it possible to implement the life cycle of the cyber-physical system in the MBSE paradigm in a cost-effective way and a short time—in 6 months, students developed, conducted synthesis and flight tests of CubeSat-format satellite prototype and prepared the project documentation. In addition, students were motivated to study science, technology, engineering and math disciplines, MBSE tools, and become transdisciplinary specialists.In addition, developed SysML requirements models were applied to examine the “Preliminary Design” product life cycle (PLC) stage of different space projects. Such application allowed quick assessment of project results, identifying non-compliance with requirements, conducting beforehand all necessary corrections and generating correct new product documentation. Taking into account the mentioned advantages of the obtained MBSE SMT, it can be concluded that its usage improves the quality and accuracy of current projects and speeds up the planning process of future analogue projects by up to 60%. Consequently, projects (their life cycle stages) can be realized faster by 5–10%.These results allow to recommend for all interested in the innovative D&D of systems to initiate: formation of educational programs based on the project approach and MBSE paradigm; preparation of MBSE materials for online and offline teaching of students and teachers; development of domestic widely available software for the development of integrated SysML models with HoQ models that assures synchronization with CAE/CAD/CAM systems; support these recommendations for the implementation of the above-mentioned research results at educational organizations of different levels. The future research is focused on the application of the developed MBSE methodological toolkit during design and development with numerical modelling and operation of several CubeSat satellites.KeywordsSystems engineeringMBSEParadigmMethodological toolkitSysMLQFDHoQ

The use of systems engineering has proven effective in managing complexity and improving system design. Model based system engineering utilizing the Systems Modeling Language (SysML) especially helps in multidisciplinary environments where engineering data needs to be transformed and integrated between environments. Manufacturing is another discipline same as systems engineering is on active digitalization transformation. In the paper, we propose method and solution to apply Model based system engineering (MBSE) for improvement of process planning of assembly lines leveraging model based approach. SysML modeling and execution enable automation of analysis activities as trade‐off, where the behavior of various assembly scenarios of an assembly line can be captured using SysML behavioral diagrams and compared based on various evaluation criteria. However, relying solely on descriptive SysML system models without integrating the virtual representation of the assembly line is insufficient to verify all aspects of system behavior, such as ergonomics and collision avoidance. The main objective of this work is to present a concept for transforming SysML assembly scenarios into the process and resources models of the computer‐aided design and manufacturing (CAD/CAM) environment. This yields a holistic view that serves as a foundation for further production‐related simulations and analyses, enhancing efficiency, ergonomic design, factory layout, and material flow, ensuring effective assembly workstation design optimized at systems engineering level.

Cybersecurity is a comparatively new discipline, related to computer science, electrical engineering, and similar subjects. As a newer discipline it lacks some of the tools found in more established subject areas. As one example, many engineering disciplines have modeling languages specific for that engineering discipline. As two examples, software engineering utilizes Unified Modeling Language (UML) and systems engineering uses System Modeling Language (SysML). Cybersecurity engineering lacks such a generalized modeling language. Cybersecurity as a profession would be enhanced with a security specific modeling language. This paper describes such a modeling language. The model is described in sufficient detail to be actionable and applicable. However, suggestions for future work are also provided.

In this chapter, we provide the essential theory and practical details of employing the principles of Object Orientation (OO) in system architecture modeling. We do not attempt to provide an exhaustive OO tutorial, since there exists a very large literature on this subject (see the references to this chapter). Our goal, instead, is to give the reader the level of understanding needed to master the MBSAP methodology and apply it to practical system architecting challenges. First, we present the rationale for OO and define the essential concepts and terminology, stressing the benefits it delivers in dealing with complex entities. Although we use the Systems Modeling Language (SysML) as the basis for this book, we begin by discussing and illustrating the primary diagrams of the Unified Modeling Language (UML), which is the root language standard for OO. This is then followed by a description of the changes to UML introduced by the SysML, which is defined as a Profile of UML. The reality is that a large part of the SysML is taken directly from the UML language specification. We believe understanding of this material is enhanced by first considering the parent UML and then explicitly showing how UML modifies and extends the language. We include generic UML and SysML diagrams that illustrate important principles and syntax and that can serve as format samples in developing real architecture models. Appendices A and B are concise references to UML and SysML, respectively, intended to give readers a quick and easy way to look up the details. Chapter objective: the reader will be able to create and read UML and SysML diagrams and to describe the role of each.

Over the past decade or so, improvements and changes in descriptive models of systems have been occurring. This has mainly come about in the shift from a document-centered approach to an approach using a dedicated language known as the Systems Modeling Language (SysML). SysML has allowed Systems Engineers (SEs) to consolidate information about a system and even automate some tasks leaving the SEs to concentrate on the actual engineering and decision-making. Many of our quality assurance (QA) tasks either overlap or interface with systems engineering tasks, thus, it is important for quality engineers to understand and contribute to these system engineering models. We will explore some of the ways in which QA processes and products may be model within the framework of SysML. First let us look at how quality can be assured by using requirement elements in a systems model.

An Integrated Intelligent Modeling and Simulation Language for Model-based Systems Engineering

The development process of complex systems needs to take in account differents domains and aspects. SysML (Systems Modeling Language) is a new modeling language that allows a system description with various integrated diagrams (as structure, behavior and requirements diagrams), but SysML lacks formality for the requirement verification. The aim of this paper is to propose an approach to verify complex systems using SysML as a language which describes the system structure and requirements. Petri nets and temporal logic LTL are used respectively to formalize the system behavior and requirements. The benefit of such formalization is to allow an automatic formal verification. In order to demonstrate this methodology, it will be used a factory automation system, modeled by SysML and Petri nets, and verified by the TINA toolbox.