Every problem found in the software product gets a problem report. The report states how critical the problem is (its effect on performance, safety or security) and gives other details that help resolve it, such as which devices and supported accessories are affected, along with its type (corrective, preventive or adaptive) and its scope. Problems can surface before or after release and from inside or outside the organization. Applies to classes A, B and C.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.