Workflow Verification

Create/Perform Unit Test		status: valid
status: valid tags: implementation has: doc_concept__verification__process, doc_getstrt__verification__process needs input: wp__sw_implementation, wp__verification__plan outputs: wp__verification__sw_unit_test responsible: rl__contributor approved by: rl__committer supported by: rl__safety_manager
[TODO: add :has: doc_concept__imp__concept, doc_getstrt__imp__getstrt after PR #526 is merged] Every Unit shall have at least one Unit Test. They verify the detailed design of the implementation. Unit tests are automatically executed as part of the CI after PR merge. In case of changes at inputs, the workflow need to be executed again as part of maintenance. Any contributor can create a component test and create a PR for it. During the review process the test cases will be approved by a committer. Committer and contributor need to differ. The actual Committer (rl__committer) of the implementation can also be the creator of the unit tests. Independence is achieved by different approver at PRs and by the Module Verification Report (wp__verification__module_ver_report).
wf__verification__unit_test		Workflow

Create/Maintain Component Test		status: valid
status: valid tags: verification contains: gd_req__link_tests, gd_guidl__verification_specification has: doc_concept__verification__process, doc_getstrt__verification__process needs input: wp__requirements__comp, wp__requirements__comp_aou, wp__verification__plan outputs: wp__verification__component_test responsible: rl__contributor approved by: rl__committer supported by: rl__safety_manager
Component test cases are based on component requirements. Any contributor can create a component test and create a PR for it. During the review process the test cases will be approved by a committer. Committer and contributor need to differ. The tests are automatically executed as part of the CI after PR merge. In case of changes at inputs, the workflow need to be executed again as part of maintenance.
wf__verification__comp_test		Workflow

Create/Maintain Component Integration Test		status: valid
status: valid tags: verification contains: gd_req__link_tests, gd_guidl__verification_specification has: doc_concept__verification__process, doc_getstrt__verification__process needs input: wp__component_arch, wp__sw_implementation, wp__verification__plan outputs: wp__verification__comp_int_test responsible: rl__contributor approved by: rl__committer supported by: rl__safety_manager
Component Integration test cases are based on component architecture and detailed design of implementation. Any contributor can create a component integration test and create a PR for it. During the review process the test cases will be approved by a committer. Committer and contributor need to differ. The tests are automatically executed as part of the CI after PR merge. In case of changes at inputs, the workflow need to be executed again as part of maintenance.
wf__verification__comp_int_test		Workflow

Create/Maintain Feature Integration Test		status: valid
status: valid tags: verification contains: gd_req__link_tests, gd_guidl__verification_specification has: doc_concept__verification__process, doc_getstrt__verification__process needs input: wp__feature_arch, wp__requirements__feat, wp__requirements__feat_aou, wp__verification__plan outputs: wp__verification__feat_int_test responsible: rl__contributor approved by: rl__committer supported by: rl__safety_manager
Feature Integration test cases are based on feature requirements and architecture of a specific feature. Any contributor can create a feature integration test and create a PR for it. During the review process the test cases will be approved by a committer. Committer and contributor need to differ. The tests are automatically executed as part of the CI after PR merge. In case of changes at inputs, the workflow need to be executed again as part of maintenance.
wf__verification__feat_int_test		Workflow

Create/Maintain Platform Test		status: valid
status: valid tags: verification contains: gd_req__link_tests, gd_guidl__verification_specification has: doc_concept__verification__process, doc_getstrt__verification__process needs input: wp__requirements__stkh, wp__verification__plan outputs: wp__verification__platform_test responsible: rl__contributor approved by: rl__committer supported by: rl__safety_manager
Platform test cases are based on Stakeholder requirements. This is the highest test level. Any contributor can create a platform test and create a PR for it. During the review process the test cases will be approved by a committer. Committer and contributor need to differ. The tests are automatically executed as part of the CI after PR merge. In case of changes at inputs, the workflow need to be executed again as part of maintenance.
wf__verification__platform_test		Workflow

Create Verification Plan		status: valid
status: valid tags: verification contains: gd_guidl__verification_guide, gd_temp__verification__plan has: doc_concept__verification__process, doc_getstrt__verification__process needs input: wp__requirements__stkh, wp__platform_mgmt, wp__tool_eval outputs: wp__verification__plan responsible: rl__committer approved by: rl__technical_lead supported by: rl__safety_manager, rl__infrastructure_tooling_community
The verification plan is created by Committer (rl__committer). It clearly outlines all aspects of the verification activities, provide a roadmap for the verification efforts throughout the software development lifecycle. The plan should be dynamic and updated as needed throughout the project lifecycle by Maintain Verification Plan (wf__verification__plan_maintain).
wf__verification__plan		Workflow

Maintain Verification Plan		status: valid
status: valid tags: verification contains: gd_guidl__verification_guide, gd_temp__verification__plan has: doc_concept__verification__process, doc_getstrt__verification__process needs input: wp__verification__plan, wp__requirements__stkh, wp__platform_mgmt, wp__feature_arch, wp__requirements__feat, wp__requirements__feat_aou, wp__component_arch, wp__requirements__comp, wp__requirements__comp_aou, wp__tool_eval outputs: wp__verification__plan responsible: rl__committer approved by: rl__technical_lead supported by: rl__safety_manager, rl__infrastructure_tooling_community
The verification plan is maintained by Committer (rl__committer). The plan should be dynamic and updated as needed throughout the project lifecycle, as verification activities may be impacted, by new requirements, architectural decisions, introduction of tools. Note that during the initial creation of the verification plan in Create Verification Plan (wf__verification__plan) not every input down to component level may be available.
wf__verification__plan_maintain		Workflow

Create Module Verification Report		status: valid
status: valid tags: verification contains: gd_temp__mod_ver_report has: doc_concept__verification__process, doc_getstrt__verification__process needs input: wp__verification__plan, wp__requirements__comp, wp__requirements__comp_aou, wp__component_arch, wp__module_sw_release_note, wp__platform_mgmt, wp__sw_component_safety_analyses, wp__sw_component_dfa, wp__sw_arch_verification, wp__sw_code_inspect, wp__requirements__inspect, wp__verification__component_test, wp__verification__comp_int_test, wp__verification__sw_unit_test outputs: wp__verification__module_ver_report responsible: rl__committer approved by: rl__technical_lead supported by: rl__safety_manager, rl__infrastructure_tooling_community
The verification report is created and maintained by a Committer (rl__committer). It is based on the Verification Plan (wp__verification__plan) and covers all the components of a module. This includes their requirements, AoUs, Architecture, Detailed Design, Units, DFA, Safety Analyses, Unit Code coverage. The respective necessary test methods and rigor of their application is defined in the Verification Plan (wp__verification__plan). The report is valid for ONE version of a module.
wf__verification__mod_ver_report		Workflow

Create Platform Verification Report		status: valid
status: valid tags: verification contains: gd_temp__platform_ver_report has: doc_concept__verification__process, doc_getstrt__verification__process needs input: wp__verification__plan, wp__requirements__stkh, wp__requirements__feat, wp__requirements__feat_aou, wp__feature_arch, wp__platform_sw_release_note, wp__platform_mgmt, wp__feature_safety_analyses, wp__feature_dfa, wp__sw_arch_verification, wp__requirements__inspect, wp__verification__feat_int_test, wp__verification__platform_test outputs: wp__verification__platform_ver_report responsible: rl__committer approved by: rl__technical_lead supported by: rl__safety_manager, rl__infrastructure_tooling_community
The verification report is created and maintained by a Committer (rl__committer). It is based on the Verification Plan (wp__verification__plan) and covers all the selected features of a SW platform. This includes their requirements, AoUs, Architecture, DFA, Safety Analyses, The respective necessary test methods and rigor of their application is defined in the Verification Plan (wp__verification__plan) and Platform Management Plan (wp__platform_mgmt). The report is valid for ONE specific platform version baseline.
wf__verification__platform_ver_report		Workflow