Reformatted Feedback
Â
Report Section | Feedback | What to do: |
---|---|---|
Structure/Organization | ||
Formatting |
| FOLLOW CONOPS suggested format |
| include acronyms section (are we allowed an appendix?) | |
| Â | |
| pay attention to figures in editing process! | |
| be sure to include a lot of diagrams… | |
References |
| LIST MORE REFERENCES |
Grammar |
| grammarly. |
System Level Testing | ||
 |
| include risk matrix |
| talk about general tests during dev process | |
| have each subteam lead talk about their respective testing processes | |
Novel Approach to mission requirements | ||
 |
| HIGHLIGHT NOVEL APPROACH |
| ||
| Â | |
| Pretty much, just brag about everything we think is novel or really just cool about the system. | |
| Â | |
Description of system level safety issues | ||
 |
| Â |
| Â | |
| Be sure to mention safety of PEOPLE et cetera within certain situations, not just technical ones. | |
| ||
Identification of single point failure modes | ||
 |
| Figure out all possibilities for SPFM and talk about them. IN DEPTH. |
| ||
| ||
| ||
List of milestones | ||
 |
| Â |
Schedule | ||
 |
| Make sure chart is readable.. |
| ||
| ||
Project Budget | ||
 |
| Be realistic!! They don’t care too much about having a low budget… apparently. |
| ||
| ||
Alternate Solutions | ||
 |
| Â |
| Â | |
| Be sure to consider more REASONS as to why a particular solution was chosen | |
| Â | |
Features & Capabilities | ||
 |
| leads should all contribute. The features and capabilities should flow through each subteam so that the judges get the bigger picture. |
| Â | |
| Â | |
| Â | |
Communications and Control | ||
 |
| INCLUDE TEAM COMMUNICATION |
BVLOS Strategy |
| Â |
| Â | |
| Â | |
| Â | |
Pickup/Drop-off Methodology | ||
 |
| Â |
| Â | |
| Â | |
Navigation Strategy | ||
 |
| Include Diagram |
| Discuss how specific to task | |
| Highlight novelty. | |
| mention pilot in emergency | |
| Explain how the system works. IN DEPTH. | |
Safety | ||
 |
| Just … write more about safety. Consider more cases where safety need to be talked about. |
| ||
| ||
| ||
| ||
Project Risk Mitigation Plan | ||
 |
| Consider risks and mitigation plan over all subteams. |
|
Â