Requirements

Turn discovery inputs into structured, reviewable scope with traceability to tasks and tests.

Overview

Requirements represent scope that must be delivered and validated. They connect discovery inputs to tasks and test cases.

Key Concepts

• Requirement: scope statement with acceptance criteria
• Lifecycle: statuses that move scope from draft to completed
• Traceability: links from requirements to tasks and tests

How It’s Used

Use Requirements to define what must be delivered. Use tasks to implement requirements. Use tests to validate requirements.

Benefits

• Clearer scope boundaries and reduced scope creep
• Better accountability through ownership and status tracking
• Stronger audits through traceability to validation evidence

Setup Steps

1

Create a requirement

1. Navigate to a Project.
2. Open Requirements.
3. Select New requirement.
4. Define title, description, and acceptance criteria.

2

Use consistent lifecycle states

Typical states include Draft, In review, Approved, In progress, and Completed. Status names vary by Account configuration.

3

Link to tasks and tests

Link requirements to tasks for execution tracking. Link requirements to tests for coverage tracking.

• Create and Assign Tasks
• Create Test Cases

When enabled, Console can generate draft tasks and draft test cases from requirement context. Generated output still requires review before approval.

Best Practices

• Require acceptance criteria before approval.
• Keep requirement titles short and scannable.
• Link artifacts that justify scope decisions.
• Use Segments and Processes for reporting consistency when configured.

Summary

Requirements define scope and connect to execution and validation. Traceability links support reporting, governance, and audits.

Related

• Requirements Management
• Requirements View
• Requirements Modification
• Requirements Rejection
• Audit Trail
• Dependencies and Relationships
• Creating Dependencies Between Requirements
• Custom Fields
• Working with Views