Guideline: Requirements Guideline
A brief overview of best practices and requirements for the management of safety requirements in ISO 26262
Relationships
Main Description

In ISO 26262 safety requirements consist of all the requirements that are aimed achieving and ensuring the required ASILs for the item being developed.

Safety requirements are specified at several different levels and detailed in a hierarchical structure (see ISO 2626 vol 8 clause 6.2, fig 2).

Safety requirements exist as Safety goals as a result of the hazard analysis and risk assessment, these get broken down into a derived set of functional safety requirements which are capture in the Functional Safety Concept. From here they are broken down into technical safety requirements at the systems level and safety related hw and sw requirements.

In order to support and manage safety requirements the use of suitable safety requirements tool is recommended .  The management of safety requirements includes the tasks of

Obtaining agreement, between stakeholders, on the requirements

Obtaining commitments on implementing the requirements from the responsible bodies

and most importantly managing the traceability between the requirements and the artifacts detailing the implementation and tests.

Word and Excel are not requirements management tools.

When managing safety requirements they shall be captured in  hierarchical manner, they should be traceable, understandable, complete and consistent with each other.

Each individual safety requirement shall be unambiguous, comprehensible, atomic, internally consistent, feasible and verifiable.

Safety requirements shall be specified using the appropriate combination of natural language and a combination of informal, semi-formal and formal notations. Natural language is appropriate for the for the higher level safety requirements whilst the other techniques are useful for defining the more detailed systems, hw and sw requirements.

The applicability of certain methods for specifying safety requirements is dependent upon the ASIL of the item being developed

Informal notations (structured language and text) are highly recommended for Items of ASIL A or B and recommended for items of ASIL C or D

Semi formal notations (formal models, i.e. SysML, Matlab) are highly recommended for Items of ASIL C or D and recommended for items of ASIL A or B

Formal notations (Z, VDM) are recommended for Items of items of all ASIL level

This information is a summary of the information taken from ISO 26262 vol 8, clause 6.4.1 Table 1-Specifying safety requirements

Each safety requirement must have a unique identifier, an ASIL and be unambiguously identifiable as a safety requirement. A common way to do this is through the use of an attribute or some sort

Safety requirements shall inherit the ASIL of the safety requirement from which they are derived from upto the level of the original safety goal owning the ASIL. The exception is if ASIL decomposition has been applied.

Safety requirements shall be allocated to an item or an element at each level of the items hierarchy.

Each safety requirement shall be traceable to its source safety requirement in the upper hierarchical layer, each derived safety requirement at a lower hierarchical layer or its realization in the design and to the specification of its verification (i.e. test specification) .

This level of traceability is important as it supports the impact analysis if a change request is being made, and audit trail if some goes wrong in the development process and it is required for the functional safety assessment.

Safety requirements can be verified using an appropriate combination of the following methods.

Methods for the verification of safety requirements

Safety requirements must also be kept under configuration management. When there is consistency between a lower level set of safety requirements and a higher level, then the configuration management can define a baseline as the basis for the subsequent phases of the safety lifecycle.