Lines Matching +full:non +full:- +full:standard
9 This document is the safety documentation providing an overview over the safety-relevant activities
20 is, what standard we aim to achieve and what quality standards and processes need to be implemented
41 <https://en.wikipedia.org/wiki/IEC_61508>`__ standard and the Safety Integrity Level (SIL) 3 /
43 code base is pre-existing, we use the route 3s/1s approach defined by the IEC 61508 standard.
46 *Assessment of non-compliant development. Which is basically the route 1s with existing
50 *Compliant development. Compliance with the requirements of this standard for the avoidance and
53 Summarization IEC 61508 standard
56 The IEC 61508 standard is a widely recognized international standard for functional safety of
57 electrical, electronic, and programmable electronic safety-related systems. Here's an overview of
58 some of the key safety aspects of the standard:
60 #. **Hazard and Risk Analysis**: The IEC 61508 standard requires a thorough analysis of potential
64 #. **Safety Integrity Level (SIL)**: The standard introduces the concept of Safety Integrity Level
68 #. **System Design**: The IEC 61508 standard requires a systematic approach to system design that
73 #. **Verification and Validation**: The standard requires rigorous testing and evaluation of the
74 safety-related system to ensure that it meets the specified SIL and other safety requirements.
78 #. **Documentation and Traceability**: The IEC 61508 standard requires a comprehensive
79 documentation process to ensure that all aspects of the safety-related system are fully
83 Overall, the IEC 61508 standard provides a framework for the design, development, and
84 implementation of safety-related systems that aims to reduce the risk of accidents and improve
85 overall safety. By following the standard, organizations can ensure that their safety-related
90 The IEC 61508 standard was selected because it serves as a foundational functional safety standard
96 The following diagram illustrates the relationship between the IEC 61508 standard and other related
99 .. figure:: images/IEC-61508-basis.svg
102 :figclass: align-center
113 as an existing pre-condition and therefore the "quality managed" status should be pursued for any
129 Basic software quality standards - Safety view
133 pre-condition and what needs to be done to achieve an auditable code base from the safety
138 -----------------
147 Also the **IEC 61508 standard** sets a pre-condition and recommendation towards the use of coding
157 but not enforced. Rules are not yet enforced in CI and pull-requests cannot be
161 Reviewers/approvers can block pull-requests due to violations of the coding guidelines
162 in pull-requests across the codebase.
188 <https://github.com/zephyrproject-rtos/zephyr/issues/58903>`__ is being worked on.
191 -------------------------------------
201 Also the IEC 61508 standard highly recommends (which is like a must-have for the certification)
205 -------------
212 prescribed by the IEC 61508 standard for the SIL 3 / SC3 target. The following must be fulfilled,
233 --------------------------
235 The **IEC 61508 standard** strongly recommends a modular approach to software architecture. This
240 very high level, and thus it can be determined which functionalities are safety-relevant and can be
245 -----------------------
248 The most important aspect is the separation of safety-relevant components from non-safety-relevant
253 ------------------------------------------------------------------------------
264 .. figure:: images/zephyr-safety-process.svg
267 :figclass: align-center
286 and decisions of minor changes in the safety scope to be able to react to safety-relevant
288 influential change or improvement that requires extended discussion or decision-making, the
305 during the certification, and which are prescribed by the certifying authority and the standard