Project Metrics
Status charts read the canonical Sphinx-Needs records on each documentation build. Counts describe recorded workflow status; they do not establish release readiness. See Project maturity for review history and verification context.
Requirement status
Status counts are calculated from the requirements on each documentation build.
Stakeholder requirements
Total: 65
System requirements
Total: 11
Software requirements
Total: 75
Architecture element status
System elements
Total: 2
Software elements
Total: 10
Test-case maturity
Maturity describes review status (draft, reviewed, accepted), not execution
outcome, pass rate or verification state. Populations use the canonical
test_system and test_software tags, independently of requirement links.
System test cases
Total: 70
Software test cases
Total: 56
Scope management status
Problem tickets use their New / Analyzed / Fixed lifecycle. Change requests use their canonical Draft / Accepted / Implemented Need status. These lifecycles do not change requirement acceptance or verification results.
Problem tickets
Total: 16
Change requests
Total: 19