Process Requirements

Problem Attributes

Problem attribute: UID		status: valid
tags: done_automation, problem_resolution, attribute, mandatory complies: std_req__aspice_40__SUP-9-BP1 satisfies: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr
Each Problem shall have a unique ID. It shall be in an integer number.
gd_req__problem_attr_uid		Process Requirements

Problem attribute: status		status: valid
tags: manual_prio_1, problem_resolution, attribute, mandatory complies: std_req__aspice_40__SUP-9-BP1 satisfies: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr
Each Problem shall have a status: open in review in implementation closed rejected
gd_req__problem_attr_status		Process Requirements

Problem attribute: title		status: valid
tags: manual_prio_1, problem_resolution, attribute, mandatory complies: std_req__aspice_40__SUP-9-BP1 satisfies: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr
Reason for Problem Report
gd_req__problem_attr_title		Process Requirements

Problem attribute: description		status: valid
tags: manual_prio_1, problem_resolution, attribute, mandatory complies: std_req__aspice_40__SUP-9-BP1, std_req__aspice_40__SUP-9-BP2 satisfies: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr
Exact description of the Problem, including potential cause and impact of the problem. Record especially, if functional safety or cybersecurity may affected here. Record potential affected parties, and if it may required to notify them about the potential problem.
gd_req__problem_attr_impact_description		Process Requirements

Problem attribute: analysis results		status: valid
tags: manual_prio_1, problem_resolution, attribute, mandatory complies: std_req__aspice_40__SUP-9-BP2 satisfies: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr
Record analysis results (e.g. reason for rejection, safety, security, quality impact) as comments.
gd_req__problem_attr_anaylsis_results		Process Requirements

Problem attribute: stakeholder		status: valid
tags: prio_1_automation, problem_resolution, attribute, mandatory complies: std_req__aspice_40__SUP-9-BP2, std_req__aspice_40__SUP-9-BP5 satisfies: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr
Assign responsible stakeholder for analyzing the problem Assign responsible stakeholder to resolve the problem
gd_req__problem_attr_stakeholder		Process Requirements

Problem attribute: classification		status: valid
tags: prio_1_automation, problem_resolution, attribute, mandatory complies: std_req__aspice_40__SUP-9-BP1, std_req__aspice_40__SUP-9-BP2 satisfies: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr
Each Problem shall have a classification identifier: minor major critical blocker
gd_req__problem_attr_classification		Process Requirements

Problem attribute:: safety affected		status: valid
tags: prio_1_automation, problem_resolution, attribute, mandatory complies: std_req__aspice_40__SUP-9-BP1 satisfies: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr
Each Problem shall have a safety relevance identifier: Yes No Note: If neither security or safety relevance is set the bug is always quality relevant.
gd_req__problem_attr_safety_affected		Process Requirements

Problem attribute:: security affected		status: valid
tags: prio_1_automation, problem_resolution, attribute, mandatory complies: std_req__aspice_40__SUP-9-BP1 satisfies: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr
Each Problem shall have a security relevance identifier: Yes No Note: If neither security or safety relevance is set the bug is always quality relevant.
gd_req__problem_attr_security_affected		Process Requirements

Problem attribute: milestone		status: valid
tags: manual_prio_1, problem_resolution, attribute, mandatory complies: std_req__aspice_40__SUP-9-BP1, std_req__aspice_40__SUP-9-BP6 satisfies: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr
Milestone until the Problem must be implemented (used for prioritization)
gd_req__problem_attr_milestone		Process Requirements

Problem Resolution Checks

Problem Resolution mandatory attributes provided		status: valid
tags: prio_2_automation, problem_resolution, attribute, check complies: std_req__aspice_40__SUP-9-BP1 satisfies: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr
It shall be checked if all mandatory attributes for each Problem is provided by the user. Following attributes shall be mandatory: Overview mandatory problem attributes Title Problem attribute: analysis results Problem attribute: classification Problem attribute: description Problem attribute: milestone Problem attribute:: safety affected Problem attribute:: security affected Problem attribute: stakeholder Problem attribute: status Problem attribute: title Problem attribute: UID Note: See also template for problem report: Problem Template (gd_temp__problem_template)
gd_req__problem_check_mandatory		Process Requirements

Problem Report issues closing constraints		status: valid
tags: prio_1_automation, problem_resolution, attribute, check complies: std_req__aspice_40__SUP-9-BP1 satisfies: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr
ISSUEs related to Problem Reports shall not automatically closed, if linked ISSUEs or PRs are closed or merged and these ISSUEs shall be closed only manually from the Committer (rl__committer).
gd_req__problem_check_closing		Process Requirements