Software Verification

Introduction

Testing and Verification

Development will primarily be conducted on a development unit, with secondary development on the CDH models. The exception to this rule is when development cannot take place due to hardware differences, in which case as much of the logic should be written/tested as possible.

The following can be developed and tested with the development unit with no additional hardware:

1. CAN communication and CAN firmware.

2. Command and data handling with respect to CAN communication.

3. Radio communication (requires the use of the communications board).

4. Command and data handling with respect to Radio communication.

5. Data handling with respect to the external Flash. This is possible because the Flash interface used for the development unit will be identical to the interface used for the CDH models.

6. Any other application logic that is independent of hardware.

The following can be developed, tested, and verified with the CDH models, or with the development unit (so long as there is additional hardware):

1. Anything that can be developed and tested with the development unit.

2. Functionality involving watchdog timers.

3. Functionality involving the RTC.

Test Apparatus

CAN and radio communication can be tested using a test apparatus. The test apparatus should be designed to spoof the inter-subsystem communication as accurately as possible. There may be additional CAN messages added to exercise application logic (e.g. a CAN message to exercise a ground station command).

All the possible measurements and commands should be documented, and then tested one by one on all platforms.

Verification Activities

Test Plan