Annex B lists thirty-one quality measure elements, all count or duration primitives, from the number of functions and requirements to the number of environments and duration. Every measure in clause 6 is built from elements like these. The annex is the vocabulary of the raw material. Each of the thirty-one subclauses names one element: number of functions, requirements, failures, faults, hazards, test cases, restarts, jobs, tasks, user actions, user inputs, data items, records, responses, results, user operations, system operations, languages, software modules, components, interfaces, information structures, user interfaces, interface items, operational usage scenarios, events, input conditions, hardware environments, software environments, operational environments, and duration. The names are public in the contents; the text of each subclause is behind the paywall. The list is worth reading as a whole because it shows the shape of the measure set: almost everything is a count of something, or a duration, and the quality measures combine those counts into ratios, percentages and statistics. A team that wants a measure the draft does not name can build it from the same elements and should label it as a local measure.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.