1. Using Electronic Datasheet for Testing

2. SOIS EDS: Common Interchange Format
Devices
Documentation IRDs, ICDs, Verification reports, etc.
validate
EDS Interchangeable Model of data interfaces
System Design
translate
generate
OBSW SOIS CDAS, …
transform
MCS/EGSE S/C database
SVF/Simulators Data encoding, calibration

3. EDS IN CCSDS Reference Architecture
Device
DSAP
DACP
Arbitrary message exchanges, with timing dependencies
Regular message exchanges
Subnetwork Layer
Calibrated Parameters
Raw Parameters
Arbitrarily Encoded data
Datasheet scope
Subnetwork Implementation
Calibrated Commands
Raw Commands
Application Support Layer
DSAI
DSFI

4. ESA Study Projects SOIS Proof Of Concept (2012)
Adoption of Electronic Data Sheets (2014)
Deploying Plug and Play Avionics (2015)
Simulator IFV (2016)
Un-named GSTP (2017)
Verification of Computer Controlled Systems (2015)

5. SEDS Reference Tooling
Tooling Status
Authoring
Datasheet Validation
Document Generation
SEDS Reference Tooling
TASTE
SEDS XML Schema
OBSW Code Generation
NASA
CFE

6. Datasheet: example.xml

7. Run Commands: java -jar SedsTooling.jar docgen
Generate HTML Documentation for example datasheet
java -jar SedsTooling.jar docgen
test-data/xml/example.xml
--output-dir example_html --level ALL
Generate HTML Index and Component Diagram for example datasheet
java -jar SedsTooling.jar docgen
test-data/xml/example.xml
--output-dir example_html --level INDEX

8. PDU Detail from example.xml

9. Behavioral Model Detail

10. Artificial test data: example.raw
#Telemetry2Type aa
#TelemetryEventType
#Illegal TelemetryEventType

11. Run Command: java -jar SedsTooling.jar validate
Statically validate the datasheet against schema and additional rules from 876x0.
java -jar SedsTooling.jar validate
test-classes/xml/example.xml
Verify correctness of datasheet against sample data
java -jar SedsTooling.jar verify
test-classes/xml/example.xml --data-encoding HEX_BYTE test-data test-classes/test_logs/example.raw
--output-dir example_html

12. Verification Report: Overview

13. Verification Report: Subnetwork Coverage

14. Verification Report: Low level packet log

15. Verification Report: Behavioral Model Coverage

16. Real World Example: Jena Star Tracker
No device-specific information ‘baked into’ the tool; everything is in the EDS.
Datasheet is 7600 lines of xml, covering 80 TC and 32 TM.
Test data (supplied by manufacturer) is 1Mb of raw binary milbus log.
Corresponding low-level html packet log is ~40 Mb of html (split into 20 chunks for readability).
Validation Summary identifies the one error in the file (reported to manufacturer)

17. Real World Example: Verification Report

18. Real World Example: Failed packet

19. Jena Star Tracker in Sentinel Simulator
S2A simulator uses (an earlier revision of) the AS400 Star Tracker.
Trace log of running the standard Star Tracker model regression tests is XXMb.
Corresponding low-level html packet log is ~YY Mb of html (split into ZZ chunks for readability).
Validation Summary identifies TBD
SCISYS Test Front End can run tests online and, using integrated copy of EDS tooling, check for violations in real-time.

20. Demonstrator connected to SIMSAT simulator

21. Test Script Controls Testing Code

22. Test Code Uses EDS RT Library

23. Test Report Generated from Test Runs

24. Recap
Validation and Verification of Device Interfaces is key to early, and hence cheap, problem detection and remediation.
Capturing device interfaces formally allows tools to be used to support that activity.
SOIS EDS Reference Tooling provides a Proof of Concept implementation of such a device testing tool.
Adding EDS support into existing test tools (e.g. simulators, SVF, EGSE, etc.) would allow additional testing capabilities.

25. Simulator IFV ESOC study on how to better test operational simulators.
SCISYS suggestion to use EDS technology wa accepted by the client .
2 relevant work packages:
EDS.S1 generate simulator code from an EDS.
EDS.S2 generate simulator test cases from an EDS

26. Simsat Code Generation

27. Model based Testing

28. Test Case Generation from EDS
Check on the correct operation of the system; a test can be considered as failing if it causes the system to
emit out of range values on an interface
send illegal packets on a bound interface
have a state machine transition to an error state
Generate tests that exercise the behaviour of the system:
range and pairwise combination of legal values to an interface
rejection of all illegal bit-patterns on a bound interface
‘walk’ the state machine, ensuring coverage of all states and transitions by a minimal set of sequences.

29. TFE Test Generation

30. Extract from Generated Test

31. Simulator code
The test case that crashes the simulator is one of the parameter sets for tcCHECK_MEMORY , which has three relevant arguments:
memId: BOOTLOADER, APPLICATIONSW, etc. These are the memory areas of the STR, some of which have a 4 byte word size, some 1 byte.
addr: 32 bit base address to start checking  from
amount: number of words (aka SAUs) to check.

32. Test Report Summary

33. Test Log Details