Engaging Mechanical Engineers in System Modeling

Abstract

In Model Based Systems Engineering (MBSE) the system model is used to capture and share Systems Engineering (SE) data and artifacts. Using the model to communicate with the project engineers is found to be more successful with software (SW) engineers than with other domains. As a result, the system model is developed unevenly. This article reports on how a company, whose system model is decisively more detailed in its description of SW sub‐systems, might better involve mechanical (and other) engineers in system modeling. Case‐based research is applied to understand the company's challenges. The conclusion is that the challenges originate from failing to consider the differences in how these domains view and relate to a system under development. The research determined that the models developed in the company‐specific tool implementation were incapable of producing useful deliverables for non‐software engineers. In the absence of a plan for how a mechanical engineer could access information from the model, the authors recommend defining a modeling environment to ensure the necessary contributions from both systems engineers and mechanical engineers.