Source code is analysed for correctness and consistency against a list of error types the standard names, among them stack and memory use, worst-case execution time and arithmetic accuracy; the revision extended the list with new subjects (supporting discussion papers cover cache management and floating-point use). Table A-5 objective 6, described in 6.3.4.f; applies at levels A, B, C, independence required at level A; activities 6.3.4; outputs Software Verification Results. The revision requires the effect of the compiler, linker and hardware on worst-case execution time to be assessed and recognises that reviews and analyses alone may not suffice for timing and stack, so tests may be needed; tools may perform part of the analysis.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.