The organization's features that matter for measurement, for example its business and technical goals, are described, information needs identified and prioritized, measures selected and specified, and procedures for data collection, analysis, access and reporting defined. Useful requirements measures include requirements quality against the characteristics of 5.2.5 (for estimating analysis effort, setting a release standard, as an entry criterion to reviews and in contracting), requirements quantity (progress, completeness estimates, effort per requirement), and requirements volatility (whether the process converges, and early warning of stakeholders failing to agree), together with trends, change rate and backlog, traceability measures (such as the percentage of parents without children and the average number of children per parent), verification and validation status, and closure of open-item markers against plan. Functional size measurement of software gives reliable results only if the software requirements have been allocated and derived from the system requirements fully and correctly.
This control maps to 1 controls across 1 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.
The graph holds this control, the 1 it maps to, and the evidence behind each claim, over MCP and REST.