Experience from introducing Unified Modeling Language/Systems Modeling Language at Saab Aerosystems

During the design of integrated products and services, such as in a product-service system (PSS), an analysis of specific customer needs and the requirements to fulfil them is an important activity needed to determine value propositions based on the function, use, and result of products. Requirements modeling using the OMG Systems Modeling Language (OMG SysML TM ) offers a model-based systems engineering approach to documenting the functionality, performance, and interfacing of systems. However, to use modeling languages, there is a need to understand how the language meets the needs of the modeled system or domain. Following an initial review and evaluation of attributes of PSSs and existing approaches to modeling a PSS, this article analyzes the SysML requirements diagrams-as a technique for analyzing PSS requirements. SysML was compared against existing approaches to PSS modeling using the identified PSS attributes. Case scenarios of PSSs in the automotive industry were also applied to evaluate the use of SysML requirement diagrams. The article concludes by discussing implications of SysML for PSS researchers and managers.

Section: Product-service Systems Research Implicationssupporting

confidence: 74%

Integrated product‐service analysis using SysML requirement diagrams

Durugbo

2012

“…However, the trend is clear and indicates that there are several initiatives striving to both clarify the definition and to improve its applications . Current trends also indicate that organizations are establishing long‐term goals at strategic levels to enhance their systems engineering capabilities using a model‐based paradigm . Furthermore, MBSE is predicted to become the norm for systems engineering execution, with focus on integrated modeling environments…”

Section: State Of the Practice Definition Of Mbsementioning

confidence: 99%

State‐of‐practice survey of model‐based systems engineering

Huldt

Stenius

2018

103

This paper aims to examine and document the current state of practice of model-based systems engineering (MBSE), and how organizations look toward the future. The paper is based on a survey of how MBSE has been applied and factors that influenced the perceived benefits and results.The survey was designed to evaluate the maturity and status of the implementation of MBSE (also called model-centric systems engineering), within industry, academia, and governments. The approach to the survey development is described along with the survey results. The study indicates that one of the main hurdles to introducing a model-based approach is the lack of clear and adopted organizational structures and an understanding of required conditions and needs at a management level. The survey also indicates that 50-75% of the respondents noted some improvement or a significant improvement across almost all systems engineering tasks. K E Y W O R D S analytical hierarchy process (AHP), model-based systems engineering (MBSE), systems engineering, systems engineering management, systems modeling language (SysML), Unified Modeling Language (UML) 134

“…Bayer et al [] describe (a) increasingly complex requirements, (b) competing stakeholder concerns, and (c) complexity due to system interaction as challenges facing current Systems Engineering practice at JPL. A case study from Saab Aerosystems reports similar experiences, as market desires lead to a demand for faster design realization and identification of subsystem reuse for novel integrated solutions [Andersson et al, ]. Influences from higher consumer expectations, economic pressure, and challenges due to increased complexity for integration require a novel approach to Systems Engineering.…”

Section: Literature Reviewmentioning

confidence: 99%

“…A central repository of design information is aggregated in a collaborative environment which promotes configuration control, communication within the design team (and customer interface), and a means to visualize interdomain dependencies [Raif et al, ]. Recent case studies claim MBSE increases efficiency of System‐Software transition using modeling artifacts [Andersson et al, ]. Requirements definition, a critical responsibility of Systems Engineering, can also be modeled to identify suballocation, derivation, realization, and maintain traceability.…”

Section: Literature Reviewmentioning

confidence: 99%

Leveraging Variability Modeling Techniques for Architecture Trade Studies and Analysis

Ryan

Sarkani

Mazzuchi

2013

Increasing complexity in modern systems, as well as cost and schedule constraints, require a new paradigm of Systems Engineering to fulfill stakeholder needs. Challenges facing efficient trade studies include poor tool interoperability, lack of simulation coordination (design parameters), and requirements flow down. A recent trend toward Model Based Systems Engineering (MBSE) includes flexible architecture definition, program documentation, requirements traceability, and Systems Engineering reuse. As a rapidly evolving practice, MBSE still lacks governing standards and commonly accepted frameworks. This paper proposes a framework for efficient architecture definition using MBSE in conjunction with domain specific simulation to evaluate alternatives. Variant modeling techniques are introduced as an extension to capturing parameterized architecture options. Initial exploration applies such variant modeling techniques to design for adaptability trade study criteria, as a means to evaluate candidate architecture configurations against multiple requirement sets. A general framework is provided, followed with a specific example including a method for designing a trade study, defining candidate architectures, planning simulations to fulfill requirements, and designing a weighted decision analysis to optimize system objectives.