Model-based Systems Architecting

Appendix 4Implementing CESAM through a SysML Modeling Tool

This appendix is dedicated to the presentation of a generic organization of a concrete system model based on the CESAM systems architecting framework, using the classical SysML modeling language¹ (see for instance Friedenthal et al. (2012)). Note, however, that organizing a concrete system model is always dependent on the chosen SysML modeling tool, since the different modeling tools that are existing on the market are not at all implementing in the same way the SysML standard that we may use to develop a system model. This appendix tried to be as implementation-independent as possible, but beware that its contents shall be adapted, depending on the modeling tool that you are using.

A4.1. Generic structure of a SysML system model based on the CESAM framework

We shall recall first that, from the perspective of a modeling tool, a system model consists of a set of technical data, associated with the considered system, that can be expressed in textual and graphic formats. These technical data are stored in a structured database that can be accessed by systems engineers through the modeling tool, with which they can manage the system model by adding, deleting and/or modifying its key elements that are of the following two different types:

1) Elementary objects, that is, the system and its stakeholders, lifecycle phases, use cases, functions, functional modes, components, configurations, needs, requirements and flows.