Requirement coverage, what the website has shipped against the RTM, and web rule and RTM validation status. Live from the RTM database.
Drag a chart by ⠿ to move it within its tab (or focus ⠿ and use the arrow keys); the order is kept in this browser.
Requirements by their Requirement Status.
Each Requirement Type's requirements, by Requirement Status.
Requirements by Planned Deployment: Day-1, Deferred or No Plan.
Requirements changed each week (a person's edits; not imports or new requirements), with the running total of requirements changed so far.
Linked = traced to at least one backlog functional spec or user story. A requirement on several systems or PIs counts once in each.
Every Accepted requirement whose text changed, newest first: why, its source and Change Order, who and when. Each went back to Under Review.
Loading…
Backlog functional specs by their Status value. With filters: the functional specs in the matching requirements' trace.
Backlog user stories by Program Increment. With filters: the stories linked to the matching requirements.
Requirements with at least one shipped website version (from the release-notes trace).
Distinct change requests and website versions in the trace, by release date. With filters: only the CRs that traced a matching requirement.
Requirements by their RTM Validation value.
Test cases (Validate › Standard) by Test Phase, split by TC Status. With filters: the test cases of the matching requirements.
Test cases by Test Phase, split by their last result (Test status).
Test cases by Test tool: automated is any tool but Manual.
Test cases by the week of their Last run date, split by Test status, with the running total. Only the latest run is kept: a re-run test case moves to its new week.
Days since each test case's Last run date, averaged by Test Phase.
Requirements with at least one linked test case, by RTM section.