1 / 7

Injecting Faults for Error Evaluation

Injecting Faults for Error Evaluation. NASA Glenn Research Center Kalynnda Berens, SAIC Richard Plastow, SAIC. The Problems:. Unknowns in software systems Acquired software (COTS, open source) Used more often in systems Lack of documentation No or little insight into the software

robertdreed
Télécharger la présentation

Injecting Faults for Error Evaluation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Injecting Faults for Error Evaluation NASA Glenn Research Center Kalynnda Berens, SAIC Richard Plastow, SAIC

  2. The Problems: • Unknowns in software systems • Acquired software (COTS, open source) • Used more often in systems • Lack of documentation • No or little insight into the software • Interfaces to hardware/other systems • Need a way to test and verify the functionality and reliability • Goal: Find errors on the ground…before it flies!

  3. Our approach • Gather system information • Determine interfaces/COTS • What can go wrong? • Common errors • Standards • Requirements • Create test cases • Execute tests (aka Break the System) • Feedback errors to developer (and duck)

  4. Importance and Benefits • Standardized approach to test systems with COTS and hardware interfaces • Roadmap of where to look to determine what to test • In latest pilot project, found 3 critical errors • Software crash with reboot • Invalid telemetry • Incorrect fan speed control

  5. Relevance to NASA • Allows use of COTS with improved reliability and a lower error rate • Can be used with all types of software • Two NASA pilot projects

  6. Accomplishments • Found additional errors in two diverse projects • Projects took our input and fixed the problems • Draft of Fault Injection Methodology document

  7. Next Steps • In-depth case study (ISS flight payload) • Update Fault Injection Methodology document • Record all the details – problems as well as successes • Compare results to other defect detection mechanisms • Written for those who want to try the technique • Release FI Methodology and Case Study

More Related