Process Requirements

Change Request Attributes

Change Request attribute: UID		status: valid
tags: done_automation, attribute, mandatory, change_management complies: std_req__aspice_40__SUP-10-BP1, std_req__iso26262__support_8411, std_req__iso26262__support_8421, std_req__iso26262__support_8432, std_req__iso26262__support_8453 satisfies: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr
Each Change Request shall have a unique ID. It shall be in an integer number.
gd_req__change_attr_uid		Process Requirements

Change Request attribute: status		status: valid
tags: done_automation, attribute, mandatory, change_management complies: std_req__aspice_40__SUP-10-BP3, std_req__aspice_40__SUP-10-BP5, std_req__aspice_40__SUP-10-BP6, std_req__iso26262__support_8411, std_req__iso26262__support_8422, std_req__iso26262__support_8432, std_req__iso26262__support_8442 satisfies: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr
Each Change Request shall have a status: open in review in implementation closed rejected
gd_req__change_attr_status		Process Requirements

Change Request attribute: title		status: valid
tags: manual_prio_1, attribute, mandatory, change_management complies: std_req__aspice_40__SUP-10-BP1, std_req__iso26262__support_8411, std_req__iso26262__support_8422 satisfies: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr
Reason for the Change Request
gd_req__change_attr_title		Process Requirements

Change Request attribute: description		status: valid
tags: manual_prio_1, attribute, mandatory, change_management complies: std_req__aspice_40__SUP-10-BP2, std_req__iso26262__support_8411, std_req__iso26262__support_8422, std_req__iso26262__support_8431, std_req__iso26262__support_8432, std_req__iso26262__support_8452, std_req__iso26262__support_8453 satisfies: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr
Exact description of the Change Request, including impact analysis on functional safety, security, implementation (schedule, risks, resources) verification (measures defined).
gd_req__change_attr_impact_description		Process Requirements

Change Request attribute: safety		status: valid
tags: prio_1_automation, attribute, mandatory, change_management complies: std_req__aspice_40__SUP-10-BP2, std_req__iso26262__support_8422 satisfies: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr
Each Change Request shall have a automotive safety integrity level (ASIL) identifier: QM ASIL_B
gd_req__change_attr_impact_safety		Process Requirements

Change Request attribute: security		status: valid
tags: prio_2_automation, attribute, mandatory, change_management complies: std_req__aspice_40__SUP-10-BP2, std_req__iso26262__support_8422 satisfies: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr
Each Change Request shall have a security relevance identifier: Yes No
gd_req__change_attr_impact_security		Process Requirements

Change Request attribute: Types		status: valid
tags: prio_1_automation, attribute, mandatory, change_management complies: std_req__aspice_40__SUP-10-BP1 satisfies: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr
Feature Feature Modification Component Component Modification Feature This Change Request describes a potential new feature for the platform. The Change Request uses the Feature request template: Feature Template. Feature Modification This Change Request describes a scope modification of an existing feature (requirement or work product). The Change Request modifies the already existing Feature Request template: Feature Template. Component This Change Request describes a potential new component for the platform. The Change Request uses the Component request template: Component Template. Component Modification This Change Request describes a scope modification of an existing component (requirement or work product). The Change Request modifies the already existing Component Request template: Component Template.
gd_req__change_attr_types		Process Requirements

Change Request attribute: Affected Work Products		status: draft
tags: attribute, mandatory, change_management complies: std_req__aspice_40__SUP-10-BP4, std_req__iso26262__support_8412, std_req__iso26262__support_8422, std_req__iso26262__support_8452, std_req__iso26262__support_8453 satisfies: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr
Links to the work products affected by the Change Request
gd_req__change_attr_affected_wp		Process Requirements

Change Request attribute: Milestone		status: valid
tags: done_automation, attribute, mandatory, change_management complies: std_req__aspice_40__SUP-10-BP6, std_req__iso26262__support_8413 satisfies: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr
Milestone until the Change Request must be implemented (used for prioritization)
gd_req__change_attr_milestone		Process Requirements

Change Request Checks

Change Requests mandatory attributes provided		status: valid
tags: prio_2_automation, attribute, check, change_management complies: std_req__aspice_40__iic-13-51 satisfies: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr
It shall be checked if all mandatory attributes for each Change Request is provided by the user. For all requirements following attributes shall be mandatory: Overview mandatory change request attributes Title Change Request attribute: Affected Work Products Change Request attribute: description Change Request attribute: safety Change Request attribute: security Change Request attribute: Milestone Change Request attribute: status Change Request attribute: title Change Request attribute: Types Change Request attribute: UID
gd_req__change_attr_mandatory		Process Requirements

Change Request Traceability Impact Analysis Tool

Change Requests Impact Analysis Tool		status: valid
tags: prio_3_automation, check, tool, change_management complies: std_req__aspice_40__iic-13-51 satisfies: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr
It shall be reported, which work products and elements are affected by adding a new feature or component or by a modification of an existing feature or component. Below picture illustrates the relations: The picture is derived from the building blocks metamodel containing all the work products (Building blocks concept). Its arrows show how every work product is linked (manually) to other work products (e.g. feature requirements are linked to stakeholder requirements via “satisfies”). The color code describes which of these Links need to be followed for the impact analysis (so for the example this means: if a stakeholder requirement is changed, the feature requirements linked are affected, but not the other way round). “Black” links do not need to be followed, these are the “verifies” links. And these are expected to fail after implementation change, so the impact on testing will be detected by the test automation without the need for an additional tooling. Note that for some links it is expected to have both directions followed (red arrows) - these are the artefacts which reside in different repositories. Note also: The impact analysis needs to follow the links iteratively, so first to the directly connected work products, then to the next, … (see the next illustration):
gd_req__change_tool_impact_analysis		Process Requirements