Deriving Safety Cases for Hierarchical Structure in Model-Based Development

Abstract

Abstract. Model-based development and automated code generation are increasingly used for actual production code, in particular in mathematical and engineering domains. However, since code generators are typically not qualified, there is no guarantee that their output satisfies the system requirements, or is even safe. Here we present an approach to systematically derive safety cases that argue along the hierarchical structure in model-based development. The safety cases are constructed mechanically using a formal analysis, based on automated theorem proving, of the automatically generated code. The analysis recovers the model structure and component hierarchy from the code, providing independent assurance of both code and model. It identifies how the given system safety requirements are broken down into component requirements, and where they are ultimately established, thus establishing a hierarchy of requirements that is aligned with the hierarchical model structure. The derived safety cases reflect the results of the analysis, and provide a high-level argument that traces the requirements on the model via the inferred model structure to the code. We illustrate our approach on flight code generated from hierarchical Simulink models by Real-Time Workshop.

Reliable execution of statechart-generated correct embedded software under soft errors

“…This idea could also be used to plug together unit tests, e.g., JUnit, and the reliability evaluation. At the end, using these verication artifacts the safety cases for reliability could be generated automatically as [22] does for software correction.…”

PHYSFRAME: type checking physical frames of reference for robotic systems

“…Our abstract domains are hence different from theirs and our method is type system based. The work by Basir et al [6] on automated theorem proving for automatically generated code also presented a case study to verify two frame-safety requirements. META-AMPHION system [24] helps domain experts build domain-specific program synthesizers.…”

Engineering Functional Safety Requirements for Automotive Systems: A Cyber-Physical-Social Approach

“…Moreover, Li and Zhang [12] present a hazard analysis method for automotive control systems that incorporate safety procedures in the traditional development process. Basir et al [13] propose an approach that adopts the Goal Structuring Notation (GSN) [14] to construct safety cases to trace requirements to the code. The work of Habli et al [15] examines how modeldriven development and assessment can provide a basis for the systematic generation of functional safety requirements.…”