19. ISO 26262 Applicable clausesΒΆ
Clause |
Applicable |
Rationale |
|---|---|---|
2-5 Overall safety management |
Yes |
|
2-6 Project dependent safety management |
Yes |
|
2-7 Safety management regarding production,
operation, service and decommissioning
|
Yes |
|
3-5 Item definition |
No |
SW SEooC, no Item level |
3-6 Hazard analysis |
No |
SW SEooC, no Item level |
3-7 Functional safety concept |
No |
SW SEooC, no Item level |
4-5 Product development system level |
No |
SW SEooC, no system level |
4-6 Technical safety concept |
No |
SW SEooC, no system level |
4-7 System integration and testing |
No |
SW SEooC, no system level |
4-8 Safety validation |
No |
SW SEooC, no system level |
5-5 Development on hardware level |
No |
SW SEooC, no hardware level |
5-6 Specification of hardware safety requirements |
No |
SW SEooC, no hardware level |
5-7 Hardware design |
No |
SW SEooC, no hardware level |
5-8 Evaluation of hardware metrics |
No |
SW SEooC, no hardware level |
5-9 Safety goal violations |
No |
SW SEooC, no hardware level |
5-10 Hardware integration and verification |
No |
SW SEooC, no hardware level |
5-C Architectural metrics |
No |
SW SEooC, no hardware level |
6-5 Product development at the software level |
Yes |
|
6-6 Specification of software safety requirements |
Yes |
|
6-7 Software architectural design |
Yes |
|
6-8 Software unit design and implementation |
Yes |
|
6-9 Software unit verification |
Yes |
|
6-10 Software integration and verification |
Yes |
|
6-11 Testing of the embedded software |
Yes |
|
6-C Software configuration |
No |
The certified libraries are delivered as pre-compiled libraries and have to be statically
linked into applications (see
LIBS_CSTR_0080_LINK_STATIC).There is no way to configure a certified library binary after it is compiled and linked statically.
|
7-5 Planning for production, operation,
service and decommissioning
|
No |
SW SEooC, no hardware level |
7-6 Production |
No |
SW SEooC, no hardware level |
7-7 Operation, service & decommissioning |
Tailored |
Only Field Monitoring and Safety instructions applicable |
8-5 Interfaces within distributed developments |
No |
No distributed development / DIA, therefore not applicable |
8-6 Specification and management of safety
requirements
|
Yes |
|
8-7 Configuration management |
Yes |
|
8-8 Change management |
Yes |
|
8-9 Verification |
Yes |
|
8-10 Documentation management |
Yes |
|
8-11 Confidence in the use of software tools |
Yes |
|
8-12 Qualification of software components |
No |
Qualification not applied, handled as new development |
8-13 Evaluation of hardware elements |
No |
SW SEooC, no hardware level |
8-14 Proven in use argument |
No |
Not used |
8-15 Interfacing an application that is
out of scope of ISO 26262
|
No |
SW SEooC, no system level |
8-16 Integration of safety-related systems
not developed according to ISO 26262
|
No |
SW SEooC, no system level |
9-5 Requirements decomposition |
No |
Not used, all ASIL B |
9-6 Coexistence of elements |
No |
Only a single element of ASIL B, therefore no coexistence |
9-7 Analysis of dependent failures |
No |
No dependencies*, single ASIL component, therefore tailored |
9-8 Safety analyses |
No |
No architectural level, single component, no further analysis required |
12-5 Adaption for motorcycles |
No |
No motorcycles in scope |
12-6 Safety culture |
No |
No motorcycles in scope |
12-7 Confirmation measures |
No |
No motorcycles in scope |
12-8 Hazard analysis and risk analysis |
No |
No motorcycles in scope |
12-9 Vehicle integration and testing |
No |
No motorcycles in scope |
12-10 Safety validation |
No |
No motorcycles in scope |