---
id: req.term-specification
title: Specification (requirements specification)
kind: term
domain: requirements
description: 'A requirements specification is a systematically written collection of requirements for a system — what it must do and how well — that can be reviewed, tested against and traced.'
version: 1.0.1
status: review
applies_to: [core]
sources:
  - title: IREB CPRE Glossary
    url: https://cpre.ireb.org/en/downloads-and-resources/glossary
    license: LicenseRef-All-Rights-Reserved
    accessed: 2026-11-20
  - title: SWEBOK Guide v4.0
    url: https://www.computer.org/education/bodies-of-knowledge/software-engineering
    license: LicenseRef-All-Rights-Reserved
    accessed: 2026-11-20
standards: [ISO/IEC/IEEE 29148:2018]
related: [req.requirements-specification, req.acceptance-criteria, req.term-prd, arch.term-blueprint, process.term-release-spec]
last_reviewed: 2026-11-21
review_every: 12
---

## 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](/knowledge/glossary/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)](/knowledge/core/requirements/requirements-specification/) — rules for writing, tracing, approving and changing it.
- [Acceptance criteria](/knowledge/core/requirements/acceptance-criteria/) — how each requirement is proved.
- [PRD](/knowledge/glossary/prd/) — a specification written from the product side.
- [Blueprint](/knowledge/glossary/blueprint/) — the document that says how it is built.
- [Release spec](/knowledge/glossary/release-spec/) — the document for one release; not a specification in this sense.

## Sources

- [IREB CPRE Glossary](https://cpre.ireb.org/en/downloads-and-resources/glossary) — all rights reserved; summarised, not copied. Accessed 2026-11-20.
- [SWEBOK Guide v4.0](https://www.computer.org/education/bodies-of-knowledge/software-engineering) — all rights reserved; summarised, not copied. Accessed 2026-11-20.
