Scott 1994. John A. Scott and J. Dennis Lawrence, Testing Existing Software for Safety-Related Applications, Lawrence Livermore National Laboratory (in prep).  Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
Safety Assurance of Commercial-Off-The-Shelf Software - Lindsay, Smith (2000) (Correct)
.... of COTS items is to use black box testing together with system level fault and operational system [Voas98] However, the effectiveness of black box testing to achieve high levels of integrity is questionable and more rigorous testing generally requires knowledge of design and source code structure [Scott]. A particular problem is determining the total functionality of the COTS item to test [McDermid98] 4.4 Using Empirical Evidence Some standards such as DO 178B [Std178B] and IEC 61508 [Std61508] allow assurance to be generated from empirical evidence such as operational use. Where it is ....
J.A. Scott and J.D. Lawrence. Testing Existing Software for Safety-Related Applications. Lawrence Livermore National Laboratory, Report UCRLID -117224, Revision 7.1.
Safety Verification Conditions For Software-Intensive Critical.. - Wong (1998) (Correct)
....the hazards. This step is necessary even after hazards have been identified and controlled through design, in order to determine if any mistakes were made in the safety engineering process. Safety verification includes both static and dynamic analysis, such as system testing and code inspections [SL94], as well as software fault tree analysis [LCS91] and formal verification techniques [Bar97] Process checks are conducted to ensure that the hazard mitigations identified in the earlier stages of development have been implemented. Final system risk assessment is performed to ensure that the risks ....
John A. Scott and J. Dennis Lawrence, "Testing Existing Software For Safety-Related Applications", Fission Energy and Systems Safety Program, Lawrence Livermore National Laboratory, UCLR-ID-117224, Revision 7.1, December 1994.
Design Factors for Safety-Critical Software - Dennis Lawrence Gary Self-citation (Lawrence) (Correct)
....IEEE 1074 (1991) Section 2. Summary 2 IEEE Standard for Software Safety Plans, IEEE 1228 (1994) Research performed by LLNL for the NRC. This research is documented in the following references (in addition to those cited in Section 1. 2) Preckshot 1993a, Preckshot 1993b, Persons 1994, and Scott 1994. A report, Factors in Software Quality, written for Rome Air Development Center in 1977 (McCall et al. 1977) The general literature on software engineering, as published in books, journal articles and technical reports. Much of the information in this report also appears in Ploof and Preckshot ....
Scott 1994. John A. Scott and J. Dennis Lawrence, Testing Existing Software for Safety-Related Applications, Lawrence Livermore National Laboratory (in prep).
Ensuring the Inspectability, Repeatability and.. - Wong, Joyce, Ronback (1998) (Correct)
No context found.
SCO94 John A. Scott and J. Dennis Lawrence, "Testing Existing Software For Safety-Related Applications", Fission Energy and Systems Safety Program, Lawrence Livermore National Laboratory, UCLR-ID-117224, Revision 7.1, December 1994.
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