Week 15 · overview
Week 15: Mapping Products, Reports, and Evidence Limits
This week, you will build mapping product review report for a bounded Drone Engineering scenario. The work stays in classroom-safe analysis, supplied evidence, simulation, planning, and documentation. It does not authorize real flight or unsupervised hardware work.
The engineering problem
A stakeholder wants to use a student-generated map to make a maintenance decision.
The core idea is that the final map is not the end of the evidence chain. It is the start of review. Students will connect that idea to orthomosaics, point clouds, digital surface models, annotations, and reports package data into products for decisions.
Evidence you keep
| Sequence | Evidence artifact |
|---|---|
| Lesson 1 | Mechanism explanation and first evidence table |
| Lesson 2 | Boundary note and no-go or revision condition |
| Lesson 3 | Review-ready decision table |
| Mapping Log | Mapping product review report with limitation statement |
Vocabulary and decision lens
Important language this week includes: system boundary, evidence, limitation, no-go condition, revision rule, and mapping products, reports, and evidence limits.
Decision lens: separate observation claims from measurement claims and require stronger evidence for stronger claims.
Approximate time: 3 to 4 class periods, about 160 to 200 minutes of reading, analysis, evidence writing, and review.