Process Requirements

Problem Attributes

Problem attribute: UID		status: valid
tags: done_automation, problem_resolution, attribute, mandatory, problem_resolution version: 1 complies: std_req__aspice_40__SUP-9-BP1 satisfies: wf__problem_analyze_pr, wf__problem_close_pr, wf__problem_create_pr, wf__problem_initiate_monitor_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, problem_resolution version: 1 complies: std_req__aspice_40__SUP-9-BP1 satisfies: wf__problem_analyze_pr, wf__problem_close_pr, wf__problem_create_pr, wf__problem_initiate_monitor_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, problem_resolution version: 1 complies: std_req__aspice_40__SUP-9-BP1 satisfies: wf__problem_analyze_pr, wf__problem_close_pr, wf__problem_create_pr, wf__problem_initiate_monitor_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, problem_resolution version: 2 complies: std_req__aspice_40__SUP-9-BP1, std_req__aspice_40__SUP-9-BP2 satisfies: wf__problem_analyze_pr, wf__problem_close_pr, wf__problem_create_pr, wf__problem_initiate_monitor_pr
Exact description of the Problem, including potential cause and impact of the problem. Record especially whether functional safety or cybersecurity may be affected. Record affected parties, whether notification is needed and why, and who was notified and when. See Notification of Affected Parties.
gd_req__problem_attr_impact_description		Process Requirements

Problem attribute: affected versions		status: valid
tags: manual_prio_1, problem_resolution, attribute, mandatory, problem_resolution version: 1 complies: std_req__aspice_40__SUP-9-BP2 satisfies: wf__problem_analyze_pr, wf__problem_close_pr, wf__problem_create_pr, wf__problem_initiate_monitor_pr
Each Problem shall record the detection version and the first and last affected versions, including versions derived from the faulty version. Identify affected branches and dependent integrations where applicable. Record unknowns as under investigation and update them during analysis.
gd_req__problem_attr_affected_versions		Process Requirements

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

Problem attribute: stakeholder		status: valid
tags: prio_1_automation, problem_resolution, attribute, mandatory, problem_resolution version: 1 complies: std_req__aspice_40__SUP-9-BP2, std_req__aspice_40__SUP-9-BP5 satisfies: wf__problem_analyze_pr, wf__problem_close_pr, wf__problem_create_pr, wf__problem_initiate_monitor_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, problem_resolution version: 1 complies: std_req__aspice_40__SUP-9-BP1, std_req__aspice_40__SUP-9-BP2 satisfies: wf__problem_analyze_pr, wf__problem_close_pr, wf__problem_create_pr, wf__problem_initiate_monitor_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, problem_resolution version: 2 complies: std_req__aspice_40__SUP-9-BP1 satisfies: wf__problem_analyze_pr, wf__problem_close_pr, wf__problem_create_pr, wf__problem_initiate_monitor_pr
Each Problem shall have a safety relevance identifier: Yes No Where safety may be affected, the responsible Safety Manager shall confirm or disconfirm safety relevance and record the reason. Note: If neither safety nor security is affected, the problem is quality relevant.
gd_req__problem_attr_safety_affected		Process Requirements

Problem attribute:: security affected		status: valid
tags: prio_1_automation, problem_resolution, attribute, mandatory, problem_resolution version: 2 complies: std_req__aspice_40__SUP-9-BP1 satisfies: wf__problem_analyze_pr, wf__problem_close_pr, wf__problem_create_pr, wf__problem_initiate_monitor_pr
Each Problem shall have a security relevance identifier: Yes No Where security may be affected, the responsible Security Manager shall confirm or disconfirm security relevance and record the reason. Note: If neither safety nor security is affected, the problem is quality relevant.
gd_req__problem_attr_security_affected		Process Requirements

Problem attribute: milestone		status: valid
tags: manual_prio_1, problem_resolution, attribute, mandatory, problem_resolution version: 1 complies: std_req__aspice_40__SUP-9-BP1, std_req__aspice_40__SUP-9-BP6 satisfies: wf__problem_analyze_pr, wf__problem_close_pr, wf__problem_create_pr, wf__problem_initiate_monitor_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, problem_resolution version: 1 complies: std_req__aspice_40__SUP-9-BP1 satisfies: wf__problem_analyze_pr, wf__problem_close_pr, wf__problem_create_pr, wf__problem_initiate_monitor_pr
It shall be checked if all mandatory attributes for each Problem is provided by the user. Following attributes shall be mandatory: Overview of mandatory problem attributes Title Problem attribute: affected versions 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_req__problem_check_mandatory		Process Requirements

Problem Report issues closing constraints		status: valid
tags: prio_1_automation, problem_resolution, attribute, check, problem_resolution version: 1 complies: std_req__aspice_40__SUP-9-BP1 satisfies: wf__problem_analyze_pr, wf__problem_close_pr, wf__problem_create_pr, wf__problem_initiate_monitor_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.
gd_req__problem_check_closing		Process Requirements

Closure conditions for problems where safety is affected		status: valid
tags: manual_prio_1, problem_resolution, check, problem_resolution version: 1 complies: std_req__iso26262__management_5433 satisfies: wf__problem_close_pr
A problem classified as Safety affected shall be considered managed to closure only when a rationale supports either an implemented adequate safety measure whose effectiveness has been verified, or an evaluation that the problem does not constitute an unreasonable risk.
gd_req__problem_check_safety_closure		Process Requirements

Documentation and review of closure rationale where safety is affected		status: valid
tags: manual_prio_1, problem_resolution, check, problem_resolution version: 1 complies: std_req__iso26262__management_5434 satisfies: wf__problem_close_pr
For either safety-specific closure condition, the rationale shall be documented and reviewed. Record the review result. See Closure of Problems Where Safety Is Affected.
gd_req__problem_check_safety_rationale		Process Requirements