18. IEC 61508-3 Annex B¶
18.1. Table B.1 - Design and coding standards¶
18.1.1. 1¶
The Rust project has extensive measures (lints and tests) in place to assure quality and consistency of the codebase. The certified libraries use the same implicit standards as are ensured in the upstream codebase, to minimize divergence. Increased divergence from upstream leads to a higher maintenance burden and is a source of potential bugs.
18.1.2. 2, 5, 7, 8¶
Covered by Programming language.
18.2. Table B.2 - Dynamic analysis and testing¶
18.2.1. 1¶
The test cases in unit test test suites are crafted with a lot of care. Ferrous Systems did not do a full review to ensure boundary and extreme values are always tested. But achieving 100% region coverage will ensure all code paths have been executed and no untested code exists due to no test with a specific input.
18.2.2. 7b¶
Covered by Code coverage report.
18.3. Table B.3 - Functional and black-box testing¶
18.3.1. 4¶
The test cases in unit test test suites are crafted with a lot of care. Ferrous Systems did not do a full review to ensure boundary and extreme values are always tested. But achieving 100% region coverage will ensure all code paths have been executed and no untested code exists due to no test with a specific input.
18.4. Table B.4 - Failure analysis¶
18.4.1. 3¶
Covered by Failure analysis.
18.5. Table B.5 - Modelling¶
18.5.1. 3¶
N/A
Ferrous Systems certifies the certified libraries as libraries, to be used in other systems whose requirements are unknown. Users of the certified libraries should consider their specific system safety requirements when developing safety related software with the certified libraries.
18.6. Table B.6 - Performance testing¶
18.6.1. 2-3¶
N/A
Ferrous Systems certifies the certified libraries as libraries, to be used in other systems whose requirements are unknown. Users of the certified libraries should consider their specific system safety requirements when developing safety related software with the certified libraries.
18.7. Table B.7 - Semi-formal methods¶
Covered by Requirements Management.
18.8. Table B.8 - Static analysis¶
18.8.1. 3-4¶
Covered by Programming language.
18.9. Table B.9 - Modular approach¶
18.9.1. 1, 3, 4, 5, 6¶
Covered by Programming language.