| 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-sufficient | Adding simple boards to the system should be relatively easy | |
| The backplane shall route power to every board | Boards need power | |
| The assembly (including batteries) shall fit on a single sled | Two connected sleds are annoying | |
| Each module should be the same size | Easier to mechanically integrate | |
| The backplane shall survive New Mexico | Avionics 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) | Improves reliability | |
| Modules shall be individually accessible | Speeds up prototyping/troubleshooting/repair | |
| The backplane shall be achievable given existing team bandwidth | We can only build what we can build | |
| The backplane shall be manufacturable with RIT resources | We can only rely on RIT resources | |
| The modules shall be drop-in replaceable | Speeds up prototyping/troubleshooting/repair |
General
Content
Integrations