5
Components in the finished document
Template And Component Specs
What each page template and reusable component must contain and emit, at every state.
Where This Sits
0
Measured directly, not asserted
5
Pieces that carry my judgment
This is a Specification and build deliverable, which means it specifies a change precisely enough to build. It is the unit of scope: it can be commissioned on its own, priced on its own, and accepted on its own, whether or not anything else is bought alongside it.
It is not a package and not a retainer. It is one document with 5 components, and the list below is the whole of it.
What Is Inside It
Every component is listed with the one sentence that says what it is. They are grouped by how each one is produced, because the difference between a number a tool gave me and a number I decided matters more than most reports admit.
Judged
My reading of the evidence. This is the part you are actually paying for, and the part you are entitled to argue with.
- Component specification
- The behaviour, markup and states of one reusable interface component.
- Technical specification
- The behaviour required, described precisely enough that two engineers would build the same thing.
- Placement diagram
- Where in the template each element belongs, and what it must not sit inside.
- Acceptance criteria
- The conditions each ticket must satisfy to be accepted, written so QA does not require judgement.
- Edge case rules
- What to do at the boundaries, where the general rule stops working.