docs: revise safety status of requirements - #736
Conversation
Derived from the [tool verification report](https://eclipse-score.github.io/score/main/score_tools/tools_documentation/doc_as_code.html), we now know what aspects of the tool are safety-relevant and which are not.
License Check Results🚀 The license check job ran with the Bazel command: bazel run --lockfile_mode=error //src:license-checkStatus: Click to expand output |
|
Documentation preview for this pull request is available at: |
|
discussed in call: ask process experts how to derive safety status from tool classification |
|
@a-zw can you argument for the tool_reqs why they should be QM now? As they were all ASIL_B before so if we downgrade them we need to argument this. @PandaeDo @aschemmel-tech please review this if you have time <3 |
PandaeDo
left a comment
There was a problem hiding this comment.
Would not agree on some classifications. You can check against the process requirements https://eclipse-score.github.io/process_description/main/process_areas/safety_analysis/safety_analysis_workproducts.html. If they comply to ISO 26262 I would rate them as ASIL B. In case that they are only comply to ASPICE I would rate them as QM.
📌 Description
Derived from the tool verification report, we now know what aspects of the tool are safety-relevant and which are not.
🚨 Impact Analysis
✅ Checklist