Process Requirements#

Problem Attributes#

Problem attribute: UID		status: valid
status: valid tags: problem_resolution, attribute, mandatory complies: std_req__aspice_40__SUP-9-BP1 satisfies: wf__problem__create_pr, wf__problem__analyse_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
status: valid tags: problem_resolution, attribute, mandatory complies: std_req__aspice_40__SUP-9-BP1 satisfies: wf__problem__create_pr, wf__problem__analyse_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
status: valid tags: problem_resolution, attribute, mandatory complies: std_req__aspice_40__SUP-9-BP1 satisfies: wf__problem__create_pr, wf__problem__analyse_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
status: valid tags: 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__analyse_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 requried to notify them about the potential problem.
gd_req__problem__attr_impact_description		Process Requirements

Problem attribute: analysis results		status: valid
status: valid tags: problem_resolution, attribute, mandatory complies: std_req__aspice_40__SUP-9-BP2 satisfies: wf__problem__create_pr, wf__problem__analyse_pr, wf__problem__initiate_monitor_pr, wf__problem__close_pr
Record analysis results (e.g. reason for rejection, safety, security, quality impact)
gd_req__problem__attr_anaylsis_results		Process Requirements

Problem attribute: stakeholder		status: valid
status: valid tags: 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__analyse_pr, wf__problem__initiate_monitor_pr, wf__problem__close_pr
Assign responsible stakeholder for analysing the problem Assign responsible stakeholder to resolve the problem
gd_req__problem__attr_stakeholder		Process Requirements

Problem attribute: classification		status: valid
status: valid tags: 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__analyse_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: category		status: valid
status: valid tags: problem_resolution, attribute, mandatory complies: std_req__aspice_40__SUP-9-BP1 satisfies: wf__problem__create_pr, wf__problem__analyse_pr, wf__problem__initiate_monitor_pr, wf__problem__close_pr
Each Problem shall have a category identifier: User Bug
gd_req__problem__attr_category		Process Requirements

Problem attribute:: safety affected		status: valid
status: valid tags: problem_resolution, attribute, mandatory complies: std_req__aspice_40__SUP-9-BP1 satisfies: wf__problem__create_pr, wf__problem__analyse_pr, wf__problem__initiate_monitor_pr, wf__problem__close_pr
Each Problem shall have a safety relevance identifier: Yes No
gd_req__problem__attr_safety_affected		Process Requirements

Problem attribute:: security affected		status: valid
status: valid tags: problem_resolution, attribute, mandatory complies: std_req__aspice_40__SUP-9-BP1 satisfies: wf__problem__create_pr, wf__problem__analyse_pr, wf__problem__initiate_monitor_pr, wf__problem__close_pr
Each Problem shall have a security relevance identifier: Yes No
gd_req__problem__attr_security_affected		Process Requirements

Problem attribute:: quality affected		status: valid
status: valid tags: problem_resolution, attribute, mandatory complies: std_req__aspice_40__SUP-9-BP1 satisfies: wf__problem__create_pr, wf__problem__analyse_pr, wf__problem__initiate_monitor_pr, wf__problem__close_pr
Each Problem shall have a quality relevance identifier: Yes No
gd_req__problem__attr_quality_affected		Process Requirements

Problem attribute: milestone		status: valid
status: valid tags: 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__analyse_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

status: valid

tags: problem_resolution, attribute, check

complies: std_req__aspice_40__SUP-9-BP1

satisfies: wf__problem__create_pr, wf__problem__analyse_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. For all requirements following attributes shall be mandatory:

Overview mandatory problem attributes#
Title
Problem attribute: analysis results
Problem attribute: category
Problem attribute: classification
Problem attribute: description
Problem attribute: milestone
Problem attribute:: quality affected
Problem attribute:: safety affected
Problem attribute:: security affected
Problem attribute: stakeholder
Problem attribute: status
Problem attribute: title
Problem attribute: UID

Problem Report issues closing constraints		status: valid
status: valid tags: problem_resolution, attribute, check complies: std_req__aspice_40__SUP-9-BP1 satisfies: wf__problem__create_pr, wf__problem__analyse_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

Process Requirements#

Problem Attributes#

Problem Resolution Checks#

This Page