38. EN 50716¶
38.1. 4¶
Covered by the following subsections.
38.2. 4.1¶
N/A; there is no system in which the certified libraries are embedded during their certification.
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.
38.3. 4.2-3¶
All functions in all certified libraries are deemed to be of the same software integrity level, see Systematic capabilities. The certified libraries are targeting SIL 2, see Certification scope.
38.4. 4.4¶
Covered by Systematic capabilities: every public function of the certified subset is considered safety related and is targeting SIL 2.
38.5. 4.5¶
Covered by this norm mapping and by Safety Assessment.
38.6. 4.6-9¶
The selection of the techniques and measures of Annex A, including the justification for every deviation from a highly recommended (HR) technique and for every technique not contained in the tables, is documented in EN 50716 Annex A.
38.7. 4.10¶
Covered by this norm mapping and by Safety Assessment.
38.8. 4.11¶
N/A; the certified libraries are assessed against this document, they are not re-used software developed according to EN 50128 or EN 50657.
38.9. 5¶
Covered by the following subsections.
38.10. 5.1.1¶
Covered by
38.11. 5.1.2.1¶
Ferrous Systems is ISO 9001:2015 certified. See Qualification Plan - Ferrocene Organization.
38.12. 5.1.2.2¶
Intentionally left blank in the standard.
38.13. 5.1.2.3¶
Covered by Qualification Plan - Ferrocene Organization.
38.14. 5.1.2.4-7¶
Covered by Safety Assessment: the Assessor is TÜV SÜD, an independent assessment body which is organizationally independent from the project team.
38.15. 5.1.2.8¶
Covered by
The release decision is taken by the Release Manager after reviewing the evidence, see Qualification Plan - Ferrocene Organization.
38.16. 5.1.2.9-12¶
Covered by
The upstream Rust project specifies, designs and implements the certified libraries; Ferrous Systems performs the verification and the testing of the code it receives. Every change is reviewed by an expert who was not involved in the change.
38.17. 5.2.1¶
Covered by Roles and responsibilities.
38.18. 5.2.2.1¶
The key competencies of Annex B are covered by the roles described in Qualification Plan - Ferrocene Organization. No additional competencies are required, therefore nothing is added to the Software Quality Assurance Plan.
38.19. 5.2.2.2-4¶
Covered by
38.20. 5.2.2.5¶
Covered by
The responsibilities and competencies of the roles in Annex B are allocated there.
38.21. 5.3.1¶
Covered by Lifecycle Phases Overview.
38.22. 5.3.2.1¶
Covered by Lifecycle Phases Overview.
38.23. 5.3.2.2-3¶
Covered by
The deviations from the ideal lifecycle (as compared to certification of an existing project) are documented in V-Model.
38.24. 5.3.2.4¶
The plans required by this document are distributed over the Ferrocene certification documentation:
Document of EN 50716 |
Ferrocene document |
|---|---|
Software Quality Assurance Plan |
|
Software Verification Plan |
|
Software Validation Plan |
|
Software Configuration Management Plan |
|
Software Maintenance Plan |
|
Software Assessment Plan and Report |
Written by the external Assessor, see Safety Assessment |
38.25. 5.3.2.5¶
Covered by Lifecycle Phases Overview.
38.26. 5.3.2.6¶
All documentation is part of the Ferrocene documentation package and is versioned together with the code (see Change Tracking).
38.27. 5.3.2.7¶
Covered by
38.28. 5.3.2.8¶
All documents of the Ferrocene documentation package share one glossary and are reviewed together (Qualification Plan - Documentation Validation).
38.29. 5.3.2.9¶
Covered by Qualification Plan - Documentation Validation.
38.30. 5.3.2.10¶
All documents of the Ferrocene documentation package share one glossary and are reviewed together (Qualification Plan - Documentation Validation).
38.31. 5.3.2.11¶
All documentation is part of the Ferrocene documentation package and is versioned together with the code (see Change Tracking).
38.32. 5.3.2.12-13¶
The documents are combined as listed in the table of 5.3.2.4; the parts produced by independent roles are reviewed independently (see Responsibility split).
38.33. 5.3.2.14¶
Covered by Safety Assessment.
38.34. 6¶
Covered by the following subsections.
38.35. 6.1.1-3¶
The test specifications are the test suites in the source code, described in Testing Plan; the test reports are the test results.
There are no separate test specification documents for the software/hardware integration level, see 7.3.4.34-40.
38.36. 6.1.4.1¶
Covered by Responsibility split: most tests are written by the upstream Rust project and are accepted by Ferrous Systems after review; the rationale is documented there.
38.37. 6.1.4.2¶
Covered by
No measurement equipment is used; testing is performed on real targets and emulators, both listed in the tool safety assessments.
38.38. 6.1.4.3-5¶
Covered by
Deviation: the Test Specification is the test suite source code (test cases, test data and expected results are the assertions), and the Test Report is the CI test report, which also records the identity and configuration of all items involved.
38.39. 6.2.1-4¶
Covered by Development Process and Testing Plan.
38.40. 6.2.4.1-4¶
Covered by Development Process; the verification results are retained by the CI infrastructure, see Storing Test Results.
38.41. 6.2.4.5¶
The techniques and measures chosen from Table A.5, Table A.6 and Table A.7 are documented in EN 50716 Annex A.
38.42. 6.2.4.6-9¶
Covered by
Performance requirements are not verified at library level, see 7.9.2.14 of IEC 61508-3.
38.43. 6.2.4.10-11¶
The verification of the plans is part of the safety assessment, see Safety Assessment.
38.44. 6.2.4.12-13¶
Covered by
The identity and configuration of the verified items is recorded in the CI artifacts (see Configuration).
38.45. 6.3.1-3¶
Covered by Validation Process.
Ferrous Systems does not appoint a separate Validator; the independence is achieved by the split of responsibilities between the upstream Rust project and Ferrous Systems (see Responsibility split) and by the independent Assessor.
38.46. 6.3.4.1-3¶
Covered by Validation Process.
Ferrous Systems does not appoint a separate Validator; the independence is achieved by the split of responsibilities between the upstream Rust project and Ferrous Systems (see Responsibility split) and by the independent Assessor.
38.47. 6.3.4.4-6¶
Covered by
Only dynamic testing (real targets and emulators) is used; no static, analytical or statistical validation techniques are applied beyond the code coverage measurement.
38.48. 6.3.4.7-11¶
Covered by
The validated software baseline is the released Ferrocene version (see 9.1.4.2-3).
38.49. 6.3.4.12-14¶
Covered by Safety Assessment and Release Process. Simulation and modelling are not used.
38.50. 6.4.1-3¶
Covered by Safety Assessment: the assessment is performed by TÜV SÜD as the independent Assessor.
38.51. 6.4.4.1¶
Covered by Safety Assessment: the assessment is performed by TÜV SÜD as the independent Assessor.
38.52. 6.4.4.2¶
Not used; no previously assessed software is re-used (see 7.3.4.7-8). Every Ferrocene release undergoes a new assessment, see Release cadence.
38.53. 6.4.4.3¶
Covered by Deliverables and Documents.
38.54. 6.4.4.4-5¶
The Software Assessment Plan is written by the Assessor, based on the deliverables listed in Deliverables and Documents.
38.55. 6.4.4.6-7¶
The application conditions of the certified libraries are documented in Constraints; the applied techniques of Annex A are documented in EN 50716 Annex A.
38.56. 6.4.4.8¶
Covered by Configuration and Change Tracking.
38.57. 6.4.4.9¶
Covered by Qualification Plan - Ferrocene Organization.
38.58. 6.4.4.10-13¶
Covered by
38.59. 6.4.4.14-17¶
The Software Assessment Report is written by the Assessor, based on the evidence provided in the deliverables (see Deliverables and Documents).
38.60. 6.5.1-3¶
Covered by the documents listed in 5.3.2.4 and by
The techniques and measures of Table A.9 are documented in EN 50716 Annex A.
38.61. 6.5.4.1-6¶
Covered by the documents listed in 5.3.2.4 and by
The techniques and measures of Table A.9 are documented in EN 50716 Annex A.
38.62. 6.5.4.7-8¶
Intentionally left blank in the standard.
38.63. 6.5.4.9¶
All planning documents are updated through the same process as the code, see Change Tracking and New Features and Bug Fixes.
38.64. 6.5.4.10-12¶
Covered by
The complete development and test environment is delivered to the customer in the ferrocene-src component, which allows reproducing every release.
38.65. 6.5.4.13¶
N/A; no external suppliers are involved, see 6.2.17 of IEC 61508-1.
The upstream Rust project is not an external supplier: its contributions are integrated and verified like every other change, as described in Responsibility split.
38.66. 6.5.4.14-17¶
Covered by
Code which cannot be traced or tested is annotated and justified, see Manual test coverage.
38.67. 6.5.4.18¶
Covered by Responsibility split: the upstream Rust project develops the libraries, Ferrous Systems performs the certification activities. The interface between both is documented there.
38.68. 6.6.1-3¶
Covered by Change Tracking and Development Process.
38.69. 6.6.4.1¶
Covered by
Impact analysis is not performed per change: the complete test suite of all certified libraries is executed for every change, therefore no re-verification scope has to be determined.
38.70. 6.6.4.2¶
Covered by Re-verification scope and Development Process.
38.71. 6.7.1-3¶
Covered by Tool safety assessments, which also classifies the tools into T1, T2 and T3.
38.72. 6.7.4.1-3¶
Covered by Tool safety assessments (usage, version and safety assessment of every tool).
38.73. 6.7.4.4-5¶
Covered by Tool safety assessments; the compiler is pre-qualified (see Ferrocene Evaluation Plan), therefore no tool validation is performed for it.
38.74. 6.7.4.6-8¶
Intentionally left blank in the standard.
38.75. 6.7.4.9¶
The Ferrocene compiler is the only automatic translator used; it is qualified as described in Ferrocene Evaluation Plan and Tool Analysis.
38.76. 6.7.4.10-11¶
Covered by Configuration: all tools and their versions are pinned in the versioned build environment (ferrocene-src), and the tool versions are re-assessed for each release.
38.77. 6.7.4.12¶
Covered by Tool safety assessments.
38.78. 7¶
Covered by the following subsections.
38.79. 7.1.1¶
Covered by V-Model.
38.80. 7.1.2.1¶
The documents of Table A.1 are listed in EN 50716 Annex A and provided as described in Deliverables and Documents.
38.81. 7.1.2.2¶
Covered by V-Model.
38.82. 7.2.1-3¶
Covered by Requirements Management: the doc-comments plus the function signature are the Software Requirements Specification of each function.
Robustness and maintainability requirements are covered by Programming language and Lifecycle Phases Overview.
38.83. 7.2.4.1-5¶
Covered by Requirements Management: the doc-comments plus the function signature are the Software Requirements Specification of each function.
Robustness and maintainability requirements are covered by Programming language and Lifecycle Phases Overview.
38.84. 7.2.4.13¶
Covered by Requirements Management: the doc-comments plus the function signature are the Software Requirements Specification of each function.
Robustness and maintainability requirements are covered by Programming language and Lifecycle Phases Overview.
38.85. 7.2.4.6¶
Covered by the Certified standard library API docs, which document all public interfaces of the certified libraries. There are no interfaces to any other system.
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.
38.86. 7.2.4.7-8¶
The behaviour of every function, including its failure behaviour (panic), is documented in its doc-comment, see Doc-comments in the certified libraries. The user shall compile with -C panic=abort, see LIBS_CSTR_0020_PANIC_ABORT.
There is no programmable electronics in the certification scope.
38.87. 7.2.4.9¶
The constraints between the certified libraries and their environment are documented in Constraints (e.g. static linking, matching compiler version).
38.88. 7.2.4.10¶
N/A; there is no hardware to be checked by the software.
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.
38.89. 7.2.4.11-12¶
N/A for periodic testing and for testability during overall system operation: the overall system is unknown at certification time, see 7.9.2.14 of IEC 61508-3.
All functions of the certified subset are testable and tested, see Code coverage report.
38.90. 7.2.4.14¶
N/A; no function of the certified libraries can be configured by application data.
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.
38.91. 7.2.4.15¶
The techniques and measures chosen from Table A.2 are documented in EN 50716 Annex A.
38.92. 7.2.4.16-19¶
Covered by Testing Plan: the Overall Software Test Specification is the set of unit test, doc-test and integration test suites executed by the CI for every change on all qualified targets.
Out-of-specification inputs (7.2.4.19 d)) are covered by the tests of panics and error paths, see Unit tests and Code coverage report.
38.93. 7.2.4.20-22¶
Covered by
The requirements are re-checked for every release during the semantic diff (see Safety Case).
38.94. 7.3.1-3¶
N/A; no Software Architecture Specification and no Software Design Specification document is written, see 7.3.4.1-3 below.
38.95. 7.3.4.1-3¶
N/A; no Software Architecture Specification is written.
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.
The feasibility of the required integrity level is argued in Systematic capabilities.
38.96. 7.3.4.10¶
N/A; no Software Architecture Specification is written.
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.
The feasibility of the required integrity level is argued in Systematic capabilities.
38.97. 7.3.4.12¶
N/A; no Software Architecture Specification is written.
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.
The feasibility of the required integrity level is argued in Systematic capabilities.
38.98. 7.3.4.14¶
N/A; no Software Architecture Specification is written.
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.
The feasibility of the required integrity level is argued in Systematic capabilities.
38.99. 7.3.4.4¶
N/A; there is no hardware in the certification scope, see Alloc library for the allocator interface which must be implemented by the user.
38.100. 7.3.4.5-6¶
All software components (modules) of the certified libraries are identified in the Certified standard library API docs and in Subset. They are all new from the point of view of this certification and are individually versioned by git, see Configuration.
38.101. 7.3.4.7-8¶
N/A; the certified libraries are handled as a new development, they do not integrate pre-existing software elements (see 8-12 of ISO 26262 Applicable clauses).
38.102. 7.3.4.9¶
All functions in all certified libraries are deemed to be of the same software integrity level, therefore no evidence of non-interference between different levels is needed.
38.103. 7.3.4.11¶
Fault avoidance is achieved by the language and the tooling, see Programming language. Possible failures and their mitigation are analysed in Failure analysis.
38.104. 7.3.4.13¶
N/A; the certified libraries contain no application data.
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.
38.105. 7.3.4.15¶
Intentionally left blank in the standard.
38.106. 7.3.4.16-17¶
N/A; no prototyping is used in the development of the certified libraries.
38.107. 7.3.4.18-19¶
Covered by the Certified standard library API docs (function signatures and doc-comments).
The Rust type system defines the valid values of every interface; boundary values and the behaviour when they are exceeded (panic, wrapped result) are part of the doc-comments, see Doc-comments in the certified libraries. Unused and forbidden equivalence classes cannot be constructed for most types due to strong typing.
38.108. 7.3.4.20-24¶
Covered by Architecture and software design: the module doc-comments are the Software Design Specification.
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.
The techniques and measures chosen from Table A.4 are documented in EN 50716 Annex A.
38.109. 7.3.4.25¶
Covered by Programming language; the criteria of Table A.15 are assessed in EN 50716 Annex A.
38.110. 7.3.4.26-28¶
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.
As such, the certified libraries do not have a coding standard of their own; the implicit upstream standards are enforced by the tidy test suite and the lints, see rustc lints.
38.111. 7.3.4.29¶
Covered by Programming language (modularity, encapsulation, data structures) and Systematic capabilities (verifiability through coverage).
38.112. 7.3.4.30-33¶
Covered by Integration tests: the certified libraries are integrated and tested by building and testing the other components of the Ferrocene toolchain on all supported platforms. The results of the component tests that are re-used are the unit test suites, see Re-verification scope.
38.113. 7.3.4.34-40¶
N/A; there is no hardware in the certification scope.
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.
38.114. 7.3.4.41-44¶
Covered by
Development Process (independent review of every change)
Safety Case (semantic diff for every release)
38.115. 7.4.1-3¶
Covered by the module doc-comments and the test suites, see Architecture and software design and Unit tests.
38.116. 7.4.4.1-6¶
Covered by the module doc-comments and the source code, see Architecture and software design. Author, configuration history and description of every component are provided by git and the code review process (see Development Process).
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.
38.117. 7.4.4.7-10¶
Covered by Unit tests. The required criteria and degree of test coverage are defined in Lifecycle Phases Overview (100 % statement coverage) and justified in EN 50716 Annex A (Table A.21).
38.118. 7.4.4.11-13¶
Covered by
38.119. 7.5.1-3¶
Covered by Testing Plan and Configuration.
38.120. 7.5.4.1-4¶
Covered by
Configuration (all source code is under configuration control before testing)
Programming language (size and complexity: compiler recursion limit, discouraged many-parameter functions)
38.121. 7.5.4.5-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.
The statement of test coverage per component is provided by Code coverage report.
38.122. 7.5.4.8-10¶
Covered by
rustc lints and the
tidytest suite (Tidy test suite)
The correct application of the coding standard is verified by these lints, see 7.3.4.26-28.
38.123. 7.6.1-3¶
Covered by Integration tests and Testing Plan.
38.124. 7.6.4.1-2¶
Covered by Integration tests and Development Process. Every change triggers a complete rebuild and re-test, therefore the impact study of 7.6.4.2 always covers the whole test suite (see Re-verification scope).
38.125. 7.6.4.3-6¶
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.
The identity and configuration of all items involved is recorded in the CI artifacts (see Configuration).
38.126. 7.6.4.7-10¶
N/A; there is no hardware in the certification scope.
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.
38.127. 7.6.4.11-13¶
Covered by Test results overview and Safety Case.
38.128. 7.7.1-3¶
Covered by Testing Plan and Safety Case.
38.129. 7.7.4.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.
The Overall Software Test Specification and Report are the complete Ferrocene test suite and its results on all qualified targets; there is no separate overall test document.
38.130. 7.7.4.5¶
Covered by Infrastructure: the tests are executed on real hardware targets and on emulators, listed in all qualified targets. Simulated environments are only used for bare metal targets, see Bare metal testing.
38.131. 7.7.4.6-10¶
Covered by
The evaluation of the applied techniques and measures is documented in EN 50716 Annex A.
38.132. 7.7.4.11-12¶
Covered by
38.133. 8¶
N/A; the certified libraries are not configurable by application data, therefore Clause 8 does not apply.
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.
This also covers 7.2.4.14 and Table A.11.
38.134. 9¶
Covered by the following subsections.
38.135. 9.1.1-3¶
The certified libraries are delivered as pre-compiled, statically linked libraries; their deployment into a target system is performed by the customer.
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.
38.136. 9.1.4.1¶
Covered by Release Process; the deployment in the final environment of application is under the responsibility of the user of the certified libraries.
38.137. 9.1.4.2-3¶
Covered by Configuration: every release is uniquely identified and the ferrocene-src component contains everything needed to reproduce it, including the pre-existing and previously developed parts.
38.138. 9.1.4.4-5¶
Intentionally left blank in the standard.
38.139. 9.1.4.6-7¶
Covered by Installation Procedures (Installation Procedures) and Installing Ferrocene.
38.140. 9.1.4.8-9¶
Covered by the constraint to use matching versions of the certified libraries and rustc, see LIBS_CSTR_0040_MATCHING_VERSION, and by static linking only, see LIBS_CSTR_0080_LINK_STATIC.
38.141. 9.1.4.10¶
N/A for the certified libraries themselves: a rollback is achieved by re-installing a previous Ferrocene release, which is only performed as a whole (see Installation Validation).
38.142. 9.1.4.11¶
N/A; the certified libraries are statically linked into the application binary and are not loaded at run-time. Their identity is established through the matching versions constraint, see LIBS_CSTR_0040_MATCHING_VERSION.
38.143. 9.1.4.12-14¶
The deployment records and the traceability to delivered installations are the responsibility of the customer, since the installations are unknown at certification time.
Covered on the Ferrocene side by Change Tracking (traceability up to delivery) and by Installation Validation.
38.144. 9.1.4.15¶
N/A; fault monitoring is a system level activity. The certified libraries report failures by panicking, which is documented per function in the API docs (see LIBS_CSTR_0020_PANIC_ABORT).
38.145. 9.1.4.16-19¶
Intentionally left blank for 9.1.4.19; otherwise covered by Installation Procedures and Safety Assessment.
38.146. 9.1.4.20¶
Covered by Installation Validation (checking that the archives were extracted correctly) and by Configuration (hashes of all packages of the build environment).
38.147. 9.2.1-3¶
Covered by Patching process and Internal procedures: corrections, enhancements and adaptations are performed with the same process, tools and documentation as the initial development.
38.148. 9.2.4.1-3¶
Covered by Patching process: for every change it is decided whether it falls within the scope of a patch release or requires assessor review, and this decision is recorded.
Maintenance is performed with the same process as the development (see 9.2.4.15-17).
38.149. 9.2.4.4¶
Covered by Programming language and Architecture and software design.
38.150. 9.2.4.5-6¶
Covered by
The techniques and measures of Table A.10 are documented in EN 50716 Annex A.
38.151. 9.2.4.7-10¶
Covered by
Change Tracking (git history, change records, release identification)
Re-verification scope (re-validation and regression testing: the complete test suite is executed for every change)
38.152. 9.2.4.11-14¶
Covered by Development Process (review of every change, including its documentation) and Safety Assessment.
38.153. 9.2.4.15-17¶
Covered by Internal procedures: maintenance uses the same tools, infrastructure, review process and configuration management as the initial development.
38.154. 9.2.4.18¶
N/A; no external suppliers are involved.
38.155. 9.2.4.19-20¶
Covered by
Known Problems Tracking (severity tagging and impact of every known problem)
Known Problems (workaround, detection and mitigation strategies)