Drivers

Every sensor, actuator, antenna, storage device, and electronic component needs a driver to interface it with the rest of the satellite. This is where they’re all tracked.

Generally, each story represent a set of drivers (ex. power delivery, RF chain), and each driver has 3 main chapters (task levels):

• Base Driver: Relatively simple, being able to talk to device and access some basic information, like a model number or system status
• Core Functionality Driver: Implements at least some of the functionality needed by the subsystem. An appropriate level of detail and features is decided between Firmware members and the stakeholder subsystem(s).
• MVP Driver: Stands for minimum viable product, this driver is able to execute all of the functionality required by the system. It may not be pretty, or responsive enough, but it does the job.
• Additional chapters are added based on specific requirements

One important thing: think twice about rewriting a test case so that it passes. Normalization of deviance is a very serious concern, so make sure you can properly explain why a test case cannot be made to pass, and document that reason. For safety, please seek approval from either Firmware Design Lead or CDH Design Lead for any major test case changes.

Catch-all for driver tasks that don’t fall under any other category.