---
# System prepended metadata

title: Flight software requirements
tags: [master, fs]

---

###### tags: `master` `fs`
# Flight software requirements
[TOC]
## Flight Software
:::info
 Inspired by Phoenix Flight Software Cubesat
:::

| ID | Requirement | Rationale | Parent Requirement | Verification |
| ------ | -------- | -------- | -------- | -------- |
| FS1     | Read Housekeeping telemetry from other subsystems   | Allows monitoring and study of cubesat health and/or unexpected behaviour      |           |     Testing|
|FS2|FS must be able to communicate with ground station| Essential | | Testing|
|FS3| FS shall issue commands according to schedules uplinked by the CHESS team| A schedule allows more predictable execution of mission objectives and study of unexoected behavior ||Testing|
| FS4 | FS need to have the Time in UTC for many apsect of the software like TC/TM |Scientifique aspect||Testing|
|FS5|FW shall collect and maintain datas| Not sure, payload maybe need informations for metadata||Testing|
|FS6| FW shall be able to receive commands from Ground Software||Retrieval of science data|Testing|
|FS7| Shall tolerate being powered off at any time iwhtout loss of ciritcal data| If the OBC must be shut down or reset, the FW must not lose all telemetry data ||Testing|
|FS8| Manage reset | must be capable of manage a reset of configuration of subsystems||Testing|
|FS9|FS must be capable of commanding the the ADCS to track a specified target | If payload need position or to be at gsp coordinates to perform||Testing|
|FS10|FS must be capable of commanding the EPS to power individual hardware upon command|  EPS should be able to trun off/on hardware upon command to maintain battery levels||Testing|
|FS11|FS must be capable to manage all transmission from the communication hardware|||Testing|
|FS12|FS must manage payloads|The base of the mission||Testing|
|FS13|Fs must be capable of update internal time (maybe with the gps) |Need to maintain utc time to allow operations schedules to be planned out and synced with sat|||

------------------------------------------------------------------

:::info
 Inspired by Phoenix Flight Software Cubesat requirements matrix
:::


| ID | Title | Requirement | Rational |verification method| Verification Method Description |
| -------- | -------- | -------- |------|----|---|-----|
| FS1     | Storage     | FS must store somme telemetry, log, and payload data in memory     |Basic storage requirement necessary to complete mission objectives| Test| Payload data + Demo|
|FS2|Payload data format|FS must record and document science data captured by the payload after performed| need to hace data and metadata for science purpose|Test|Payload data + Demo|
|FS3|Power control|FS must be capable of commanding the EPS to enable or disable power to individual hardware upon commande|Maintain battery level|Test| Demo|
|FS4|Health Beacon|FS must implement a health beacon|The health beacon must provide constant health data dfor monitoring during mission operation Health must be access quickly|Test||
|FS5|Short Telemetry Dump|FS must be capable ot transmitting all telemetry gathered upond commande| Missions controle should be able to trend data wihtout having to requet a full telemetry file|Test||
|FS6| FS Transmission halt| Fs must be capable of halting all transmitted messages if the sat is orderer to cease RF transmission| power requirement|Test| Test with power supplie|
|||||||




## Test Software
| ID | Requirement | Rationale | Parent Requirement | Verification |
| ------ | -------- | -------- | -------- | -------- |