Capstone assessment
Deliverables
- A short metric contract stating grain, population, date range, currency, refund cutoff and attribution.
- A monthly SQL report with the seven columns specified in module 13.
- An all-customer contribution query retaining all eight customers.
- An audit note with source counts, unique-order checks, at least one hand calculation, total reconciliation, boundary checks and one counterexample to an incorrect method.
- A 150–250 word manager summary describing findings, one reasonable next question and the evidence limits. Include a labelled monthly table or chart.
- A feature appendix from module 11 with its six-row population, feature/label time separation and two limitations of the fixture's history assumptions.
Use the synthetic data only. Do not submit credentials, real customer information, production connection details or an unreviewed AI chat export.
Rubric
| Area | Points | Full-credit evidence |
|---|---|---|
| Metric definition and scope | 15 | Explicit order grain, completed-only filter, half-open dates, INR units and stated refund attribution |
| SQL and grain correctness | 25 | Independent child aggregation; unique order keys; correct monthly and customer outputs |
| Coverage and data quality | 15 | All customers retained where required; no missing included orders; raw intake and null limitations explained |
| Verification | 20 | Hand-calculated split-payment case, source counts, monetary reconciliation and boundary/empty checks |
| AI feature design and safety | 15 | Correct cutoff population, no future label in features, history caveat, reviewed read-only execution |
| Communication and reproducibility | 10 | Runnable files, meaningful names, concise summary, labelled output and justified limits |
Suggested pass threshold: 75/100. In addition, all mandatory gates below must pass. This is a course design rubric, not an accredited qualification or an automatically granted certificate.
Mandatory gates
- No duplicated monetary amounts from joining independent child records
- Completed-order and date-boundary definitions preserved
- Refunds included exactly once under the agreed cutoff
- Every required customer retained in the customer report
- Feature and label windows separated, with historical-availability limits acknowledged
- No production writes, exposed secrets or claim that arbitrary AI-generated SQL is safe merely because it begins SELECT
A learner should correct a failed gate and resubmit the relevant evidence rather than receive a pass based on formatting or total points alone.
Review questions
Ask the learner to explain order 1001 on paper, move the cutoff mentally to 1 March, describe why Eren has null recency, and identify what changes if a month has no records. These questions test understanding beyond memorizing an expected output.
Instructor notes
The validator checks the supplied reference files, not a learner's intent, free-form query equivalence or written reasoning. Review the learner's outputs and explanations separately. Exact plan costs and numeric trailing zeros are not grading criteria. A different correct query is acceptable if it preserves the metric contract and passes the evidence checks.
Before public release, run a beginner pilot, test installation on the learner's supported operating systems, and conduct a fuller keyboard/screen-reader accessibility review of the eventual website integration. These checks are not implied by the cloud reference validation.