Node A5

Requirement ID Scheme Generator

Compose the segments — prefix, subsystem, type, serial — and get back a live preview, a plain-language scheme specification your whole team can follow, and a starter allocation register.

Preview

Scheme specification

Why numbering schemes rot — and the rules that prevent it

Every requirements database starts tidy. It rots the same three ways, and all three are preventable at scheme-design time.

Rot #1: reused IDs. A requirement gets deleted, someone recycles its number for a new one, and now every old test report, analysis, and email that cited the original silently points at the wrong requirement. The fix is a rule, stated in the scheme and enforced in review: an ID, once assigned, is permanent. Gaps in the sequence are not untidiness — they're the audit trail working.

Rot #2: volatile information baked into the ID. Encoding priority, revision, requirement owner, or verification status in the identifier feels efficient right up until any of those change — and they all change. Then you either renumber (breaking every reference; see rot #1) or you live with IDs that lie. The ID should encode only what is true for the requirement's whole life: which project, which subsystem, which kind of statement, and a serial. Everything volatile belongs in attributes alongside the requirement, not inside its name.

Rot #3: variable-width serials. REQ-42 sorts after REQ-100 in every plain-text listing, spreadsheets mangle it, and a dropped digit turns one valid ID into another valid ID. Fixed-width, zero-padded serials (REQ-0042) keep text sorting correct and make most transcription errors visually obvious. Four digits is the safe default — three-digit schemes get outgrown by real projects more often than anyone expects.

The allocation register is the quiet workhorse: by reserving a serial block per subsystem up front, two teams can assign IDs in parallel without colliding and without a central bottleneck. Keep the register under version control, update it in the same change that adds the requirement, and the scheme will still be clean at CDR.

Everything runs locally in your browser. Nothing you enter is transmitted anywhere.