MBSE and MBSA with Capella and Safety Architect Tools

Abstract

The development of critical systems is a challenging task that requires collaborative work for various purposes: specification, design and verification. Today, no single modeling language and environment covers all these aspects. ARCADIA and Capella © are Model-based System Engineering (MBSE) method and tool developed for the system design process. ARCADIA/Capella also adopts a viewpoint-based description to describe engineering specialty, such as the safety engineering. Safety Architect © is a MBSA (Model Based Safety Analysis) tool developed by ALL4TEC to analyze the robustness of design models. Indeed, Safety Architect can use design models imported from usual modelling tools, such as Capella, in order to perform classical safety analyses: automatic deduction of fault tree of the identified feared events. In this paper, we present our MBSE and MBSA approach developed in the Clarity project around Safety viewpoint in Capella and the import legacy into Safety Architect in order to realize safety analysis.

Model-driven engineering to ensure automotive embedded software safety. Methodological proposal and case study

“…Several MBSA approaches exist. Some of them, such as the Failure Propagation and Transformation Notation (FPTN) [21] or the Hierarchically Performed Hazard Origins and Propagation Studies (HiP-HOPS) [22] are methodological; others, such as FSAP/NuSVM [23] or Safety Architect [34], are tools; yet others, such as Figaro (implemented in EDF's KB3 tool [35]), SAML (Safety Analysis Modeling Language) [26] or AltaRica [37] are languages. In addition to these native MBSA approaches, some of the MBSE approaches mentioned earlier in 3.1 extend their semantics to support safety analysis through annexes or safety related packages.…”

Event-B formalization of a variability-aware component model patterns framework

“…In our work, we consider hierarchical components models as an abstraction of the classical "boxes and arrows" modeling formalism used to model: systems as for example Capella [27], SysML [21] or AADL [14]; software as for example BIP [6], UML [25], Scade [4]; or hardware as for example VHDL [16]. In each of these formalisms, components are connected through arrows (and sometimes ports or interfaces).…”