The following outlines the design constraints and must-haves for the control system for our satellite. Requirements are primarily based upon requirements specified by the Canadian Satellite Design Challenge (CSDC). Supplemental requirements on the control systems are based on needs of the secondary payload (QEYnet payload at the time of writing) and other subsystems present on the satellite.
<aside> 📢 To be consistent with aerospace systems engineering (and the CSDC competition itself), the terminology SHALL is used to designate a mandatory requirement and SHOULD designates an optional but desired requirement.
</aside>
GNC has classified requirements using our own internal scheme and traceability to parent requirements are maintained if it exists (i.e. links to external sources or other pages on the notion). Other requirements without traceability are justified where appropriate according to calculations or industry standards. Design documents and other considerations shall reference these requirements. Such documents satisfying one or more requirements should be referenced below.
<aside> 💡 Justifications made based on simplistic calculations will use a safety factor (SF) to account for uncertainty. The SF used in these requirements will be 1.4 and is based on the ultimate factor of safety used in structural analyses on spacecraft (https://ntrs.nasa.gov/api/citations/20150003482/downloads/20150003482.pdf).
</aside>
Other requirements may be notifications of faults, current progress on alignment, etc.