Requirements Engineering Workflows

For a detailed explanation of workflows and their role within the process model, please refer to the Introduction.

Create/Maintain Stakeholder requirements and SW-Platform AoU		status: valid
tags: requirements_engineering version: 1 contains: gd_temp__req_stkh_req, gd_temp__req_formulation has: doc_concept__req_process, doc_getstrt__req_process needs input: wp__policies, wp__issue_track_system outputs: wp__requirements_stkh, wp__requirements_sw_platform_aou responsible: rl__contributor approved by: rl__project_lead supported by: rl__safety_manager satisfied by: gd_req__req_structure, gd_req__req_attr_uid, gd_req__req_attr_title, gd_req__req_attr_description, gd_req__req_attr_type, gd_req__req_attr_safety, gd_req__req_attr_status, gd_req__req_attr_rationale, gd_req__req_attr_valid_from, gd_req__req_attr_valid_until, gd_req__req_linkage, gd_req__req_traceability, gd_req__req_attr_version, gd_req__req_suspicious, gd_req__req_check_mandatory, gd_req__req_desc_weak, gd_req__req_linkage_fulfill, gd_req__req_linkage_safety, gd_req__req_validity
Stakeholder requirements and SW-Platform Assumptions of Use (AoU) can be created during a change request. Any contributor can create a stakeholder requirement (or AoU) and propose it for approval.
wf__req_stkh_req		Workflow

Create/Maintain Feature requirements		status: valid
tags: requirements_engineering version: 1 contains: gd_temp__req_feat_req, gd_temp__req_formulation has: doc_concept__req_process, doc_getstrt__req_process needs input: wp__requirements_stkh, wp__issue_track_system outputs: wp__requirements_feat responsible: rl__contributor approved by: rl__architecture_community supported by: rl__safety_manager, rl__security_manager, rl__delivery_team satisfied by: gd_req__req_structure, gd_req__req_attr_uid, gd_req__req_attr_title, gd_req__req_attr_description, gd_req__req_attr_type, gd_req__req_attr_security, gd_req__req_attr_safety, gd_req__req_attr_status, gd_req__req_attr_valid_from, gd_req__req_attr_valid_until, gd_req__req_linkage, gd_req__req_linkage_aou, gd_req__req_traceability, gd_req__req_attr_impl, gd_req__req_attr_testlink, gd_req__req_attr_test_covered, gd_req__req_attr_version, gd_req__req_suspicious, gd_req__req_check_mandatory, gd_req__req_desc_weak, gd_req__req_linkage_fulfill, gd_req__req_linkage_architecture_mandatory, gd_req__req_linkage_architecture, gd_req__req_linkage_architecture_switch, gd_req__req_linkage_safety, gd_req__req_validity
Depending on the stakeholder requirements feature requirements can be derived. This can be done by any contributor and will be approved by the architecture community. If needed safety and security managers can provide support. In case of modification of already implemented feature requirements the feature delivery team will be consulted.
wf__req_feat_req		Workflow

Create/Maintain Feature AoUs		status: valid
tags: requirements_engineering version: 1 contains: gd_temp__req_aou_req, gd_temp__req_formulation has: doc_concept__req_process, doc_getstrt__req_process needs input: wp__requirements_feat, wp__feature_arch, wp__issue_track_system outputs: wp__requirements_feat_aou, wp__platform_safety_manual responsible: rl__contributor approved by: rl__committer supported by: rl__safety_manager, rl__security_manager satisfied by: gd_req__req_structure, gd_req__req_attr_uid, gd_req__req_attr_title, gd_req__req_attr_description, gd_req__req_attr_type, gd_req__req_attr_security, gd_req__req_attr_safety, gd_req__req_attr_status, gd_req__req_check_mandatory, gd_req__req_desc_weak
Based on the safety concept on feature level, feature AoUs can be derived. See also Workflow for Creating and Linking Assumption of Use (AoU)
wf__req_feat_aou		Workflow

