[ISO 26262, Sub-phase] Technical Safety Concept Design

Brief Introduction

In an iterative process, the technical safety concept is developed, incorporating technical safety requirements and the system architectural design. The system architecture is established, the technical safety requirements are allocated to elements of the system, and, if applicable, on other technologies. In addition, the technical safety requirements are refined and requirements arising from the system architecture are added, including the hardware-software interface (HSI). Depending on the complexity of the architecture, the requirements for subsystems can be derived iteratively.

Input Work Products

Prerequisites

• Functional Safety Concept
  • If the system under analysis is a sub-system, this input should be the Technical Safety Concept of its mother system
• System Architectural Design (from external source)
• Requirements to the item from other safety relevant items (if applicable)

Supporting Information

• Hazard Analysis and Risk Assessment (HARA) Report
• Item Definition

Output Work Products

1. Technical safety requirements specification
2. Technical safety concept
3. System architectural design specification
4. Hardware-software interface (HSI) specification
5. Specification of requirements for production, operation, service and decommissioning
6. Verification report for
   • system architectural design
   • HSI specification
   • specification of requirements for production, operation, service and decommissioning
   • technical safety concept

Activities

• to specify technical safety requirements regarding the functionality, dependencies, constraints and properties of the system elements and interfaces needed for their implementation (for output 1)
• to specify technical safety requirements regarding the safety mechanisms to be implemented in the system elements and interfaces (for output 1)
• to develop a system architectural design and a technical safety concept that satisfy the safety requirements and that are not in conflict with the non-safety-related requirements (for output 2 and 3)
• Safety Analyses and avoidance of systematic failures (for output 2 and 3)
• Measures for control of random hardware failures during operation (for output 2 and 3)
• Allocation to hardware and software (for output 2 and 3)
• Hardware-software interface (HSI) specification (for output 4)
• to specify requirements regarding the functional safety of the system and its elements during production, operation, service and decommissioning (for output 5)
• Verification (of the design) (for output 6)
  • to verify that the technical safety requirements are suitable to achieve functional safety at the system level and are consistent with the functional safety requirements
  • to verify that the system architectural design and the technical safety concept are suitable to satisfy the safety requirements according to their respective ASIL.

Explanation

Required info for the specification of technical safety requirements

• the safety-related dependencies and constraints of items, systems and their elements
  • Design constraints can result from
    • environmental conditions
    • the installation space
    • the implementation itself (e.g. available performance, thermal capacity, thermal dissipation)
    • other functional or non-functional requirements (e.g. security, physical limits of used technology)
• the external interfaces of the system (if applicable)
• the configurability of the system
  • The configurability of systems is determined by variants in the system elements, by configuration data or by calibration data and is often used as part of the strategy to reuse existing systems for different applications.