The road to the first E2E tests Chris Watson SOWG#9, ESAC 25/Jan/2017

Overview What the first E2E tests are. How we get to the point where we can run one in April 2018 In terms of interfaces In terms of planning concept

First E2E tests What are the first E2E tests? “End-to-end” tests are End-to-end in the sense that, as far as possible, uplink products go all the way from ITs-SOC-MOC and (in principal) downlink products v.v. Scenario tests. We are simulating real operations in a realistic way (as far as possible) They are validation rather than verification. The first E2E tests are 1) IS-only E2E 2) Remote-sensing check-out window E2E Might be possible to merge the two tests, but at the moment they are separate. Both planned for L-6 months (April 2018) Both focussed on Cruise phase These E2E tests are big, semi-realistic, scenario tests involving multiple parties and multiple interfaces. They cannot possibly succeed without preparatory / lower-level tests. This presentation lays out the steps we want to take to be ready for these first E2E tests in ~Apr next year

E2E test schematic

First E2E tests schematic

Differences / limitations on first E2E tests pt1 In our opinion Mission-level planning equivalent for CP can be planned by SOC RSCW placement Pass planning RS-instruments have already seen a couple of crude CP plans for RSCWs from SOC LTP still exists, albeit simplified Not SOOP-orientated for RS-instruments at least Needed to coordinate e.g. when shared calibration pointing mosaics will run that data volumes can be supported

Differences / limitations on first E2E tests pt2 Simulator time The E2E command (input) products are supposed to cover one – several weeks We are probably not going to execute a several week E2E test all the way through We will need to intelligent about the period we plan, and the subset we execute Open question of whether E2E runs like a batch job (all inputs submitted in advance), or (more realistically) we run over an STP boundary, and allow STPn+1 commanding submission whilst STPn TM flow is ongoing Zero simulator time is actually a possibility => manual inspection and zero TM Science data content MOC simulator can provide science TM volume, but not meaningful content nor APID mix, packet cadence etc. Means that we can exercise the broad retrieval of science “data” but not process that TM

Differences / limitations on first E2E tests pt3 No Selective Since Cruise Phase No i-VSTP No TAC No PDORs/MDORs Auxiliary data Spacecraft clock kernels TBC which other aux data produced

First E2E tests schematic

Preparation - interfaces SOC concept of interface maturity 1) Compatibility test Representative ICD-compliant file, sent by any convenient method. Does not need to be generated by the “real” SW. Normally “example file” 2) Integration test As before, but created by the real SW (can be an early release thereof) and sent via the flight mechanism. 3) Validation test Active use of the product in some wider scenario-based test This is the E2E test in this case.

Preparation – validating the planning concept Besides the individual interfaces, we also want to exercise the planning cycle flow. I already touched on this Mission-level equivalent can be planned by SOC RSCW placement Pass planning LTP still exists, albeit simplified Not SOOP-orientated Needed e.g. to coordinate when instruments will Additionally for these first E2E tests, we propose to skip MTP. i.e. go directly from LTP->STP => Cruise phase SOWG LTP planning exercise in SOWG#10, July 2017. To feed into E2E test.

Preparation schedule affecting Instrument Teams – Current status Date Item May 2016 EFECS TMC Compatibility test TM (EDDS) Generic EDDS TM example as part of LL-pipeline development Approx half of ITs have also received EDDS TM from SFT/FFT Jan 2017 TC (EDDS) Example files on SOC-Public Instrument teams inspection to be formalised Trajectory files Trajectory files have been available for a long time, but have not been formally exchanged. For instruments that will actively use the trajectory in their planning, do we need to organise formal compatibility, integration test?...

Preparation schedule affecting Instrument Teams - future Date Item Feb-Mar 2017 File-transfer ITs<->SOC Interface tests ??Feb 2017 IOR Compatibility test ITs write a example IOR by any means July 2017 SOWG#10 LTP planning Oct 2017 EFECS/TMC Integration test SOC delivery of EFECS/TMC to be used for first E2E test ??Oct 2017 ITs write IORs with proper SW and deliver via file-transfer Dec 2017 EDDS Test Integration Test (for TM, TC) Jan 2018 Deliver final IORs to SOC Mar 2018 SOC deliver final PORs to ESOC

Current biggest single concern = procedures