# Research Infusion 2008

# Potential Tool and Technology Candidate

**[Contact Information]{.underline}**

Name of Tool/Technology: STOL (Systems Test and Operations Language)
Analysis Tool

Name of Technology Provider: MATRIC

Primary Point of Contact (PPC): Dr Jack Smith

PPC Phone No.: (800) 611-2296, x814

PPC e-mail: <Jack.Smith@MatricResearch.com>

Alternate Contact Name (APC): Jason Blackhurst

APC Phone No.: (800) 611-2296

APC e-mail: <Jason.Blackhurst@MatricResearch.com>

Technology Provider Website:
[http://www.matricresearch.com](http://www.matricresearch.com/)

Technology Provider Address: 3200/3300 Kanawha Turnpike Building 701

> South Charleston, WV 25303 Tel. (800) 611-2296

**[Tool/Technology Details]{.underline}**

Description of Tool/Technology: Automated tool to help analyze STOL test
scripts and their

> associated logs for test coverage.

Commercial or Research Derived: Research

Associated Program: SARP

Potential Benefits: Improve the quality and timeliness of test
verification of STOL-

> based systems. Ongoing standards activities could help unify,
>
> advance, and further broaden the use of a common STOL-like language in
> future NASA projects.

Supported Platforms: Any platform supporting Eclipse, Java and Antlr.

Required Inputs: STOL scripts and certain (stamped) associated log
files.

Outputs Produced: Visual displays and annotations only, no printable
reports or

graphics. Internal model representations are exportable as XMI.

**[Maturity Level]{.underline}**

Applied to Real Problems? Yes No

If Yes, Level of Success Achieved: Being applied to SDO. No feedback
received yet.

Already in Use within NASA? Yes No

If Yes, at what center(s): NASA IV&V, GSFC (both for SDO)

**[Support]{.underline}**

User/Ref. Documentation Available: Yes

Phone Support Available: Yes

Is Tool/Technology Developer willing to support infusion effort? Yes No

**[Licensing]{.underline}**

Is Tool/Technology Provider willing to provide Evaluation Copy for
extended period of time? Yes No

**[Other Information]{.underline}**

Infusion partners would be encouraged to participate in an Open Source
style web-based feature/bug tracking system and discussion forums.

References to relevant technical papers and URL for this product or its
parent:

<http://sarpresults.ivv.nasa.gov/ViewResearch/112.jsp>

[SAS 2007 Technical Presentation:
<http://sarpresults.ivv.nasa.gov/DownloadFile/112/12/SAS_07_Tech_Pres_STOL_Smith_J.ppt>]{.mark}

[STOLENID Product:
<http://srvr1.matricresearch.com/stolenid/STOLENID_1.0.10.v20070916.zip>]{.mark}

[Phase I Findings Report: (upon request from
<Jack.Smith@matricresearch.com>)]{.mark}

Research product objective: (Select **all** that apply)

Tool

Method or Technique

Process

Other (Please specify)

     

Description of research product objective:

[Automated tool to help analyze STOL test scripts and their associated
logs for test coverage.]{.mark}

What **differentiates the research product** from related research and
from commercially-available products?

[No other tool exists that understands any variant of the STOL language
or accompanying log files]{.mark}

Target application domain type:

Autonomous Systems

AI other than Robotics

Business Automated Data Processing

Collaboration

Command and Control

Communications

Diagnosis

Multi-Agent

Multi-Threaded

Navigation / Guidance

Real-Time

Robotics

Scientific

Security

Software Development Tools (Tools for building tools)

Other (Specify)

[Any of the above that involve STOL test scripts]{.mark}

Target software engineering areas:

Project Management including tool selection

Measurement of software artifacts

Requirements

Specification

Design

Implementation

Maintenance

Process Management

Configuration Management

QA

Safety

V & V

Other (Specify)

[Testing]{.mark}

What are the **key characteristics of a target application that
determine the applicability** (or not) of the research?\
[Works only on ASIST STOL scripts and stamped log files]{.mark}

What does a **software development project** need to do to make use of
the research product?

[Use ASIST STOL scripts and stamped log files]{.mark}

What do you see as the next steps **that you need to take to support
tech infusion of the research** into practice at NASA?

-   [Extend to other variants of STOL (e.g. EPOCH, CSTOL)]{.mark}

-   [Extend to non-stamped log files (based on user-definable
    heuristics)]{.mark}

-   [Extend to the script development and simulated testing
    stages]{.mark}

-   [Make the grammars, parsers and integrated model more complete
    (compiler grade)]{.mark}

-   [Extend model to include test specifications, provide an import
    facility, and automate much of the test coverage analysis]{.mark}

What kind of support does a software development project need to make
use of the research?

[Participation in web-based feature/bug tracking system and discussion
forums; telephone and e-mail support as needed]{.mark}

What do you think is a viable tech infusion strategy for users within
NASA?

[Open Source plus fee-based support (subject to change by MATRIC
management)]{.mark}