Designing development processes related to system of systems using a modeling framework

Abstract

As manmade systems become increasingly complex and evolve into Systems of Systems of various kinds, a multitude of tasks needs to be performed in coordination throughout their development. In this paper, we briefly introduce a new modeling framework that was designed following systems engineering principles and based on extensive research of development efforts characteristics. We focus on the framework's ability to support the design of development processes while addressing Systems of Systems‐related challenges. We then describe a case study of using this framework to introduce a new capability into a large enterprise, which specializes in systems and System of Systems development. The example demonstrates the utility of using this framework for planning complex development efforts as well as improving the coordination of multiple development efforts in System of Systems development scenarios.

Using Domain-Specific Models to Facilitate Model-Based Systems-Engineering: Development Process Design Modeling with OPM and PROVE

“…Unlike the established OPM, PROVE is a recently-introduced addition to the stock of modeling methodologies. PROVE is a DSM for DPD, designed based on DPD domain ontology [24]. As with OPM, pertinent aspects of PROVE will be explained in their context of use.…”

“…We chose PROVE as the representative DSM due to two reasons: (1) PROVE's core concepts are consistent with OPM [24]; thereby, allowing us to explicitly demonstrate how DSMs may contribute to state-of-the-art GPM; and (2) PROVE establishes a DPD ontology with concise notation, allowing us to communicate domain ideas easily with readers.…”

“…By comparison, an equivalent PROVE model is shown in Figure 12, relying on the analysis of Table 2. A detailed description of PROVE's ontology and modeling process is given in [24,25] and is beyond the scope of this paper. We briefly note that in PROVE, process descriptions are represented by rectangles; and objects in specific states are denoted by directed arrows from source process to target process, conveying the object and attribute using an "object::attribute" label (unspecified states/attributes are designated as "0").…”

“…We expect both hypotheses to be confirmed, thereby showing that DSM can relieve cognitive load in model-based design. First, in Section 2, we provide background regarding MBSE and the two modeling approaches that we use in our demonstration: the generalpurpose Object Process Methodology (OPM) [17,22,23] and the domain-specific Process Oriented Viewpoint for Engineering (PROVE) [24,25]. While our ideas are demonstrated with these specific approaches, this paper is not about them, does not attempt to promote any of them.…”

Implementing MBSE – An Enterprise Approach to an Enterprise Problem

“…The migration from document-based systems engineering processes to MBSE requires more than purchasing tools and a one-week course on Systems Modeling Language (SysML). It requires a system-of-systems engineering approach guided by an enterprise architecture (Shaked & Reich, 2019).…”