Towards a maturity assessment scale for the Systems Engineering assets valorization to facilitate Model-Based Systems Engineering adoption

Résumé En

CONTEXT AND OBJECTIVES In the context of engineering practices transition from a document-based approach towards Model-Based Systems Engineering (MBSE) approaches, it is necessary to demonstrate to end-users how MBSE will help them design their system, even if their daily routines are disrupted. However, unlike engineering practices that can change, engineer's know-how is sustainable and remains key to the development of good systems. For that purpose, previous works have shown the relevance of patterns for the capture of engineering assets and their valorization through reuse (Wu et al. 2018). Yet, it appears that the current trend to adopt MBSE methodologies (Figure 1) does not make enough sense for engineers to take the leap towards these new approaches (Huldt and Stenius 2018), as the gap with engineering practices is too significant. Figure 1. Current trend for the adoption of MBSE methodologies Unlike the current trend to capitalize on know-how after a development in MBSE, the adoption process should consider engineer's know-how before rushing towards modelling (Figure 2). In the proposed approach the process starts by extracting System Engineering (SE) patterns. Among them, some will meet the needs of engineering teams more than others. It is therefore these patterns who will be modelled and integrated into an MBSE approach. This approach allows engineering teams to choose the patterns that will have the most added value for them, and thus facilitate the adoption of MBSE methodologies. Figure 2. Proposed approach for the adoption of MBSE methodologies The aim of this article is to propose a scale to evaluate the maturity of the valorization of Systems Engineering assets. This paper assumes that this valorization process consists in the highlighting of valuable engineers' know-how to be disseminated to other engineers at the time and at the level of comprehension needed. It means that, if the final goal is to reuse SE assets, other processes are necessary to achieve these expectations. As promoted in the software