 |
||
|
Advanced Search |
||
|
|||||
|
Test Analysis < Verification & Validation < Results Home
|
|
Click here to complete a short survey. The results of this survey will be used to help us improve the research program and this website.
Click here to view research projects that had new research results added in the last 90 days.
|
| Injecting Faults for Software Error Evaluation | |
| Point of Contact |
Kalynnda Berens Kalynnda.M.Berens@grc.nasa.gov |
| Dates | October 2000 - September 2003 |
| Problem | Complex software is an integral part of many NASA projects. Mission assurance requires that the software must be fault/failure tolerant. How can this be verified independently in a system where not all of the software source code may be accessible? What new techniques can be used by IV&V and assurance to assure the safety and robustness of NASA software? |
| Objective | Answer these questions: Can Software Fault Injection be used by an Independent V&V engineer. Are the errors and problems found of sufficient severity or abundance, and are the costs of applying this technique low enough, that SFI would be a useful and cost-effective technique for NASA? Is SFI a good tool for safer software? |
| Results |
Fault Injection Test Plan.doc SFI CSIP metrics and scope.doc Software Fault Injection Test Document.doc Injecting Faults for Error Evaluation SAS '02 Presentation.ppt FCF Software Fault Injection Test Plan - CANbus processors.doc Paper on what was learned in applying software fault injection for this project..doc |
| Keywords | mission assurance, fault/failure tolerant, software fault injection, mission critical, Combustion Module-2, COTS, injecting faults, Microgravity Droplet Combustion Application, prototype test plan, real-world anomalies, software error evaluation, independent verification, black-box |
| Categories |
Code Analysis Design Analysis Test Analysis Traceability Analysis |
|
| |
|
Curator: Josh Stonestreet NASA Official: Lisa Montgomery |
|
NASA Privacy, Security, Notices |