0. The backplane baddies shall not consider fuckery outside the avionics bay
| Number | Requirement | Rationale |
|---|
| The backplane shall provide a method of communication between all modules | Adding simple boards to the system should be relatively easy |
| Each module shall be |
self-sufficientAdding simple boards to the system should be relatively easy| able to function independently to the best of its ability | Allows computer to be in modular configurations depending on flight needs |
| The backplane shall route power to every board | Boards need power |
| The assembly ( |
including batteries| backplane and at least four modules) shall be able to fit |
on single sledTwo connected sleds are annoying | Each module should be the same size| 3U cubesat | Extra points for 3U cubesat payload |
| The backplane architecture shall define a standard width and height for each module | Easier to mechanically integrate |
| The backplane shall survive |
New MexicoAvionics should work where we want to use it | The backplane shall survive launch and Launch | Avionics should work where we want to use it | The backplane shall (tolerate module failures/isolate faults) | Reducing system-wide failure chance | | launch operations | A flight computer should be able to survive a flight |
| Modules shall be individually mechanically accessible | Speeds up prototyping |
, , backplane shall be achievable given existing team bandwidthWe can only build what we can build (still worth stating) | The backplane shall be manufacturable with RIT resources | We can only rely on RIT resources | The replaceable| interchangeable | Speeds up prototyping |
, , repair| /repair |
| Each module should limit the amount of external I/O | Prevents a rats nest in the avionics bay/payload |