Software fault tree

Software Fault Tree ( Soft Trees ) The soft tree technique is used to determine what software event, failure, or combination of each will result in a real or hypothetically loss event (a top event). This top-down analytical approach, which assumes a problem and then evaluates affecting conditions backward to determine causal factors, also takes into consideration any influencing environmental factors. It is concerned primarily with the analysis of any hardware-software interfaces that deal directly with the operation of mechanical components. [Pg.180]

Software System Hazard Analysis This type of analysis is conducted similar to a hardware system hazard analysis (SHA), analyzing software functional processing steps to determine whether they may have any particular hazardous effect on the system. The analysis utilizes a hazard-risk index to illustrate the severity of each potential failure. The main advantage to this method is in its ability to positively identify safety-critical hardware and software functions as well as consider the effect of the human element in system software operations. The results of the software SHA, which identifies single-point failures or errors within a system, can often be used to assist in the development of a software fault tree analysis or, to some degree, a system FMEA. However, as with the other various SWHA techniques briefly described above, this method is also time-consuming and costly to perform. [Pg.181]

Dehlinger, J., Lutz, R. PLFaultCAT A Product-Line Software Fault Tree Analysis Tool. Automated Software Engineering 13(1), 169-193 (2006)... [Pg.160]

Dehlinger, J., Humphrey, M., Suvorov, L., Padmanabahn, P., Lutz, R. Decimal and PLFaultCAT From Product-Line Requirements to Product-Line Member Software Fault Trees, Research Demonstration. In 29th International Conference on Software Engineering (ICSE 2007), Minneapolis (2007)... [Pg.160]

FIGURE 21.31 Software fault tree. The solid lines define the requirements definition and analysis phase fault tree. The requirements definition and analysis phase and coding phase fault tree is obtained by adding solid and dashed contributions. [Pg.2313]

Temporal (relationship) gate in software fault tree analysis. [Pg.341]

Soft Tree Also known as Software Fault Tree Analysis, a system safety technique used to evaluate a single loss event and/or the effect of simultaneous failures with a software system on that single loss, or top event. [Pg.218]

There are numerous software safety tools on the market, some quite good. And you can even take some of our current tools and use them for analyzing software systems. The most common ones are software hazard analysis, software fault tree analysis, and software FMECA. These are good starts, but insufficient to do the job completely. However, before you can attack the problem of software safety, a few facts should be stated first ... [Pg.243]

Software fault tree analysis (also called soft tree analysis)... [Pg.248]

It has become quite popular to integrate timed Petri-Nets with software fault tree analysis. You can use the Petri-Net to describe the system architecture and then switch to software fault trees to describe the hazards in the system and the events that lead to that top event and keep switching back and forth to analyze the software safety of the system. [Pg.249]

Code analysis Code analysis goes into the very heart of the software system and verifies that the coded program actually accomplishes what it is designed to do. Software fault trees and Petri-Nets are used, as well as various other techniques. Some of the other tools used are code logic analysis, code data analysis, code interface analysis, measurement of complexity, code constraint analysis, safe subsets of programming languages, and formal methods and safety-critical considerations. [Pg.249]

SFTA (Software Fault Tree Analysis) [1] is a static analysis technique which is primarily used to discover all potential faults such as faulty inputs or software bugs that could occur in software. SFTA has also been used for verifying software... [Pg.403]

Leveson, N.G., Cha, S.S., Shimeall, T.J. Safety verification of Ada Programs Using Software Fault Trees. IEEE Software 8(4), 48-59 (1991)... [Pg.412]

Phuh Westerheide, Quirk, Taylor and Voges, Software fault tree analysis in Verification and Validation of Real time software ed W.J.Quick Springer Verlag 1985. [Pg.76]

At the specification phase we intend to concentrate on the benefits of a formal specification for safety analysis proofs. Proof is currently a very expensive activity and so careful analysis of which requirements should be proven is necessary. We intend to use software fault tree analysis to help identify the key safety requirements that should be proven. [Pg.173]

Programs Using Software Fault Trees. IEEE Software July 1991, 48 - 59... [Pg.240]

Helmer, G., Wong, J., Slagell, M., Honavar, V., Miller, L., Wang, Y., Lutz, R. Software fault tree and colored petri net based specification, design and implementation of agent-based intrusion detection systems. IEEE Transactions of Software Engineering (2002) (submitted)... [Pg.92]

Big Chemical Encyclopedia

Chemical substances, components, reactions, process design ...