Chapter 6: System Design Models

The "System Design Modeling" component of medini analyze supports the modelling and management of all relevant design models in the SysML language ranging from system architecture, functions, over design, software, hardware, down to IP models at chip level.

The SysML editor enables the creation of SysML models for analysis purpose and most of the analyses require a model to work properly. The editor features modelling of structures (e.g. blocks, containment, ports and connections) as well as behavior (e.g. functions, activities, actions). The editor provides more flexibility than the strict language definition, but the underlying metamodel conforms to OMG's SysML[2]. Therefore models can be imported from various 3rd party modelling tools. For further details as well as a list of supported tools see About SysML Model Integration.

Ansys medini analyze adds safety extensions to SysML that embed concepts such as failure modes/malfunctions and failure rates into the language. Therefore, it is possible to add this information directly to the elements. For example, this means a SysML part can carry failure modes and a failure rate (see also Safety Analysis Overview and Working with the failure net). Moreover, the object-oriented type concept is aligned with the safety extensions so that a block type can define a fault model (i.e. failure modes, failure rates, distributions, failure relations) of its typed parts. These concepts provide a powerful way to express common failure characteristics at the type which then can be parameterized (via variables) for the individual instances. See Editing Properties of Model Elements for more details. These models are also the base for safety analysis as FTA, FMEA, and FMEDA (DC Worksheets) where data is re-used that is specified for system model elements.

As with all modeling concepts, you can specify trace relations between the elements of a SysML model to other artifacts of the project, such as safety requirements, HARA/FHA, FTA, FME(C)A, FMEDA, and cross-check consistency rules.



[2] From 2022 R1 onwards the metamodel will converge towards the upcoming version 2 of the standard.