Adopting MBSE in Construction Equipment Industry: An Experience Report

Suryadevara, Jagadish; Tiwari, Saurabh

doi:10.1109/apsec.2018.00066

Cited by 36 publications

(39 citation statements)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…16,26,33 Consistency of MBSE practices Consistency/standardization is necessary to assist with communication between units and integration of models/artifacts. 1,18,33,40,41,46 However, some find that there is a "resistance to enforced consistency." 43,48 Different organizational units choosing their own methods, tools, languages, and so forth can lead to "integration and model interchange issues" down the road.…”

Section: Automationmentioning

confidence: 99%

“…There is not a simple process to translate old artifacts into a model-based environment. 17,27,48 Additionally, the document-based way of working often still needs to be maintained, 26,40,52 and therefore models need to be able to produce the expected document-based artifacts. 26,40 Maturity of MBSE MBSE tools, methods, terminology, and standards are often seen as immature.…”

Section: Lessons Learned Categories Literature Examplesmentioning

confidence: 99%

See 1 more Smart Citation

MBSE adoption experiences in organizations: Lessons learned

Henderson,

McDermott,

Salado

2023

Systems Engineering

View full text Add to dashboard Cite

Lessons learned through MBSE adoption efforts is one of the key ways of communicating best practices and recommendations for MBSE. This study compiles lessons learned from published case studies and practitioner interviews. Lessons are summarized into categories such as adoption strategy, modeling practices, and communication. This paper provides a source for future adopters of MBSE to review best practices and recommendations from a multitude of different experiences. This should improve the adoption and implementation of MBSE.

show abstract

Section: Automationmentioning

confidence: 99%

Section: Lessons Learned Categories Literature Examplesmentioning

confidence: 99%

MBSE adoption experiences in organizations: Lessons learned

Henderson,

McDermott,

Salado

2023

Systems Engineering

View full text Add to dashboard Cite

show abstract

“…They mention several gains of MBSE such as early defect detection, reuse, product line definition, risk reduction, improved communication, usage in the supply chain and standards conformance that are important. Suryadevara et al [11] imply that significant investment, a considerable learning effort and attainment of good tool interoperability are components required for success. Selberg et al [12] have studied MBSE adoption in a company, based on which they give recommendations for adopting MBSE.…”

Section: A Background and Related Workmentioning

confidence: 99%

Model-Based System Engineering Adoption in the Vehicular Systems Domain

Gustavsson¹,

Carlson²,

Enoiu³

2022

Annals of Computer Science and Information Systems

View full text Add to dashboard Cite

As systems continue to increase in complexity, some companies have turned to Model-Based Systems Engineering (MBSE) to address different challenges such as requirement complexity, consistency, traceability, and quality assurance during system development. Consequently, to foster the adoption of MBSE, practitioners need to understand what factors are impeding or promoting success in applying such a method in their existing processes and infrastructure. While many of the existing studies on the adoption of MBSE in specific contexts focus on its applicability, it is unclear what attributes foster a successful adoption of MBSE and what targets the companies are setting. Consequently, practitioners need to understand what adoption strategies are applicable. To shed more light on this topic, we conducted semi-structured interviews with 12 professionals working in the vehicular domain with roles in several MBSE adoption projects. The aim is to investigate their experiences, reasons, targets, and promoting and impeding factors. The obtained data was synthesized using thematic analysis. This study suggests that the reasons for MBSE adoption relate to two main themes: better management of complex engineering tasks and communication between different actors. Furthermore, engagement, activeness and access to expert knowledge are indicated as factors promoting MBSE adoption success, while the lack of MBSE knowledge is an impeding factor for successful adoption.

show abstract

“…This work provides an approach to lightweight consistency checking between heterogeneous models in a multi-view modelling context. In particular, we study an industrial multi-view modelling environment [ST18] in combination with agile development practices.…”

Section: Related Workmentioning

confidence: 99%

“…Further, models are also used for advanced development activities such as simulation and code generation. Besides, in industrial contexts, models as main project artifacts play an important role in documentation and communication between different development teams [ST18]. Models are becoming critical assets for development of industrial systems and software, not only within single projects but over several projects through model reuse.…”

Section: Introductionmentioning

confidence: 99%

Lightweight Consistency Checking for Agile Model-Based Development in Practice.

Jongeling¹,

Ciccozzi²,

Cicchetti³

et al. 2019

JOT

View full text Add to dashboard Cite

In model-based development projects, models at different abstraction levels capture different aspects of a software system, e.g., specification or design. Inconsistencies between these models can cause inefficient and incorrect development. A tool-based framework to assist developers creating and maintaining models conforming to different languages (i.e. heterogeneous models) and consistency between them is not only important but also much needed in practice. In this work, we focus on assisting developers bringing about multi-view consistency in the context of agile model-based development, through frequent, lightweight consistency checks across views and between heterogeneous models. The checks are lightweight in the sense that they are easy to create, edit, use and maintain, and since they find inconsistencies but do not attempt to automatically resolve them. With respect to ease of use, we explicitly separate the two main concerns in defining consistency checks, being (i) which modelling elements across heterogeneous models should be consistent with each other and (ii) what constitutes consistency between them. We assess the feasibility and illustrate the potential usefulness of our consistency checking approach, from an industrial agile model-based development point-of-view, through a proof-of-concept implementation on a sample project leveraging models expressed in SysML and Simulink. A continuous integration pipeline hosts the initial definition and subsequent execution of consistency checks, it is also the place where the user can view results of consistency checks and reconfigure them.

show abstract

Adopting MBSE in Construction Equipment Industry: An Experience Report

Cited by 36 publications

References 11 publications

MBSE adoption experiences in organizations: Lessons learned

MBSE adoption experiences in organizations: Lessons learned

Model-Based System Engineering Adoption in the Vehicular Systems Domain

Lightweight Consistency Checking for Agile Model-Based Development in Practice.

Contact Info

Product

Resources

About