Skip to content

Add process requirements for AoU linking #599

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
aschemmel-tech wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Add process requirements for AoU linking #599

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 20 additions & 2 deletions process/process_areas/architecture_design/guidance/architecture_process_reqs.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -158,8 +158,8 @@ Attributes of Architectural Elements
* valid
* invalid

Traceability to Requirements
----------------------------
Traceability to Requirements and AoU
------------------------------------

.. gd_req:: Architecture attribute: fulfils
:id: gd_req__arch_attr_fulfils
Expand All @@ -170,6 +170,15 @@ Traceability to Requirements

Each architectural element shall be linked to a requirement.

.. gd_req:: Architecture attribute: fulfils (AoU)
:id: gd_req__arch_attr_fulfils_aou
:status: valid
:tags: manual_prio_1, attribute, mandatory
:complies: std_req__iso26262__support_6425, std_req__aspice_40__SWE-2-BP4
:satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch

Each architectural element shall be linked to AoUs if it fulfills these.

.. gd_req:: Architecture traceability
:id: gd_req__arch_traceability
:status: valid
Expand Down Expand Up @@ -250,6 +259,15 @@ Checks for Architectural Design
* Functional requirements <-> static / dynamic architectural elements (feat_arc_sta, feat_arc_dyn)
* Interface requirements <-> interface architectural elements (logic_arc_int, logic_arc_int_op)

.. gd_req:: Check of Architecture linkage to AoU
:id: gd_req__arch_linkage_aou
:status: valid
:tags: prio_2_automation, attribute, check
:satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch

It shall be checked that architecture elements are not linked to its own AoU
("own" means the AoU linked as "mitigated_by" to the Safety/Security Analysis linked via "violates" to the element)

.. gd_req:: Check of Architecture consistency Components in modules
:id: gd_req__arch_consistency_model
:status: valid
Expand Down
15 changes: 15 additions & 0 deletions ...s/process_areas/requirements_engineering/guidance/requirements_process_reqs.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -192,6 +192,21 @@ Process Requirement Linkage
* workflow or stakeholder requirements <- process requirements
* process requirements or stakeholder requirements <- tool requirements

.. gd_req:: Requirement Linkage to AoU
:id: gd_req__req_linkage_aou
:status: valid
:tags: manual_prio_1, attribute
:complies: std_req__iso26262__support_6432, std_req__aspice_40__SWE-1-BP5
:satisfies: wf__req_feat_req, wf__req_comp_req

Requirements shall be linked to AoU via the attribute satisfies, if they already satisfy these.

* AoU <- feature requirements
* AoU <- component requirements

Note: "Already" illustrates the understanding that AoU come from used (external) components
which appear later in the development (after deciding an architecture).

.. gd_req:: Requirement Traceability
:id: gd_req__req_traceability
:status: valid
Expand Down
Loading