Create/Maintain Component requirements		status: valid
tags: requirements_engineering version: 1 contains: gd_temp__req_comp_req, gd_temp__req_formulation has: doc_concept__req_process, doc_getstrt__req_process needs input: wp__requirements_feat, wp__issue_track_system outputs: wp__requirements_comp responsible: rl__contributor approved by: rl__committer supported by: rl__safety_manager, rl__security_manager satisfied by: gd_req__req_structure, gd_req__req_attr_uid, gd_req__req_attr_title, gd_req__req_attr_description, gd_req__req_attr_type, gd_req__req_attr_security, gd_req__req_attr_safety, gd_req__req_attr_status, gd_req__req_linkage, gd_req__req_linkage_aou, gd_req__req_traceability, gd_req__req_attr_impl, gd_req__req_attr_testlink, gd_req__req_attr_test_covered, gd_req__req_attr_version, gd_req__req_suspicious, gd_req__req_check_mandatory, gd_req__req_desc_weak, gd_req__req_linkage_fulfill, gd_req__req_linkage_architecture_mandatory, gd_req__req_linkage_architecture, gd_req__req_linkage_architecture_switch, gd_req__req_linkage_safety
wf__req_comp_req		Workflow

Create/Maintain Component AoUs		status: valid
tags: requirements_engineering version: 1 contains: gd_temp__req_aou_req, gd_temp__req_formulation has: doc_concept__req_process, doc_getstrt__req_process needs input: wp__requirements_comp, wp__component_arch, wp__issue_track_system outputs: wp__requirements_comp_aou, wp__module_safety_manual responsible: rl__contributor approved by: rl__committer supported by: rl__safety_manager, rl__security_manager satisfied by: gd_req__req_structure, gd_req__req_attr_uid, gd_req__req_attr_title, gd_req__req_attr_description, gd_req__req_attr_type, gd_req__req_attr_security, gd_req__req_attr_safety, gd_req__req_attr_status, gd_req__req_check_mandatory, gd_req__req_desc_weak
Based on the safety concept on component level, component AoUs can be derived. See also Workflow for Creating and Linking Assumption of Use (AoU)
wf__req_comp_aou		Workflow

Create/Maintain Tool Requirements		status: valid
tags: requirements_engineering version: 1 contains: gd_temp__req_tool_req, gd_temp__req_formulation has: doc_concept__req_process, doc_getstrt__req_process needs input: wp__process_description outputs: wp__requirements_proc_tool responsible: rl__contributor approved by: rl__committer supported by: rl__safety_manager, rl__security_manager satisfied by: gd_req__req_structure, gd_req__req_attr_uid, gd_req__req_attr_title, gd_req__req_attr_description, gd_req__req_linkage, gd_req__req_traceability, gd_req__req_check_mandatory, gd_req__req_desc_weak
Based on the process descriptions (which comply to standards) and/or stakeholder/feature/component requirements tool requirements are derived.
wf__req_tool		Workflow

Monitor/Verify Requirements		status: valid
tags: requirements_engineering version: 1 contains: gd_chklst__req_inspection needs input: wp__requirements_stkh, wp__requirements_feat, wp__requirements_comp, wp__requirements_feat_aou, wp__requirements_comp_aou, wp__platform_safety_manual, wp__module_safety_manual outputs: wp__issue_track_system, wp__requirements_inspect responsible: rl__committer approved by: rl__committer supported by: rl__safety_manager satisfied by: gd_req__configuration_uid, gd_req__config_pull_request_storage, gd_req__general_requirements_version, gd_req__general_checklist_templates, gd_req__general_status_set_check, gd_req__general_status_reset_check
The requirements are monitored and verified. The inspection shall be implemented as integral part of the review in version management tool.
wf__monitor_verify_requirements		Workflow

RAS(IC) for Requirements Engineering:

RASIC Overview for Requirements Engineering

Activity	Responsible	Approver	Supporter
wf__req_stkh_req	rl__contributor	rl__project_lead	rl__safety_manager
wf__req_feat_req	rl__contributor	rl__architecture_community	rl__safety_manager; rl__security_manager; rl__delivery_team
wf__req_feat_aou	rl__contributor	rl__committer	rl__safety_manager; rl__security_manager
wf__req_comp_req	rl__contributor	rl__committer	rl__safety_manager; rl__security_manager
wf__req_comp_aou	rl__contributor	rl__committer	rl__safety_manager; rl__security_manager
wf__req_tool	rl__contributor	rl__committer	rl__safety_manager; rl__security_manager
wf__monitor_verify_requirements	rl__committer	rl__committer	rl__safety_manager