| | 1 | = Goals for the 2017 Systems Engineering Team |
| | 2 | These were the goals for systems engineering as established in the preseason before the 2017 season. |
| | 3 | 1. Development functional requirements of subsystems from the high-level strategy requirements. |
| | 4 | 2. Develop a system for verification/validation of system requirements. |
| | 5 | 3. Research and determine tools and techniques of the systems engineering trade for use in the build season: |
| | 6 | * power/weight/cost budgets |
| | 7 | * systems requirements (see 2.) |
| | 8 | * physical/mechanical allocation |
| | 9 | * inter subteam integration (horizontal integration) |
| | 10 | 4. Create practical timeline of the build season with milestones. |
| | 11 | 5. Review systems engineering and integration (as well as testing) strategies and best practices of at least 10 top teams. |
| | 12 | 6. Research/review industry systems engineering best practices. |
| | 13 | * risk analysis/risk matrix/risk mitigation |
| | 14 | * compliance matrix |
| | 15 | * Quality Function Deployment matrix |
| | 16 | 7. Practice use of industry-standard tools and methods. |
| | 17 | 8. Create comprehensive documentation, sharable with other teams. |
