Turn a workbook-delivery brief into measurable quality criteria, a defect log and a release decision supported by observed checks.
Aster Club is preparing a 20-page learner workbook. The agreed checks are readable text, working links, correct example totals and complete page order. A practice review finds six defects. Severity labels are local learning rules, not a universal quality standard.
| Defect | Severity | State |
|---|---|---|
| Wrong example total | critical | open |
| Broken download link | critical | fixed; retest pending |
| Missing page number | minor | open |
| Typo in heading | minor | fixed; retest passed |
| Low-contrast note | major | open |
| Duplicate page | major | fixed; retest passed |
A quality criterion translates a user need into evidence. Correct examples require reconciled calculations; usable links require the intended destination; complete order requires all expected pages. Avoid a single looks professional checkbox. Specify who checks what and which failures prevent release so the team does not negotiate the meaning of done at the deadline.
Write four acceptance criteria with a method, expected result and evidence location.
Acceptance matrix
Record your result and evidence here or in a separate file.
Each criterion can fail for a stated reason and has an observable pass condition.
Replace a subjective label with a concrete review question or measurement.
Quality assurance improves the process that produces the deliverable. A reusable calculation sheet, link review and controlled source file can reduce recurring errors. These practices support inspection but do not prove that the final workbook passes. Assign checkpoints while revision is still affordable, and record the document version reviewed at each one.
Design three early checkpoints and name the defect each is intended to prevent.
Quality assurance plan
Record your result and evidence here or in a separate file.
Each checkpoint has a purpose, owner and version reference.
Do not list final acceptance checks again without showing an earlier prevention activity.
A defect record needs location, expected behavior, observed behavior, severity, owner and status. Severity concerns impact; priority concerns the order of work. A critical defect may be fixed quickly yet remain unverified. Keep fixed, retested and accepted states distinct to prevent a status label from overstating the evidence.
Expand the six supplied rows into complete records. Count open and unverified critical defects separately.
Six-row defect register
Record your result and evidence here or in a separate file.
One critical defect is open and one critical fix still needs retesting.
Do not count a promised fix as a passed retest.
A retest checks whether the original failure was corrected; a nearby regression check asks whether the fix broke something else. Apply the release rule consistently. For this case, every critical and major defect must be verified closed, and any accepted minor defect must have an explicit owner and disposition.
Write a retest for the example total and download link, then make the release decision from the supplied states.
Retest sheet and hold decision
Record your result and evidence here or in a separate file.
The current workbook is held because critical and major issues remain unresolved.
Trace the decision to individual defects rather than a vague percentage complete.
Acceptance is a recorded decision about a particular version and set of conditions. Preserve the evidence trail, including accepted limitations. A later edit can invalidate earlier checks, so identify which checks must be repeated when a calculation, URL or page is changed. This protects both the learner and the delivery team from stale sign-off.
Create a release record template and apply a change that modifies one calculation page. Identify the affected retests.
Versioned acceptance record
Record your result and evidence here or in a separate file.
The record names the version and does not carry forward an invalidated calculation check.
Add a change-impact column so a new version cannot inherit every old pass automatically.
Deliver the acceptance matrix, prevention plan, defect register, retest instructions and versioned release decision. Simulate one corrected build and record exactly which new evidence permits release.
No release is marked accepted while a critical or major defect lacks the required verified closure.
| Criterion | Points | Evidence |
|---|---|---|
| Evidence and correctness | 30 | Calculations, source use and results match the supplied case; limitations are honest. |
| Required artifacts | 30 | All five stage outputs and the capstone handoff are present and inspectable. |
| Reasoning and decisions | 20 | Choices, assumptions, alternatives and the case-specific critical condition are explained. |
| Reproducibility | 10 | A reviewer can follow the stated steps and distinguish expected from observed results. |
| Clear communication | 10 | Labels, units, structure and evidence references make the work easy to review. |
Score at least 80/100, supply every required artifact, and satisfy the path-specific critical condition. Rework missing evidence before marking complete.
The baseline is not releasable: two critical items lack verified closure, and one major contrast defect is open. A minor typo already passed retest, but that success does not cancel the unresolved issues. The release decision must change only after the required evidence changes.
This is a document-quality practice case; it is not certification, regulatory compliance testing or a universal severity scheme.