...
| 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 easyable 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 batteriesbackplane and at least four modules) shall be able to fit on within a single sled | Two connected sleds are annoying | Each module should be the same size3U 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 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 | launch operations | A flight computer should be able to survive a flight | |
| Modules shall be individually mechanically 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 replaceableinterchangeable | Speeds up prototyping/troubleshooting/repair | |||||||
| Each module should limit the amount of external I/O | Prevents a rats nest in the avionics bay/payload |