Abstract
In this paper, we define Model Based Systems Engineering (MBSE) as a set of different approaches which vary in scope and in purpose, as opposed to defining it as a monolithic concept. To do so, we inductively extract common themes from papers proposing new MBSE methods based on the type of Systems Engineering (SE) artifacts produced and the expected benefits of MBSE implementation. These themes are then validated against the experiences depicted in a second set of papers evaluating the deployment of MBSE methods in practice. We propose a taxonomy for MBSE which identifies three main categories: system specification repositories, system execution models, and design automation models. The proposed categories map well onto common discussions of the nature of the SE activity, in that the first is employed in the management of system development processes and the second in the understanding of system performance and emergent properties. The third category is almost exclusively discussed in an academic context and is therefore more difficult to relate to SE practice, but its features are clearly distinct from the other two. The proposed taxonomy clarifies what MBSE is and what it can be, therefore helping focus research on the issues that still prevent MBSE practice from living up to expectations.
