Done: 0 / 42
Partial: 0
Missing: 42
Overall Coverage: 0.0%
| ID | Title | requirement requirement |
Status |
|---|---|---|---|
| UC-002 | UC-002 — Requirements Engineer defines custom domain model via config | - | missing |
| UC-006 | UC-006 — Project lead bootstraps traceability for a new project | - | missing |
| UC-001 | UC-001 — Team member writes traceable items in AsciiDoc | - | missing |
| UC-004 | UC-004 — Requirements Engineer organizes items in partial files | - | missing |
| UC-011 | UC-011 — Requirements Engineer writes a use case | - | missing |
| UC-015 | UC-015 — Team member allocates a collision-free item ID | - | missing |
| UC-005 | UC-005 — Reviewer browses traceability matrices for coverage | - | missing |
| UC-008 | UC-008 — Data analyst explores traceability in Neo4j | - | missing |
| UC-009 | UC-009 — Architect visualizes relationship dependencies | - | missing |
| UC-012 | UC-012 — Reader finds a traceable item through site search | - | missing |
| UC-007 | UC-007 — Developer validates traceability in CI pipeline | - | missing |
| UC-010 | UC-010 — Developer assesses impact before changing a traceable item | - | missing |
| UC-013 | UC-013 — Requirements Engineer retires an obsolete traceable item | - | missing |
| UC-014 | UC-014 — Developer compares traceability across two versions | - | missing |
| UC-002 | UC-002 — Requirements Engineer defines custom domain model via config | - | missing |
| UC-006 | UC-006 — Project lead bootstraps traceability for a new project | - | missing |
| UC-001 | UC-001 — Team member writes traceable items in AsciiDoc | - | missing |
| UC-004 | UC-004 — Requirements Engineer organizes items in partial files | - | missing |
| UC-011 | UC-011 — Requirements Engineer writes a use case | - | missing |
| UC-015 | UC-015 — Team member allocates a collision-free item ID | - | missing |
| UC-007 | UC-007 — Developer validates traceability in CI pipeline | - | missing |
| UC-010 | UC-010 — Developer assesses impact before changing a traceable item | - | missing |
| UC-013 | UC-013 — Requirements Engineer retires an obsolete traceable item | - | missing |
| UC-014 | UC-014 — Developer compares traceability across two versions | - | missing |
| UC-005 | UC-005 — Reviewer browses traceability matrices for coverage | - | missing |
| UC-008 | UC-008 — Data analyst explores traceability in Neo4j | - | missing |
| UC-009 | UC-009 — Architect visualizes relationship dependencies | - | missing |
| UC-012 | UC-012 — Reader finds a traceable item through site search | - | missing |
| UC-002 | UC-002 — Requirements Engineer defines custom domain model via config | - | missing |
| UC-006 | UC-006 — Project lead bootstraps traceability for a new project | - | missing |
| UC-001 | UC-001 — Team member writes traceable items in AsciiDoc | - | missing |
| UC-004 | UC-004 — Requirements Engineer organizes items in partial files | - | missing |
| UC-011 | UC-011 — Requirements Engineer writes a use case | - | missing |
| UC-015 | UC-015 — Team member allocates a collision-free item ID | - | missing |
| UC-005 | UC-005 — Reviewer browses traceability matrices for coverage | - | missing |
| UC-008 | UC-008 — Data analyst explores traceability in Neo4j | - | missing |
| UC-009 | UC-009 — Architect visualizes relationship dependencies | - | missing |
| UC-012 | UC-012 — Reader finds a traceable item through site search | - | missing |
| UC-007 | UC-007 — Developer validates traceability in CI pipeline | - | missing |
| UC-010 | UC-010 — Developer assesses impact before changing a traceable item | - | missing |
| UC-013 | UC-013 — Requirements Engineer retires an obsolete traceable item | - | missing |
| UC-014 | UC-014 — Developer compares traceability across two versions | - | missing |