One or more software development plans are set up to cover the development activities, suited to the scope, size and safety class of the software system. The plan fully defines, or refers to, the life cycle model used for development and addresses: the processes to be followed; the deliverables of activities and tasks, documentation included; traceability that links system requirements, software requirements, system tests and the software-implemented risk control measures; managing configuration and change, covering configuration items that are SOUP as well as development support tools; and problem resolution at every life cycle stage. The model may vary by item class and may be iterative, and the plan may sit within the overall system plan. Applies to classes A, B and C.
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.