MBSE for Real World Teams

Abstract With the release of the OMG Systems Modeling Language (SysML) (Object Management Group, 2007) there was a surge of enthusiasm for model‐based systems engineering (MBSE). Expectations were high. Cumbersome, fragmented documents would be completely replaced by coherent, fully integrated models. The models would serve as the “Single Version of the Truth” (later transitioning to models being part of the “Authoratative Source of Truth”). While progress has been made, this utopian vision has largely failed to materialize. Certainly tool and language limitations have been a factor. However, the bigger factor in many communities has been human factors challenges. In our enthusiasm to propagate the MBSE vision, we forgot to perform the most basic systems engineering task: stakeholder analysis. This paper will introduce some of the basic human factors issues that were overlooked. The paper will then discuss three concrete cases in which a community was struggling with the abstract, radical change approach and how the teams involved have modified this approach and tooling to make it more practical and successful for those communities. Finally, the paper will conclude with some recommendations to consider when undertaking the introduction of MBSE methods in a new community.