Nov 16, 2026 | 715 words | 7 min read
20.3. Milestone 5 - Final Technical Report (Team)#
At a Glance
What you will do: Complete your Design Project Technical Report. The report is addressed to the client and documents the controller your team delivers.
What you will submit: One completed Technical Report (PDF) per team.
For this milestone, you finish the
Design Project Technical Report
you have been working on since Milestone 1. The sections below are its closing
pieces: your Executive Summary and the Final Design sections written for
the client. Address the report to Dr. Okafor and assume the reader is an engineer
who never met your team and was not in this course.
Mission Control will judge the report on three professional qualities.
Usability: Mission Control engineers can run, score, and operate your controller using only this report.
Validity: Your claims are supported by data, with the evidence shown.
Modifiability: An engineer can adapt your controller, for example, to a different crop or a longer mission, because the report states why every critical value is what it is.
20.3.1. Required Sections#
For this milestone, draft and revise the following sections:
Report section |
What this milestone requires |
|---|---|
Title Block |
The final report title, team name and number, team members, date, and client name. |
I. Executive Summary |
New this milestone. One page covering what you delivered, your headline acceptance-test results, and why the controller is worth deploying. |
II. Team Member Roles |
Revise: finalize the list of each member and what they owned. |
III. Problem Scoping |
Revise: replace your first-draft list with the design criteria and constraints your team built to. |
IX. Overview of Final Design |
Revise the sections a-b drafted in M4 (if necessary) and complete subsections c-e. |
IX.c Novel Aspects of the Solution |
What your design does that a standard solution would not. |
IX.d Trade-off Decisions and Limitations |
Your requirements disposition (met, partially met, or formally revised), your responsible-use notes, and how you handled humidity. See VIII, Table 15 for your assumptions and their evidence. |
IX.e Lessons Learned |
Reflect on your team’s process and skills: its strengths, what you would change, and how your thinking developed. |
X. References |
Finalize. Choose APA or MLA and use it consistently for in-text citations and reference entries. |
XI. Appendices |
Complete the AI Use Log. |
20.3.2. Submission#
Submit one PDF per team, named
TP5_design_project_final_report_team_#.pdf, to 20.3 Milestone 5 - Final Technical Report (Team) in Gradescope as a group before the deadline on the Course Schedule.Late team submissions are NOT accepted.
Learning Objectives
- PC01:
Written Communication Standards - Use professional tone, clear sentence structure, and correct spelling and grammar in all written work.
- PC02:
Communicating Results from Analysis - Clearly state conclusions or results derived from code, models, or data analysis.
- PC03:
Captioning Visuals - Include professional captions for all figures, tables, and plots that describe what is shown and why it is relevant.
- PC04:
Visual Communication of Engineering Contexts - Create visuals that clearly communicate engineering data, models, or concepts to a technical audience and support claims or conclusions.
- SQ03:
Trade-offs and Limitations - Explain trade-offs and limitations in the final solution.
- SQ04:
Value Proposition - Present a clear value proposition highlighting benefits and novelty.
- EC01:
Consider Context, Safety, and Uncertainty - Justify engineering decisions or recommendations by considering cultural, economic, environmental, safety, and uncertainty-related factors.
- EC02:
Recognize Limits, Trade-offs, and Confidence - Recognize limitations, trade-offs, and uncertainty in engineering work and communicate appropriate levels of confidence in conclusions.
- EC03:
Make Honest and Responsible Recommendations - Make recommendations that are honest, responsible, and consistent with evidence, while acknowledging broader impacts and professional responsibility.
- IL03:
Supporting Claims with Evidence - Use data, examples, or published sources appropriately to support claims, assumptions, or recommendations.
- IL05:
Reference List and Source Documentation - Provide a complete and properly formatted reference list for all external sources used.
- AI05:
Communicate clearly and effectively about AI usage and the choices surrounding it in a given field.
- PC05:
Meeting Assignment Expectations - Fully complete all parts of each assignment according to provided instructions.
- TM02:
Document Contributions - Provide clear evidence of individual contributions to the team’s work, including technical, written, or supportive tasks.
- PS05:
Problem Revision - Revise the problem statement based on new evidence or insights.
- EB03:
Data-Supported Justification - Justify decisions or comparisons using explicit reference to data.
- EB05:
Iterative Improvement - Present findings from iterative testing or optimization efforts.
- PA01:
Identify Strengths in Process - Identify effective strategies, behaviors, or decisions used during the problem-solving or design process.
- PA02:
Identify Limitations in Process - Identify limitations, challenges, or inefficiencies in the problem-solving or design approach.
- PA03:
Plan for Process Improvement - Identify concrete behaviors or strategies to improve future problem-solving or design efforts.
- IL04:
In-Text Citations - Include appropriate in-text citations to indicate the source of information, data, or ideas.