Requirements

Every requirement in TraceUnified is a controlled record with its own identity, lifecycle, and state — scored for quality and checked for compliance as you write, not after the fact. Requirements are the anchor of the thread: tests verify them, risks reference them, and architecture realizes them.

This section covers authoring requirements, the item types and fields that structure them, how they’re versioned, and the governance — lifecycle, quality, and compliance — that keeps them trustworthy.

What’s in this section

• Authoring requirements — creating and editing under control
• Item types & fields — the structure of a requirement
• Versions & history — every change, captured
• Lifecycle & states — draft, review, approved, and beyond
• Quality scoring — writing quality and ALCOA+ data integrity
• Compliance checks — framework checks during authoring
• Author a requirement — a step-by-step walkthrough from draft to clean quality and compliance