Specification (requirements specification)
- Status
- Review
- Version
- 1.0.1
- Authority
- Not stated
- Applies to
- Core
Definition
A specification, in requirements work, is a systematically written collection of requirements for a system: what it must do and how well. A specification says what is needed and can be checked; it does not say how the system will be built, which is the blueprint’s job.
The definition follows the IREB glossary entry for requirements specification. A specification is not a release spec: that is a shorter document written for one release or change, kept apart by name (see Release spec).
Example
Each requirement is one verifiable statement with an id (FR-5 The site MUST show at most 20 search results per page.) and traces forward to an acceptance criterion (AC-5).
Related
- Requirements specification (PRD or SRS) — rules for writing, tracing, approving and changing it.
- Acceptance criteria — how each requirement is proved.
- PRD — a specification written from the product side.
- Blueprint — the document that says how it is built.
- Release spec — the document for one release; not a specification in this sense.
Sources
- IREB CPRE Glossary — all rights reserved; summarised, not copied. Accessed 2026-11-20.
- SWEBOK Guide v4.0 — all rights reserved; summarised, not copied. Accessed 2026-11-20.