This content is not included in
your SAE MOBILUS subscription, or you are not logged in.
Writing Good Technical Safety Requirements
Technical Paper
2016-01-0127
ISSN: 0148-7191, e-ISSN: 2688-3627
Annotation ability available
Sector:
Language:
English
Abstract
One of the key premises of the ISO 26262 functional safety standard is the development of an appropriate Technical Safety Concept for the item under development. This is specified in detail in Part 4 of the standard - Product development at the system level. The Technical safety requirements and the technical safety concept form the basis for deriving the hardware and software safety requirements that are then used by engineering teams for developing a safe product. Just like any other form of product development, making multiple revisions of the requirements are highly undesirable. This is primarily due to cost increases, chances of having inconsistencies within work products and its impact on the overall project schedule. Good technical safety requirements are in fact the foundation for an effective functional safety implementation. Presently the ISO 26262 standard does not provide any direct guidance on any specific method to derive technical safety requirements for a given safety goal for an item. This paper provides guidelines to come up with a comprehensive and concise set of Technical Safety Requirements using safety analyses techniques like FTA or FMEA. The paper is intended to support those safety engineers tasked with developing the technical safety concept. Additionally, the paper recognizes that in practice projects face challenges such as lack of stakeholder interest, multi-party development and missing or incomplete upstream work products. The paper captures these real world challenges and provides proposed solutions. The paper concludes by citing a few methods for Fault tolerant Time Interval (FTTI) determination at the ECU level; a key parameter that is critical for the effectiveness of the technical safety concept.
Recommended Content
Journal Article | Effective Functional Safety Concept Generation in the Context of ISO 26262 |
Technical Paper | Developing Functional Safety Requirements using Process Model Variables |
Technical Paper | ASIL Decomposition: The Good, the Bad, and the Ugly |
Authors
Topic
Citation
George, A., Taylor, W., and Nelson, J., "Writing Good Technical Safety Requirements," SAE Technical Paper 2016-01-0127, 2016, https://doi.org/10.4271/2016-01-0127.Also In
References
- International Standards 2011 ISO 26262 Functional safety for road vehicles Geneva, Switzerland
- Fault Tree Handbook Vesely William Dr
- Developing Functional Safety Requirements using Process Model Variables Krithivasan Gokul
- Implementation and Verification of Technical Safety Requirements for a Dynamic Torque Vectoring Feature in an Electronic Brake System Worden James , Schneider Michael , Traskov Adrian Dr
- Functional Safety Analysis at the Software Architecture Level Barnes Doug
- Virtualized Fault Injection Methods in the Context of the ISO 26262 Standard Reyes Victor
- Writing Software Requirements Specifications (SRS) Vie Donn Le , Jr
- Quantified Fault Tree Techniques for Calculating Hardware Fault Metrics According to ISO 26262 Das Nabarun