Develop and define a system architecture fulfilling the RAMS requirements by structured decomposition into subsystems and components with completely defined interfaces, using a structured design methodology, and allocate to each a derived set of RAMS requirements; identify constraints on technology (independence of functions or development processes) and specify and document all safety-related assumptions; specify the subsystems and components to meet the system RAMS requirements including common cause and multiple failures; derive and allocate requirements for any new hazards arising from the architecture; identify and fulfil the integration requirements of pre-existing subsystems; for COTS demonstrate at system level that their failures cannot jeopardise the safety requirements; where safety functions follow a code of practice justify the relationship in the architecture and realise them per the code; specify acceptance criteria, processes and demonstration for subsystems and components and their interfaces; update the safety, RAM and validation plans; derive SRACs for the later phases from the RAMS analysis. Deliverables: architecture with interface specifications and system hazard analysis, allocation of RAMS requirements, acceptance criteria and processes, updated plans, SRACs and hazard log.
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.