This includes requirements specification, design, implementation, integration, verification, validation and configuration. ISO 26262 specifies the following requirements:
- Functional safety management for automotive applications
- The concept phase for automotive applications
- Product development at the system level for automotive applications software architectural design
- Product development at the hardware level for automotive applications software unit testing
- Product development at the software level for automotive applications
- Production, operation, service and decommissioning
- Supporting processes: interfaces within distributed developments, safety management requirements, change and configuration management, verification, documentation, use of software tools, qualification of software components, qualification of hardware components and proven-in-use argument
- Automotive Safety Integrity Level (ASIL)-oriented and safety-oriented analysis
ISO 26262 does not cover:
- Unique E/E systems in special purpose vehicles such as vehicles designed for drivers with disabilities
- Safety standards for large vehicles, such as those over 3500KB (7700 pounds) gross weight
- Hazards related to electric shock, fire, smoke, heat, radiation, toxicity, flammability, reactivity, corrosion, release of energy and similar hazards, unless directly caused by malfunctioning behavior of E/E safety-related systems
- Nominal performance of E/E systems
Part 6 of the standard specifically addresses product development at the software level. Requirements for the following development activities are specified:
- Initialization of product development
- Specification of software safety requirements
- Software architectural design
- Unit design and implementation
- Unit testing
- Software integration and testing
- Verification of software safety requirements.
Methods defined by the ISO 26262 standard should be selected depending on the automotive safety integrity level. The higher the ASIL, the more rigorous the methods.
