1 / 9

Verification and Validation of Spacecraft Embedded Software

Verification and Validation of Spacecraft Embedded Software. Presented by Mike Rennie Director of Real-Time Systems DEIMOS Space S.L. (Madrid, Spain). V&V of Spacecraft Embedded SW. Contents. Parent-Child Object Integration Tests Single Thread Integration Tests

delta
Télécharger la présentation

Verification and Validation of Spacecraft Embedded Software

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Verification and Validation of Spacecraft Embedded Software Presented by Mike Rennie Director of Real-Time Systems DEIMOS Space S.L. (Madrid, Spain)

  2. V&V of Spacecraft Embedded SW Contents • Parent-Child Object Integration Tests • Single Thread Integration Tests • Multiple Thread Integration Tests • Software Validation on a Real-Time Test Bench

  3. V&V of Spacecraft Embedded SW Parent-Child Object Integration Tests • Incremental, bottom-up integration of parent-child object hierarchy • Test cases described using UML sequence diagrams, showing the call from test driver to parent to child operations:

  4. V&V of Spacecraft Embedded SW Single Thread Integration Tests • Execution invoked at thread’s root, verifying that it follows the expected path and that all objects and operations along that path collaborated correctly • Each thread tested in isolation of all the other concurrent threads: • Compile modules that are within the call tree of the thread • Stub out all synchronization calls and rendezvous with other threads • Test driver calls visible operations to control the execution • Other objects needed only to compile and link the main programme are also stubbed • Stubs write “trace” messages to standard output • First and last statement of every operation in the SW-under-test is a call to a “marker” function, that gives a trace of the call sequence

  5. V&V of Spacecraft Embedded SW Structure of a Test Programme for Single-Thread Integration

  6. V&V of Spacecraft Embedded SW Call Tree Coverage Analysis for Single-Thread Integration • Intended code coverage depicted by displaying the thread’s call tree with the operations that were intended to be exercised in green, stubs in grey, and untested calls in white:

  7. V&V of Spacecraft Embedded SW Multiple Thread Integration Tests • Objective to verify real-time behaviour of concurrent tasks co-operating together to implement a major functionality. In particular, exchange of data between control flows. Thus, selection of test cases relies on identifying communication paths between threads.

  8. V&V of Spacecraft Embedded SW Communication Path via a Protected Object in HRT-HOOD

  9. V&V of Spacecraft Embedded SW Software Validation on a Real-Time Test Bench • A real-time test bench typically consists of: • Onboard computer (or emulation) • Emulation of the communications (telecommand/telemetry) link between Ground and Spacecraft • Simulation of the environment surrounding the onboard computer (actuators, sensors, space environment) • Hardware-in-the-loop, i.e. real sensors and/or actuators • Example (PACS):

More Related