A state-of-the-art technique has been introduced in recent years called STPA (System-Theoretic Process Analysis), which is based upon a new accident model called STAMP (Systems-Theoretic Accident Model and Processes). This technique’s focus on defining the initial design decisions based on safety considerations is one of its advantages. Our recent efforts have focused on enhancing MBSA (Model-Based Safety Analysis) instruments to deliver more precise, coherent failure analysis automatically. Our established techniques are based on the systematic capture of the important individual components or combinations that lead to a system failure using component models of failure modes in conjunction with a system structure. We have also developed an extension to perform the STPA procedures within the MBSA environment. In this journal, we aim to integrate both the developed MBSA tool and the STPA extension to provide additional system design-related results. The STPA results shall be injected into the system model as components’ failure modes to visualize the system effects of each non-safe scenario. This journal extends the research work we have introduced in our previous publications.
A. Abdellatif, Florian Holzapfel· Proceedings of the Instituti...· 0 citations
This paper presents an airborne software development approach for manned and unmanned aerial vehicles aimed at reducing inconsistencies across system, model-based functional, and embedded software domains. In environments influenced by standards such as ARP-4754B and DO-178C, these inconsistencies typically stem from insufficient enforcement across domain boundaries rather than missing process definitions. Building on a previously proposed toolchain centered on a relational interface database, we identify recurring failure modes and propose a repository-centered implementation to address them, tailored to small, resource-constrained teams operating without heavyweight process overhead. Each domain is assigned a primary repository with cross-repository references and dedicated CI pipelines that generate, update, and validate the exchanged artifacts. Automated interface updates, differential change notifications, and consistency checks propagate changes with minimal manual effort and surface inconsistencies before the time-consuming code-generation and compilation steps. An initial implementation in an ongoing experimental project is described, with qualitative feedback from its early use.
Nils Schlautmann, V. Sinitsyn, Benjamin Engelhard et al.· 0 citations
We use cookies to run the site and, with your consent, for analytics and to show ads.
See our Cookie Policy.
