The aircraft architecture is established, aircraft functions are grouped and the groups are allocated to systems, with each candidate architecture assessed repeatedly by analysing its functions and performance and through the PASA, to confirm it can meet the top-level safety objectives. The basis for each grouping decision, including its assumptions, is recorded, since the best grouping can depend on implementation limits, the effects of failures and support over the life cycle; each allocation defines inputs, processing and outputs and considers operational and support aspects, and assumptions made become part of the system requirements package. The output is an aircraft architecture with functions allocated to systems.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.