| S. J. Clarke and J. A. McDermid. Software fault trees and weakest preconditions: A comparison and analysis, 1993. |
....can have all the normal programming errors like unintended handling of pointers and mixing of variables, and also various syntax errors. These errors can be found during compile time, or by cyclic debugging or similar. Clarke and McDermid provides a classification of di#erent software errors [5]: Control errors are those that force the task through another path than intended. Value errors may be the assignment of incorrect values to the correct variable. Addressing errors assign values to incorrect variables. Termination errors are in some way related to control errors, but could ....
Stephen Clarke and John McDermid. Software Fault Trees and Weakest Preconditions: A Comparison and Analysis. Software Engineering Journal, 8(4):225 -- 236, July 1993.
....experience, to failure behavior that is only significant in multitasking, distributed systems and real time systems, where more than one task is competing for the same resources, e.g. processing power, memory, computer network, etc. Failure modes: 1. Sequential failure behavior (Clarke et al. [17]) Control failures, e.g. selecting the wrong branch in an if then else statement. Value failures, e.g. assigning an incorrect value to a correct (intended) variable. Addressing failures, e.g. assigning a correct (intended) value to an incorrect variable. Termination failures, ....
Clarke S.J. and McDermid JA. Software fault trees and weakest preconditions: a comparison and analysis. Software Engineering Journal. 8(4):225-236, 1993.
....systems, where more than one task is competing for the same resources, e.g. processing power, memory, computer network, etc. 8 Byzantine Timing Synchronization Ordering Sequential failures Figure 3 2. The relation between the failure modes. 1. Sequential failure behavior (Clarke et al. [10]) Control failures, e.g. selecting the wrong branch in an if then else statement. Value failures, e.g. assigning an incorrect value to a correct (intended) variable. Addressing failures, e.g. assigning a correct (intended) value to an incorrect variable. Termination failures, e.g. ....
Clarke S.J. and McDermid JA. Software fault trees and weakest preconditions: a comparison and analysis. Software Engineering Journal. 8(4):225-236, 1993.
....is to show that the logic contained in the software design will not produce system failures, and to determine environmental conditions which could lead to the software causing a safety failure. Clark and McDermid propose a more traditional view of the application of fault trees to software [Clark, McDermid 1993]. It is suggested that weakest preconditions are used for program specification and validation, and software fault tree analysis is employed for a system wide analysis of hazards. The scope of software fault trees can be increased to include, for example, compiler errors, control errors, and ....
Stephen J. Clarke and John A. McDermid, "Software Fault Trees and Weakest Preconditions: A Comparison and Analysis ", Software Engineering Journal, July 1993, pp. 225-236.
No context found.
Cla91. Clarke, Stephen J and McDermid, John A, "Software Fault Trees And Weakest Preconditions --- A Comparison And Analysis", To Appear, University of York, Department of Computer Science (1991).
No context found.
S. J. Clarke and J. A. McDermid. Software fault trees and weakest preconditions: A comparison and analysis, 1993.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC