esa unclassified – for official use sois eds interoperability f. torelli ccsds spring meeting 2015...

ESA UNCLASSIFIED – For Official Use

SOIS EDS Interoperability

F. TorelliCCSDS Spring Meeting 201523/03/2015



First step of the interoperability tests



Interoperability tests objectives

1. Validation of the EDS schema by means of independent users

2. Validation of all the features specified in the EDS schema blue book

a. Validation of the DoT ontology by means of independent users

b. Validation of all the features specified in the DoT ontology blue book



Recap from previous meetings

1. Not all the permutations foreseen by EDS schema need to be tested. 2. Not real devices to be used, because we want them to be open and

focusing on the actual features to be tested. 3. The interface spec for the artificial devices should be a suite of specs

to allow distribution of the work and to have an efficient management of the device interface complexity.

4. It is out of scope to validate the EDS schema in describing the right proprieties of the devices, while it is in scope to verify that two users understand the same from EDS schema and interface specs.

5. The questionnaire discussed in teleconference is a prerequisite for interoperability, because it will allow to shape the features of the EDS schema (completeness and usefulness).

See also [Sois-app] Spring 2014 Meeting Material emails 11-29/4/2014



Definition of artificial device interface specifications to exercise all the features of EDS schema to be validated.

Artificial device interface specifications are, practically, the interoperability test specification.

Device X SEDS

1st step of the interoperability tests

Artificial Device ICD XArtificial Device

ICD XArtificial Device ICD X

EDS Schema

Device X SEDSDevice X

SEDS

Interoperability tests



Exercise the generated code

• EDS obtained from the artificial device interface spec are input to the code generation toolchain

• The generated code from the toolchain is tested to verify the correctness of interfaces and protocols

• Tests could also use just one or two C&DA layers

DVS

DAS

Subnetwork

User Application

Device

Command Message Answer

Test Source Code

Test Source Code



Artificial devices and EDS schema



EDS schema requirements 1/2

Service Feature Reference Status

EDS syntax 3.2.1-3.2.6, 4.2 M

Subnetwork (at least one of SpaceWire, MilBus, CanBus, or TTE)

3.3.15-3.3.25, ?, ?, ? M

Namespaces 3.4, 4.3.1, 4.3.2 M

Interfaces 3.5-3.12, 4.3.3, 4.3.4, 4.3.12-4.3.14 M

Implementations 3.3.14, 3.13, 3.14, 4.3.5, 4.3.10, 4.3.11, 4.3.15-4.3.19, 4.4, 4.5 O



EDS schema requirements 2/2

Service Feature Reference StatusXInclude 3.2.2-3.2.3 MCustom Ontology 3.2.7 OGeneric Types 3.3.6-3.3.13, 4.3.6-4.3.9 O

Subcomponents and Connectors 3.3.14, 4.3.5, 4.3.10, 4.3.11 O

SpaceWire 3.3.16-3.3.25 OMilBus ? OCanBus ? OTime-Triggered Ethernet ? OMetadata 3.3.26-3.3.33 MData Types 3.5-3.9, 4.3.3, 4.3.13, 4.3.14 MInterface Types 3.10, 4.3.4 MComponent Types 3.11, 3.12, 4.3.12 MActivities and State Machines 3.13, 3.14, 4.3.15-4.3.19, 4.4, 4.5 O



Artificial device interface specification characteristics

1. Service provided interface towards test upper layer DAS or DVS interface

2. Service required interface towards lower layer stub Subnetwork interface

3. Body of the EDS exercising a consistent subset of EDS schema requirements.



Way forward



Way forward

1. Artificial device interface specification template?2. How to split the work?3. Next steps for the interoperability?

esa unclassified – for official use sois eds interoperability f. torelli ccsds spring meeting 2015...

Documents