Case: Finding Hidden Bugs With T-VEC Solutions

Implementation

Apply T-VEC automated solution to model requirements, generate tests, and execute tests

Lockheed Martin supplied MPL touchdown landing requirements and associated code module.

  • T-VEC engineer modeled the single page of textual MPL touchdown landing requirements, without knowledge of the code failure, and with no other information and support from Lockheed Martin.
  • Engineer purposely did not look at the code so that resulting tests were derived strictly from the textual requirements.
  • T-VEC was used to generate tests from the modeled requirements.
  • Test driver template created by analyzing the interfaces to the MPL touchdown landing code module to simulate multiple calls to the code much like that of the real-time multi-tasking executive of the TDM software.
  • Test drivers and harness generated by T-VEC.
  • Test drivers executed against the code.
  • T-VEC test results report generated comparing expected output to actual output.
  • The Problem
    Undiscovered code bug is likely cause of Mars Polar Lander crashs
  • The Approach
    Modeled textual requirements, generated tests and test drivers, and executed test
  • Implementation
    Apply T-VEC automated solution to model requirements, generate tests, and execute tests
  • Results
    T-VEC solutions identified code bug in fewer than 12 hours that is probable cause of failure