16. IEC 61508-3

16.1. 4

  1. The Certification scope specifies and justifies the SIL.

  2. The certified library certification excludes the requirement of having an architecture.

    The certified libraries have no overall architecture and a rather simple high-level design. Each module provides functions and data structures around a single well-defined topic. All modules have a doc-comment describing the design and contents of the module.

16.2. 5

Covered by 5.2.1 to 5.2.11 of IEC 61508-1.

16.3. 6.2.1

Covered by 6.2 of IEC 61508-1.

16.4. 6.2.2

Covered by the Safety Plan.

16.5. 6.2.3

Covered by

16.6. 7.1.2.1-3

Covered by Safety Plan - Lifecycle Phases Overview.

16.7. 7.1.2.4-6

Covered by V-Model.

16.8. 7.1.2.7

Covered by IEC 61508-3 Annex A.

16.9. 7.1.2.8-9

The following relevant artefacts are included in the deliverables:

16.10. 7.2.2.1-3

Covered by Requirements Management.

16.11. 7.2.2.4

N/A

The certified libraries have no overall architecture and a rather simple high-level design. Each module provides functions and data structures around a single well-defined topic. All modules have a doc-comment describing the design and contents of the module.

All functions in all certified libraries are deemed to be of the same SIL.

16.12. 7.2.2.5

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.

16.13. 7.2.2.6-9

N/A; the certified libraries are pure software libraries. Hardware constraints should be taken into consideration when integrating the certified libraries into a hardware environment.

16.14. 7.2.2.11

N/A;

The certified libraries are delivered as pre-compiled libraries and have to be statically linked into applications (see LIBS_CSTR_0080_LINK_STATIC). There is no way to configure a certified library binary after it is compiled and linked statically.

16.15. 7.2.2.12-13

N/A; the certified libraries do not use, and therefore do not configure, any pre-existing software.

16.16. 7.3.2.1-5

The certified libraries are tested as laid out in the Testing Plan, and those test results, for all qualified targets, are available in the Test results overview.

16.17. 7.4.2.1

Covered by Responsibility split.

16.18. 7.4.2.2-6

Covered by Doc-comments in the certified libraries.

16.19. 7.4.2.7

N/A, because the certified libraries are libraries and do not build on top of a pre-existing component.

16.20. 7.4.2.8-11

All functions in all certified libraries are deemed to be of the same SIL.

16.21. 7.4.2.12-14

N/A, because the certified libraries are libraries and do not build on top of a pre-existing component.

16.22. 7.4.3

N/A, therefore no architecture is needed

The certified libraries have no overall architecture and a rather simple high-level design. Each module provides functions and data structures around a single well-defined topic. All modules have a doc-comment describing the design and contents of the module.

16.23. 7.4.4.1-9

Covered by Tool safety assessments.

16.24. 7.4.4.10-11

Covered by Programming language.

16.25. 7.4.4.12-13

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.

16.26. 7.4.4.14

N/A; Rust macros are not automatic code generation, since they are written in source code.

16.27. 7.4.4.15-18

Covered by Configuration.

16.28. 7.4.4.19

Covered by Roles and responsibilities.

16.29. 7.4.5.1-2

Covered by Responsibility split.

16.30. 7.4.5.3-5

The certified libraries have no overall architecture and a rather simple high-level design. Each module provides functions and data structures around a single well-defined topic. All modules have a doc-comment describing the design and contents of the module.

16.31. 7.4.6

Covered by Responsibility split.

16.32. 7.4.7-8

The certified libraries are tested as laid out in the Testing Plan, and those test results, for all qualified targets, are available in the Test results overview.

16.33. 7.5

The certified libraries are tested as laid out in the Testing Plan, and those test results, for all qualified targets, are available in the Test results overview.

16.34. 7.6

See 7.8.

16.35. 7.7.1

Objective met.

16.36. 7.7.2.1-4

The certified libraries are tested as laid out in the Testing Plan, and those test results, for all qualified targets, are available in the Test results overview.

16.37. 7.7.2.5-6

Covered by Unit tests.

16.38. 7.7.2.7-9

The certified libraries are tested as laid out in the Testing Plan, and those test results, for all qualified targets, are available in the Test results overview.

16.39. 7.8

Covered by

16.40. 7.9.1

Objective met.

16.41. 7.9.2.1-7

The certified libraries are tested as laid out in the Testing Plan, and those test results, for all qualified targets, are available in the Test results overview.

16.42. 7.9.2.8

N/A; There is no system, only software requirements.

16.43. 7.9.2.9

N/A; There is no architecture design.

16.44. 7.9.2.10-13

The certified libraries are tested as laid out in the Testing Plan, and those test results, for all qualified targets, are available in the Test results overview.

16.45. 7.9.2.14

N/A; Timing performance depends on the system requirements, which are unknown during the certification phase.

16.46. 8.1-3

Covered by Safety Assessment.