What you will learn
- Frozen validation
- Demo observation
- Cost reconciliation
- Operational drill
Frozen validation
Execute the frozen protocol and record deviations as they occur. A deviation can be justified, but it creates a new version or limitation that the reader must see. Do not silently change the study after unfavorable results.
Demo observation
Maintain data and code provenance so every result can be rebuilt. Preserve raw observations, transformation steps, configuration and environment information under appropriate access rules.
Cost reconciliation
Collect demo execution records when implementation is part of the question. Label simulated, replayed and observed demo results separately. Do not combine them into one performance series without explaining the different evidence types.
Operational drill
Perform reconciliation and quality checks before interpreting outcomes. Resolve duplicate fills, missing costs and timestamp errors. Keep a defect log so the final report reflects corrections rather than an artificially flawless process.
Worked example
A capstone changes its cost model midway after discovering omitted financing. The correction is necessary, but earlier and revised results should be retained with an explanation and the conclusion reassessed.
Try it yourself
Write a protocol-deviation record for that correction, including which outputs must be regenerated.
Show the worked solution
Record the omitted charge, evidence, correction date, affected version and regenerated net results and risk measures. Explain whether the original decision changes. Do not present the revised procedure as the one originally frozen.
Apply this to your course project
Submit code or rules, evidence, risk plan, demo logs and an independent critique.
Keep the calculation inputs, assumptions and decisions with your work. Practical exercises are self-reviewed; the scored knowledge checks assess the questions shown, not an independent certification of practical competence.