Week 16 · reflection
Week 16 Capstone Concept Log
This log records the design decision, not the amount of work you did.
By the end of Week 16, your team should be able to explain why this mission exists before showing a route, aircraft, or camera.
Record the mission definition
Complete this block using the language from your revised concept brief.
| Field | Final Week 16 entry |
|---|---|
| Stakeholder | |
| Need or decision supported | |
| Required product | |
| Three success criteria | |
| Key operating boundary | |
| Proposed system capabilities | |
| Largest external dependency | |
| Most important unresolved assumption |
What changed after review?
Name one part of the concept that changed because of evidence or reviewer pressure.
Use this structure if it helps:
We originally assumed/selected ________. After reviewing ________, we changed it to ________ because ________.
A useful change can be smaller scope, a different product, a clearer boundary, or a deleted feature. “We added more detail” is not enough by itself.
One feature you refused to add
Capstone teams often confuse more features with more engineering.
Identify one idea you chose not to include and explain why it was unnecessary, unsupported, or outside the stakeholder need.
That decision is evidence of scope control.
Assumption ledger
Carry unresolved assumptions forward deliberately.
| Assumption | Why it matters | Evidence needed in Week 17 |
|---|---|---|
Do not hide an unknown by writing it as a fact.
Phase-1 reflection
Answer these three prompts in short, specific paragraphs:
- Which requirement has the strongest connection to the stakeholder need?
- Which current assumption could force the largest redesign if it is wrong?
- What must Week 17 prove before this concept can become a defensible mission plan?
Your log is complete when another reviewer can see what the mission is for, what changed, and what remains unverified.