Lines Matching +full:requirements +full:- +full:base
9 This document is the safety documentation providing an overview over the safety-relevant activities
26 This document is a living document and may evolve over time as new requirements, guidelines, or
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
57 electrical, electronic, and programmable electronic safety-related systems. Here's an overview of
69 includes the identification of safety requirements, the development of a safety plan, and the
74 safety-related system to ensure that it meets the specified SIL and other safety requirements.
79 documentation process to ensure that all aspects of the safety-related system are fully
80 documented and that there is full traceability from the safety requirements to the final system
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
92 base for specific standards for different industries. This makes IEC 61508 particularly relevant
99 .. figure:: images/IEC-61508-basis.svg
102 :figclass: align-center
109 Quality is a mandatory expectation for software across the industry. The code base of the project
110 must achieve various software quality goals in order to be considered an auditable code base from a
113 as an existing pre-condition and therefore the "quality managed" status should be pursued for any
115 which need to be reached to achieve an auditable code base:
120 b. :ref:`safety_requirements` and requirements tracing
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
150 Requirements and requirements tracing
151 -------------------------------------
153 Requirements and requirement management are not only important for software development, but also
157 purpose, tracing the requirements down to the code level is used. With the requirements management
161 Also the IEC 61508 standard highly recommends (which is like a must-have for the certification)
162 requirements and requirements tracing.
165 -------------
171 requirements apply to safety for test coverage, and various metrics must be considered, which are
188 base can be used as auditable code. However, most of these software architecture designs have
193 --------------------------
200 very high level, and thus it can be determined which functionalities are safety-relevant and can be
205 -----------------------
208 The most important aspect is the separation of safety-relevant components from non-safety-relevant
213 ------------------------------------------------------------------------------
224 .. figure:: images/zephyr-safety-process.svg
227 :figclass: align-center
238 represents a small subset of the entire code base. This subset should then be made auditable
242 that the architecture meets the safety requirements.
246 and decisions of minor changes in the safety scope to be able to react to safety-relevant
248 influential change or improvement that requires extended discussion or decision-making, the
253 #. This section describes the certification side. At this point, the code base has to be in an
254 "auditable" state, and ideally no further changes should be necessary or made to the code base.