Each modification is analysed for its impact (Figure 11): the change is described, its effect on aircraft functions, failure condition classifications and safety assessments is evaluated, a change category is assigned (Table 4 gives an example assignment) and the development assurance activities required for that category are determined (Table 5), so that the rigor applied to the change matches its significance.
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.