A Systematic Approach for Integrating Fault Trees into System Statecharts

Ariss, Omar El; Xu, Dianxiang; Wong, W. Eric; Chen, Yuting; Lee, Yann-Hang

doi:10.1109/compsac.2008.19

Cited by 7 publications

(4 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…There is some literature introducing the integration of safety analysis into functional modeling. El Ariss et al() provided a method to integrate FTs into statecharts to obtain a functional model with safety information, which facilitates safety inspection. Kim et al provided a method to bridge the gap between the FTs and the UML state machine to enable the verification of undesired behavior by translating FTs into statecharts.…”

Section: Related Workmentioning

confidence: 99%

Detecting safety‐related components in statecharts through traceability and model slicing

Kan

Huang

2017

Softw Pract Exp

View full text Add to dashboard Cite

With rapid development in software technology, more and more safety-critical systems are software intensive. Safety issues become important when software is used to control such systems. However, there are 2 important problems in software safety analysis: (1) there is often a significant traceability gap between safety requirements and software design, resulting in safety analysis and software design are often conducted separately; and (2) the growing complexity of safety-critical software makes it difficult to determine whether software design fulfills safety requirements. In this paper, we propose a technique to address the above 2 important problems on the model level. The technique is based on statecharts, which are used to model the behavior of software, and fault tree safety analysis. This technique contains the following 2 parts, which are corresponding to the 2 problems, respectively. The first part is to build a metamodel of traceability between fault trees and statecharts, which is to bridge their traceability gap. A collection of rules for the creation and maintenance of traceability links is provided. The second part is a model slicing technique to reduce the complexity of statecharts with respect to the traceability information. The slicing technique can deal with the characteristics of hierarchy, concurrency, and synchronization of statecharts. The reduced statecharts are much smaller than their original statecharts, which are helpful to successive safety analysis. Finally, we illustrate the effectiveness and the importance of the method by a case study of slats and flaps control units in flight control systems. /journal/spe Softw Pract Exper. 2018;48:428-448. We now introduce 6 dependence relations through Definitions 6 to 11. These relations aim at detecting other safety-related elements which are not in slicing criteria. Definition 6. (Data Dependence within a Single Automaton) Let el 1 and el 2 be 2 elements (states or transitions) in a single automaton. el 2 is data dependent on el 1 denoted by el 2 → dd el 1 if there exists a path from el 1 to el 2 such that RCUV (el 2 ) ∩ UpdV(el 1 ) − ⋃ el i ∈ITD(el 1 ,el 2 ) UpdV(el i ) ≠ ∅. Definition 7. (Data Dependence among Automata) Let A, B, and C be 3 automata in an EHA. Let el A be an element of A, el B be an element of B, and s C be a state in σ C , and they satisfy A, B ∈ ρ(s C ). el A is data dependent on el B denoted by el A → pd el B if RCUV (el A ) ∩ UpdV(el B ) ≠ ∅. Definition 8. (Control Dependence among Automata) Let A, B, and C be 3 automata in an EHA. Let el A be an element of A, el B be an element of B, and s C be a state of C, and they satisfy A, B ∈ ρ(s C ). el A is control dependent on el B denoted by el A → sd el B if TE(el A ) ∩ GE(el B ) ≠ ∅ Definition 9. (Control dependence within a Single Automaton) Let el be an element and t be a transition in a single automaton. el is control dependent on t denoted by el→ cd t if there exists a path from t to el such that the set E = {el ′ |t→ xd el ′ (→ xd represents → dd , → pd , → sd )} sati...

show abstract

Section: Related Workmentioning

confidence: 99%

Detecting safety‐related components in statecharts through traceability and model slicing

Kan

Huang

2017

Softw Pract Exp

View full text Add to dashboard Cite

show abstract

“…They point out that the SD should be built separately from the construction of the FT, but each model's construction process should be influenced by others. El Ariss et al 17,35 presented an approach for integrating FTA with SD, and the approach directly can solve some other aspect problems. Sa´nchez and Felder, 18 Sa´nchez et al, 36 and Dasso and Funes 37 propose an approach by integrating the safety requirement described by FT with SD in order to generate test cases.…”

Section: Related Workmentioning

confidence: 99%

“…They point out that the SD should be built separately from the construction of the FT, but each model's construction process should be influenced by others. El Ariss et al 17,35 presented an approach for integrating FTA with SD, and the approach directly first, we will define conversion rules that transform other gates in FT into SD notations through the analysis of their semantics. The conversion rule for continuous time into SD notations is given in this article, and the conversion rule for discrete time will be given in the future.…”

Section: Related Workmentioning

confidence: 99%

Research on safety analysis for airborne system based on extended functional model

Jiang

Zhu

Cao

et al. 2015

Advances in Mechanical Engineering

View full text Add to dashboard Cite

With the widespread use of embedded system in safety critical areas, system safety assurance has become one of the research hotspots of engineering technologies. System safety analysis mainly concentrates on the requirement specification and the recent design, and in the process of the actual development of the software, safety requirement analysis and design are two independent processes. This article expands the safety requirements described by fault tree into state diagram and proposes the new concept ''fault state diagram,'' which can unify safety requirement model and functional model. Based on the fault state diagram, this article proposes the method of airborne system safety analysis, including the following: gives out one method for abstracting and describing safety requirements from system fault tree based on Backus Normal Form; defines the transformation rules from fault tree logic gates and continuous time into state diagram elements; designs safety requirement information mapping table which translates safety requirements into state diagram elements; and designs the automatic construction algorithm of fault state diagram, which is based on the transformation rules and mapping table. Finally, a small gas stove control system case using the method proves the feasibility and effectiveness of the proposed method.

show abstract

“…Our previous work [23] presented a technique that integrated fault tree [24] hazards into the system statechart. Although attack trees are simpler in form (due to the limited types of gates used), they are more complex to integrate.…”

Section: Related Workmentioning

confidence: 99%

Towards an Enhanced Design Level Security: Integrating Attack Trees with Statecharts

Ariss

2011

2011 Fifth International Conference on Secure Software Integration and Reliability Improvement

Self Cite

View full text Add to dashboard Cite

Software security has become more and more critical as we are increasingly depending on the Internet, an untrustworthy computing environment. Software functionality and security are tightly related to each other; vulnerabilities due to design errors, inconsistencies, incompleteness, and missing constraints in system specifications can be wrongly exploited by security attacks. These two concerns, however, are often handled separately. In this paper we present a threat driven approach that improves on the quality of software through the realization of a more secure functional model. The approach introduces systematic transformation rules and integration steps for mapping attack tree representations into lower level dynamic behavior, then integrates this behavior into statechart-based functional models. Through the focus on both the functional and threat behavior, software engineers can introduce, clearly define and understand security concerns as software is designed. To identify vulnerabilities, our approach then applies security analysis and threat identification to the integrated model.

show abstract

A Systematic Approach for Integrating Fault Trees into System Statecharts

Cited by 7 publications

References 9 publications

Detecting safety‐related components in statecharts through traceability and model slicing

Detecting safety‐related components in statecharts through traceability and model slicing

Research on safety analysis for airborne system based on extended functional model

Towards an Enhanced Design Level Security: Integrating Attack Trees with Statecharts

Contact Info

Product

Resources

About