One or more software maintenance plans are set up for the maintenance process. They cover: how feedback after release is received, recorded, assessed, resolved and followed up; criteria for deciding whether feedback counts as a problem; applying the software risk management process; applying problem resolution to problems found after release; applying configuration management to modifications; and how upgrades, bug fixes, patches and SOUP obsolescence are assessed and put into effect. 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.