System engineering artifacts for SoS

Abstract

This describes a system of systems (80S) systems engineering (SE) artifacts, compares and contrasts them with simllar ones developed and used for Individual systems, and explains how they are used to guide SoS engineering processes. This concludes with next steps for using 80S artifacts to continue maturing the understanding of 80S SE in an international cooperative effort with the United Kingdom, Australia, and Canada. BACKGROUND AND MOTIVATION

Systems of systems: From mission definition to architecture description

“…The main elements of the wave model have been presented in Section and Figure . The critical information to realize effective SoS SE, and the corresponding artifacts were identified by Dahmann et al As we are interested only in the analysis and architecture phases of the wave model, in the following section, we present only the artifacts related to these two stages. The artifacts are described as follows: (a) The SoS capability objectives correspond to the main goals of the SoS; (b) the SoS CONcept Of OPerationS (CONOPS) defines the use of the SoS constituent system functionality in an operational context; (c) the systems information corresponds to information pertaining to the systems that impacts the SoS capability objectives, and this information is collected to be used for replacements as the SoS evolves; (d) the SoS requirement space bounds the operational tasks and missions while considering the environment change that affect the execution of the required functions; (e) the SoS performance measures and methods capture the basis for assessing the overall performance of the SoS and for improving the SoS; (f) the effectiveness data of the SoS are collected from different environments to identify the areas needing more attention; (g) the SoS SE planning elements determine “the rhythm, technical reviews, and decision processes across the SoS evolution.” These elements furnish also “the principal SE rules of engagement for the SoS and are utilized by all SoS actors”; (h) the SoS risks are captured and tracked.…”

“…The conceptual model was proposed based on the modeling experience using the SysML language of SE approaches, on SoS artifacts defined in Refs. and on the overall experience in rigorously defining a mission . Figure highlights the involved concepts.…”

“…In this paper, we define SoS as “a set of interacting systems that interact with each other and their environment to provide a common mission.” The mission is the main concept on the conceptual model (capability objectives artifact in Ref. ). We define a mission as a finality that the SoS must achieve by collaborating constituent systems.…”

Integrating systems engineering and test & evaluation in system of systems development

“…Table 1 displays a description of each step along with the associated key SoS SE artifacts [18]. Artifacts particularly germane to T&E are in bolded text.…”

Educating software engineers to become systems engineers

“…Table 3 shows a complete mapping between system engineering activities [8][9] and the project artifacts produced by the team and the supporting tools provided by the class. …”