Fix Verification Audit Findings

[aschemmel-tech]

What

Not started:

• 6-9.4.3
• 6-9.4.4
• 6-9.4.5
• 6-10.4.2
• 6-10.4.3
• 6-10.4.4
• 6-10.4.5
• 6-10.4.6
• 6-10.4.7
• 6-11.4.2
• 6-11.4.3
• 8-9.4.2.2
• 8-9.4.2.3
• 8-9.4.2.4
• 8-9.4.3.2
• 8-9.4.3.3

Action_44: Provide an argumentation about which tests have been selected for a feature. Resolved during audit

Action_50: The Coverage target values as listed by table 37 need to described in more detail. E.g. what is meant by “Coverage of detailed/architectural design” (Sequence diagram coverage?)

Action_51: It needs to be clarified where the reference system is located physically (affecting e.g. access rights).

Action_80: The method description of interface-based testing needs to describe that the functionality e.g. of a feature is verified based on tests defined on the interfaces. Not only the correctness of the interface itself shall be verified.

Action_81: The meaning of the static code Analysis still needs to be explained

Action_82: Reference integration is triggered manually today. It shall be required that the reference integration is triggered if a component is changed (process verification requirement implemented as tool requirement CI).

How

No response

Estimates for realization

1 week

Category

• Affects Detailed Design

Requirements / Architecture

• Requirements / Architecture are not affected by this change?