Integration of safety analysis and software development methods

Briones, Javier Fernández; miguel, morgan; Silva, J.P.; Alonso, Alejandro

doi:10.1049/cp:20060228

Cited by 4 publications

(6 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The methodology provided by Eurocontrol ( [2], succinctly explained in [7]) strictly forbids allocating a failure rate to the software and we have to assume that software fails. Allocation of SWALs is accomplished by looking at the overall system design in its operational environment.…”

Section: Resultsmentioning

confidence: 99%

“…They can be used to assert, as proposed in [7], that a safe-aware component affects the safety of another safe safe-aware component, that a safeaware component affects the safety of a safe-aware capability or that a safe-aware capability affects the safety of another safe-aware capability.…”

Section: Safety Conceptsmentioning

confidence: 99%

“…We are carrying out our work ( [4], [5], [6], [7]) in the context of air navigation systems (ANS) where a component and model-driven based development is suitable and where safety needs are significant. Eurocontrol works to create regulatory requirements (ESARR) and guidelines to improve the safety of air navigation.…”

Section: Introductionmentioning

confidence: 99%

“…Further clarifications about safety are detailed in [7]. Section 2 gives an overview about the use of safety analyses during the specification of the architecture in a MDA.…”

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

Application of Safety Analyses in Model Driven Development

Briones

Miguel

Silva

et al. 2007

Software Technologies for Embedded and Ubiquitous Systems

View full text Add to dashboard Cite

Abstract. Some high integrity software systems require the rigorous validation of safety properties. Assessing whether software architectures are able to meet these requirements is of great interest: to avoid the risk that the implementation does not fulfill requirements due to a bad design, and, to reduce the development cost of safety critical parts of the system. Safety analyses like FMECA and FTA are two methods used during preliminary safety assessments. We have implemented tools to automatically generate safety analyses from the models of the architecture: a UML profile for safety, modeling languages to express safety analyses, and a model transformation chain. Safety analysts can use these tools to annotate the models, analyze the architecture, and recommend system engineers mitigation means to apply for improving the architecture.

show abstract

Section: Resultsmentioning

confidence: 99%

Section: Safety Conceptsmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

“…Further clarifications about safety are detailed in [7]. Section 2 gives an overview about the use of safety analyses during the specification of the architecture in a MDA.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Application of Safety Analyses in Model Driven Development

Briones

Miguel

Silva

et al. 2007

Software Technologies for Embedded and Ubiquitous Systems

View full text Add to dashboard Cite

show abstract

“…Many other approaches for the modeling of safety requirements use only one description language of Pap's portfolio. The two most popular ones are on the one hand the description by UML, like in [7] and on the 1 http://www.quality-one.com/services/fmea.php other hand the description by (temporal) logics, like in [10]. The modeling of safety requirements via (temporal) logics is very widely used for formal verification of systems.…”

Section: Formalization Of Safety Requirementsmentioning

confidence: 99%

Deriving fault-detection mechanisms from safety requirements

2011

View full text Add to dashboard Cite

Safety requirements are an important artifact in the development of safety critical systems. They are used by experts as a basis for appropriate selection and implementation of fault detection mechanisms. Various research groups have worked on their formal modeling with the goal of determining if a system can meet these requirements.In this paper, we propose the application of formal models of safety requirements throughout all constructive development phases of a model-driven development process to automatically generate appropriate fault detection mechanisms. The main contribution of this paper is a rigorous formal specification of safety requirements that allows the automatic propagation, transformation and refinement of safety requirements and the derivation of appropriate fault detection mechanisms. This is an important step to guarantee consistency and completeness in the critical transition from requirements engineering to software design, where a lot of errors can be introduced into a system by using conventional, non-formal techniques.

show abstract

Hazardous Failure Rate of the Safety Function

Rástočný

Ždánsky

2015

Communications in Computer and Information Science

View full text Add to dashboard Cite

Integration of safety analysis and software development methods

Cited by 4 publications

References 0 publications

Application of Safety Analyses in Model Driven Development

Application of Safety Analyses in Model Driven Development

Deriving fault-detection mechanisms from safety requirements

Hazardous Failure Rate of the Safety Function

Contact Info

Product

Resources

About