You are here

A TESTING METHODOLOGY FOR HIGH RELIABILITY SOFTWARE

Award Information
Agency: National Aeronautics and Space Administration
Branch: N/A
Contract: N/A
Agency Tracking Number: 16961
Amount: $495,200.00
Phase: Phase II
Program: SBIR
Solicitation Topic Code: N/A
Solicitation Number: N/A
Timeline
Solicitation Year: N/A
Award Year: 1992
Award Start Date (Proposal Award Date): N/A
Award End Date (Contract End Date): N/A
Small Business Information
55 Wheeler St
Cambridge, MA 02138
United States
DUNS: N/A
HUBZone Owned: No
Woman Owned: No
Socially and Economically Disadvantaged: No
Principal Investigator
 () -
Business Contact
Phone: () -
Research Institution
N/A
Abstract

SINCE SOFTWARE IS A CRUCIAL COMPONENT OF CURRENT ENGINEERINGSYSTEMS, HIGH-RELIABILITY SOFTWARE IS REQUIRED FOR NASA PROGRAMS. THE USE OF FORMAL SOFTWARE ENGINEERING PRINCIPLESAND OF CASE TOOLS HAVE YIELDED ONLY MODEST PROGRESS IN THIS AREA. THE USE OF REDUNDANT SOFTWARE COMPONENTS IS NOT SUFFICIENTLY DEVELOPED TO PROVIDE AN EFFICIENT ALTERNATIVE. A TESTING METHODOLOGY WILL BE DEVELOPED THAT WILL PRODUCE HIGH RELIABILITY SOFTWARE BY USING INTERACTIVE, PROOF-BASED CORRECTNESS TESTING, ENFORCED TESTING DIVERSITY, AND KNOWLEDGE-BASED TESTING. THIS METHODOLOGY IS APPLICABLE TO PARALLEL SOFTWARE AS WELL. RECENT REDUNDANT SOFTWARE EXPERIMENTS INDICATE THAT NO SINGLE TESTING STRATEGY PRODUCES SUFFICIENT TEST CASES TO ENSURE HIGH RELIABILITY. HENCE, A COMBINATION OF TESTING STRATEGIES IS REQUIRED FOR HIGH RELIABILITY. EXPERIMENTAL RESEARCH ALSO INDICATES THAT DYNAMIC TESTING IS INEFFICIENT IN DETECTING FAILURES THAT OCCUR INFREQUENTLY. KNOWLEDGE-BASED STATIC TESTING IS MORE EFFICIENT. ORACLES FOR ASSERTING CORRECTNESS OF HIGH-RELIABILITY SOFTWARE ARE DIFFICULT TO BUILD SINCE THEIRRELIABILITY MUST EXCEED THE SOFTWARE. THE FIRM HAS DEVELOPED A GENERALIZATION OF INTERACTIVE PROOFS WHICH SOLVE THIS PROBLEM. IN THE FUTURE, PARALLEL ARCHITECTURES WILL BE USED FOR CRITICAL SOFTWARE APPLICATIONS. SINCE SOFTWARE IS A CRUCIAL COMPONENT OF CURRENT ENGINEERINGSYSTEMS, HIGH-RELIABILITY SOFTWARE IS REQUIRED FOR NASA PROGRAMS. THE USE OF FORMAL SOFTWARE ENGINEERING PRINCIPLESAND OF CASE TOOLS HAVE YIELDED ONLY MODEST PROGRESS IN THIS AREA. THE USE OF REDUNDANT SOFTWARE COMPONENTS IS NOT SUFFICIENTLY DEVELOPED TO PROVIDE AN EFFICIENT ALTERNATIVE. A TESTING METHODOLOGY WILL BE DEVELOPED THAT WILL PRODUCE HIGH RELIABILITY SOFTWARE BY USING INTERACTIVE, PROOF-BASED CORRECTNESS TESTING, ENFORCED TESTING DIVERSITY, AND KNOWLEDGE-BASED TESTING. THIS METHODOLOGY IS APPLICABLE TO PARALLEL SOFTWARE AS WELL. RECENT REDUNDANT SOFTWARE EXPERIMENTS INDICATE THAT NO SINGLE TESTING STRATEGY PRODUCES SUFFICIENT TEST CASES TO ENSURE HIGH RELIABILITY. HENCE, A COMBINATION OF TESTING STRATEGIES IS REQUIRED FOR HIGH RELIABILITY. EXPERIMENTAL RESEARCH ALSO INDICATES THAT DYNAMIC TESTING IS INEFFICIENT IN DETECTING FAILURES THAT OCCUR INFREQUENTLY. KNOWLEDGE-BASED STATIC TESTING IS MORE EFFICIENT. ORACLES FOR ASSERTING CORRECTNESS OF HIGH-RELIABILITY SOFTWARE ARE DIFFICULT TO BUILD SINCE THEIRRELIABILITY MUST EXCEED THE SOFTWARE. THE FIRM HAS DEVELOPED A GENERALIZATION OF INTERACTIVE PROOFS WHICH SOLVE THIS PROBLEM. IN THE FUTURE, PARALLEL ARCHITECTURES WILL BE USED FOR CRITICAL SOFTWARE APPLICATIONS.

* Information listed above is at the time of submission. *

US Flag An Official Website of the United States Government