liveBook · Manning

Quality gate

As explained in Build High Value Software Systems

A quality gate is a defined verification point that determines whether work satisfies specified quality conditions before proceeding.

A quality gate defines what “correct” means before work begins. A specification makes intent observable: when code diverges from it, resolve the mismatch early rather than treating the spec as an approval checkpoint. section 4.1.4

Listing 4.4 Spec file
Accept: GET /api/orders/export (authenticated user)
Return: CSV file with columns: order_id, date, total, status
Filter: Only orders belonging to the requesting user
Format: Standard CSV, UTF-8 encoding
Never: Include other users' data, build the CSV in the browser, load all orders into memory, allow unauthenticated access
Prefer: Stream CSV rows from the server using bounded database reads

A CSV export specification turns privacy, format, and streaming requirements into explicit conditions for judging the implementation. section 4.1.4

How Build High Value Software Systems covers it

How deep it goes
Defines correctness and mismatch resolution, but does not specify automated enforcement.
Examples
Uses a CSV export specification covering user privacy, columns, encoding, and streaming.
What you can do after
Apply a specification to judge correctness and resolve implementation drift before it spreads.
How it connects
Connects software specifications with Lean thinking and the Andon signal.

Also explained in

Compare how 9 books explain quality gate →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Build High Value Software Systems. The section links point to the parts of the book it draws on.