Check tailoring of standard requirements for Verification

[masc2023]

Due to https://github.com/eclipse-score/process_description/pull/464/changes achieved 100% coverage for ISO26262 WPs and Standard Requirements.

Achievement is also based on tailoring out some standard requirements, which needs to be checked, if correct tailored out.
https://eclipse-score.github.io/process_description//main/process_areas/verification/guidance/verification_guideline.html#gd_guidl__verification_req_tailored

DoD:
Check in above PR, what has tailored out and may correct, if required.

Keep the coverage as shown here to 100%

May change process area or assignee, if does not concern Verification

[pahmann]

@masc2023, @aschemmel-tech and @PandaeDo would love to hear your feedback. To my perspective std_req__iso26262__software_1041 is only very limited related to actual verification and more about integration from units and dependencies. What I could imagine is to take the relevance with verification report as this demonstrates all requirements are traceable. What I would see most fitting is the Release management parts.

[masc2023]

@masc2023, @aschemmel-tech and @PandaeDo would love to hear your feedback. To my perspective std_req__iso26262__software_1041 is only very limited related to actual verification and more about integration from units and dependencies. What I could imagine is to take the relevance with verification report as this demonstrates all requirements are traceable. What I would see most fitting is the Release management parts.

Integration process is now defined as part of wp__platform_handbook, so I would just map it there, not to the notes, traceability I agree on verification report