-
Notifications
You must be signed in to change notification settings - Fork 17
Description
What
Not started:
- 6-5.4.2
- 6-5.4.3
Action_27: No coding guideline for RUST exists. Coding standards need to be defined.
Action_74: Acceptance criteria for complexity metrics shall be defined to guarantee testability of the code. If a project deviates from process requirements, this can be argued in the project handbook.
Action_42: The acceptance criteria for the static code analysis (static, dynamic) shall be defined.
Action_75: The table “Quality Metrics” need to explain what is meant by 100%. E.g. 100% of Software Detailed Design/ Software Architecture Design remains unclear (100% of what?)
Missing metrics according to ISO 26262: on architectural design level (SW Integration testing) ISO 26262-6 requires measuring the “function and call coverage” (without a defined target value) to estimate the completeness of the tests.
How
No response
Estimates for realization
effort mostly outside of S-CORE
Category
- Affects Detailed Design
Requirements / Architecture
- Requirements / Architecture are not affected by this change?
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
Status