Defense Dossier Review

This is the final engineering review before the capstone defense.

The objective is not to make the dossier longer. The objective is to make the argument traceable, bounded, and difficult to misunderstand.

A strong defense dossier lets a reviewer move from a claim to the evidence behind it without guessing.

Build the claim-evidence index

Choose the most important claims in your plan and map each one.

This table is the backbone of the defense.

Red-team the dossier

Perform four deliberate attacks.

Attack 1: Overclaiming

Circle every word such as:

• safe;
• accurate;
• approved;
• reliable;
• guaranteed;
• authorized;
• complete.

For each one, ask:

What evidence earns this word?

If the answer is weak, narrow the claim.

Attack 2: Missing transitions

Trace the full mission as a sequence:

need -> requirement -> system choice -> route -> evidence -> product -> decision

Any jump in that chain needs explanation.

Example:

“We selected this camera because it has high resolution.”

Missing transition:

What product detail requirement makes that resolution necessary?

Attack 3: Hidden assumptions

Look for sentences written as facts that depend on future conditions.

Examples:

• the weather will be acceptable;
• the site will be empty;
• the aircraft will achieve the published endurance;
• the GNSS solution will remain stable;
• the official source will still show the same operating condition.

Mark them as assumptions or re-check gates.

Attack 4: Control without verification

Find every mitigation or control and ask:

How do we know this control is present, configured, understood, and effective?

A checklist item is not evidence that the system passed the check. A geofence is not evidence that the boundary is correct. A source link is not evidence that the source was checked recently.

Worked review: presentation quality vs evidence quality

Imagine two teams.

Team A has beautiful graphics, smooth animations, and a confident speaker. Their risk slide says “all risks mitigated.”

Team B has a plain dossier. Their risk register shows two residual risks, one unresolved assumption, and a clear no-go rule tied to each.

Team B has the stronger technical defense.

Why?

Because the goal is not to make uncertainty disappear. The goal is to show that uncertainty is known, bounded, and connected to a decision.

Assemble the final dossier

Your final package should contain, in a controlled order:

1. stakeholder and mission need;
2. required product and success criteria;
3. system concept and boundary;
4. route/data plan;
5. roles and artifact manifest;
6. source ledger;
7. risk register;
8. no-go card;
9. claim-evidence index;
10. review/revision record;
11. final limitations;
12. recommended next verification steps.

The exact file format is less important than traceability.

Peer-defense drill

Give another team five minutes with the dossier before they question you.

They must ask:

• one requirement question;
• one evidence question;
• one failure/recovery question;
• one authority/boundary question;
• one limitation question.

Your team may answer only from the dossier and its evidence. If the answer exists only in someone’s memory, record the gap and fix the artifact.

Review decision

Classify the dossier as:

• Ready for defense — claims are traceable and limitations are explicit;
• Ready with revisions — argument is coherent but specific evidence/control gaps remain;
• Not ready — mission need, boundaries, evidence, or risk logic cannot yet support the defense.

Write the decision and the evidence behind it.

That decision is more important than pretending every project is automatically ready because Week 18 arrived.