Maintained relationships explain which requirements each design decision addresses, which code implements that design, and which tests verify the required behaviour.
An issue leads to code and a pull request.
Read the rating and evidence
Work-item hierarchy, requirement-based suites, commits, pull requests, builds and test results provide meaningful traceability.
Read the rating and evidence
Confluence requirements/decision pages, Jira work items and repository references connect parts of the workflow.
Read the rating and evidence
Per-feature requirements, design and tasks are connected; optional property tests reference requirements/tasks.
Read the rating and evidence
The constitution, feature specs, plans and tasks are connected.
Read the rating and evidence
Capability specs, change proposals, designs and tasks are connected.
Read the rating and evidence
PRD-derived UX/architecture, referenced stories, code review against plans/baselines and the optional Test Architect (TEA) requirement-to-test trace connect the layers.
Read the rating and evidence
SDD specs identify code targets and individual test files.
Read the rating and evidence
Configured typed, directional relationships connect requirements, design, risks and verification.
Read the rating and evidence
Configured work-item roles/rules and LiveDocs connect requirements, design, code, test cases and test records.
Read the rating and evidence
Droid plans, repository instructions and QA flow routing do not establish maintained requirement–design–code–test relationships.
Read the rating and evidence