For each such software item the potential causes of its contribution to a hazardous situation are identified, considering incorrect or incomplete specification of functionality, software defects, failure or unexpected results from SOUP, hardware failures or other software defects causing unpredictable operation, and reasonably foreseeable misuse. Applies to classes B and C.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.