BS ISO 26262-10:2018 – TC:2020 Edition
$280.87
Tracked Changes. Road vehicles. Functional safety – Guidelines on ISO 26262
Published By | Publication Date | Number of Pages |
BSI | 2020 | 253 |
PDF Catalog
PDF Pages | PDF Title |
---|---|
163 | undefined |
169 | Foreword |
171 | Introduction |
174 | 1 Scope 2 Normative references |
175 | 3 Terms and definitions 4 Key concepts of ISO 26262 4.1 Functional safety for automotive systems (relationship with IEC 61508[1]) |
177 | 4.2 Item, system, element, component, hardware part and software unit |
178 | 4.3 Relationship between faults, errors and failures 4.3.1 Progression of faults to errors to failures |
179 | 4.4 FTTI and emergency operation tolerant time interval 4.4.1 Introduction |
180 | 4.4.2 Timing model — Example control system |
182 | 5 Selected topics regarding safety management 5.1 Work product 5.2 Confirmation measures 5.2.1 General |
183 | 5.2.2 Functional safety assessment |
185 | 5.3 Understanding of safety cases 5.3.1 Interpretation of safety cases |
186 | 5.3.2 Safety case development lifecycle 6 Concept phase and system development 6.1 General 6.2 Example of hazard analysis and risk assessment 6.2.1 General 6.2.2 HARA example 1 |
187 | 6.2.3 HARA example 2 6.3 An observation regarding controllability classification |
188 | 6.4 External measures 6.4.1 General 6.4.2 Example of vehicle dependent external measures 1 6.4.3 Example of vehicle dependent external measures 2 |
189 | 6.5 Example of combining safety goals 6.5.1 Introduction 6.5.2 General 6.5.3 Function definition 6.5.4 Safety goals applied to the same hazard in different situations |
190 | 7 Safety process requirement structure — Flow and sequence of the safety requirements |
192 | 8 Concerning hardware development 8.1 The classification of random hardware faults 8.1.1 General 8.1.2 Single-point fault |
193 | 8.1.3 Residual fault 8.1.4 Detected dual-point fault 8.1.5 Perceived dual-point fault |
194 | 8.1.6 Latent dual-point fault 8.1.7 Safe fault 8.1.8 Flow diagram for fault classification and fault class contribution calculation |
198 | 8.1.9 How to consider the failure rate of multiple-point faults related to software-based safety mechanisms addressing random hardware failures 8.2 Example of residual failure rate and local single-point fault metric evaluation 8.2.1 General 8.2.2 Technical safety requirement for sensor A_Master |
199 | 8.2.3 Description of the safety mechanism |
202 | 8.2.4 Evaluation of example 1 described in Figure 12 |
210 | 8.3 Further explanation concerning hardware 8.3.1 How to deal with microcontrollers in the context of an ISO 26262 series of standards application 8.3.2 Safety analysis methods |
217 | 8.4 PMHF units — Average probability per hour |
220 | 9 Safety Element out of Context 9.1 Safety Element out of Context development |
221 | 9.2 Use cases 9.2.1 General |
222 | 9.2.2 Development of a system as a Safety Element out of Context example |
224 | 9.2.3 Development of a hardware component as a Safety Element out of Context example |
226 | 9.2.4 Development of a software component as a Safety Element out of Context example |
228 | 10 An example of proven in use argument 10.1 General |
229 | 10.2 Item definition and definition of the proven in use candidate 10.3 Change analysis 10.4 Target values for proven in use |
230 | 11 Concerning ASIL decomposition 11.1 Objective of ASIL decomposition 11.2 Description of ASIL decomposition 11.3 An example of ASIL decomposition 11.3.1 General 11.3.2 Item definition |
231 | 11.3.3 Hazard analysis and risk assessment 11.3.4 Associated safety goal 11.3.5 System architectural design |
232 | 11.3.6 Functional safety concept |
233 | 12 Guidance for system development with safety-related availability requirements 12.1 Introduction |
234 | 12.2 Notes on concept phase when specifying fault tolerance 12.2.1 General 12.2.2 Vehicle operating states in which the availability of a functionality is safety-related 12.2.3 Prevention of hazardous events after a fault |
235 | 12.2.4 Operation after fault reaction |
236 | 12.2.5 Fault tolerant item example |
241 | 12.2.6 ASIL decomposition of fault tolerant items |
242 | 12.3 Availability considerations during hardware design phase 12.3.1 Random hardware fault quantitative analysis |
244 | 12.4 Software development phase 12.4.1 Software fault avoidance and tolerance 12.4.2 Software fault avoidance 12.4.3 Software fault tolerance |
245 | 13 Remark on “Confidence in the use of software tools” |
246 | 14 Guidance on safety-related special characteristics 14.1 General |
247 | 14.2 Identification of safety-related special characteristics 14.3 Specification of the control measures of safety-related special characteristics |
248 | 14.4 Monitoring of the safety-related special characteristics |
249 | Annex A (informative) Fault tree construction and applications |
252 | Bibliography |