Skip to content

Commit 06693b9

Browse files
add linking to iso26262 and add requirements according to ISO
1 parent cef1744 commit 06693b9

File tree

3 files changed

+22
-6
lines changed

3 files changed

+22
-6
lines changed

process/process_areas/architecture_design/guidance/architecture_guideline.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ Architecture Guideline
2020
.. gd_guidl:: Architectural Design
2121
:id: gd_guidl__arch_design
2222
:status: valid
23-
:complies: std_req__isopas8926__44411, std_req__isopas8926__44412, std_req__iso26262__software_744, std_req__iso26262__software_745
23+
:complies: std_req__isopas8926__44411, std_req__isopas8926__44412, std_req__iso26262__software_743, std_req__iso26262__software_744, std_req__iso26262__software_745
2424

2525
The guideline focuses on the steps which need to be performed in order to create the architectural design. The concept behind those steps is described in the :need:`[[title]] <doc_concept__arch_process>`.
2626

process/process_areas/architecture_design/guidance/architecture_inspection_checklist.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ Inspection Checklist Template
2121
:id: gd_chklst__arch_inspection_checklist
2222
:status: valid
2323
:tags: architecture_design
24-
:complies: std_req__iso26262__software_647, std_req__iso26262__software_749, std_req__iso26262__software_7413
24+
:complies: std_req__iso26262__software_647, std_req__iso26262__software_743, std_req__iso26262__software_749, std_req__iso26262__software_7413
2525

2626
For the content see here:
2727

process/process_areas/architecture_design/guidance/architecture_process_reqs.rst

Lines changed: 20 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -33,13 +33,13 @@ Architectural Model
3333
:id: gd_req__arch_hierarchical_structure
3434
:status: valid
3535
:tags: done_automation
36-
:complies: std_req__iso26262__support_6431, std_req__iso26262__support_6432
36+
:complies: std_req__iso26262__support_6431, std_req__iso26262__support_6432, std_req__iso26262__software_743
3737
:satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch
3838

3939
The architectural elements shall be hierarchically structured on two levels:
4040

4141
* Feature Level (=Logical Level)
42-
* Component Level
42+
* Component Level (allows also recusrsive decomposition on lower levels)
4343

4444
.. gd_req:: Structuring of the architectural elements
4545
:id: gd_req__arch_build_blocks
@@ -218,15 +218,15 @@ Checks for Architectural Design
218218
:satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch
219219
:complies: std_req__iso26262__software_746, std_req__iso26262__software_748
220220

221-
It shall be checked that valid safety architectural elements (Safety != QM) can only be linked against valid safety architectural elements.
221+
It shall be checked that valid safety architectural elements (Safety!=QM) can only be linked against valid safety architectural elements.
222222

223223
.. gd_req:: Architecture linkage security
224224
:id: gd_req__arch_linkage_security_trace
225225
:status: valid
226226
:tags: prio_2_automation, attribute, check
227227
:satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch
228228

229-
It shall be checked that security relevant architectural elements (Security == YES) can only be linked against security relevant architectural elements.
229+
It shall be checked that security relevant architectural elements (Security==YES) can only be linked against security relevant architectural elements.
230230

231231
.. gd_req:: Architecture linkage requirement
232232
:id: gd_req__arch_linkage_requirement
@@ -271,3 +271,19 @@ Checks for Architectural Design
271271
:satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch
272272

273273
It shall be checked if all SW components which are mentioned in the dynamic architecture are defined in the static architecture.
274+
275+
.. gd_req:: Architecture complexity analysis
276+
:id: gd_req__arch_complexity_analysis
277+
:status: valid
278+
:tags: prio_3_automation, model, check
279+
:complies: std_req__iso26262__software_743
280+
281+
If a component is assigned to (safety!=QM) a complexity analysis for the components shall be performed. It shall consider appropriate code metrics like lines of code, cyclomatic complexity, number of public interfaces, number of parameters and so on. The results of the analysis shall be documented in the component classification document. The project specific limits for the complexity measures shall be defined in the project guidelines.
282+
283+
.. gd_req:: Architecture scheduling properties
284+
:id: gd_req__arch_scheduling_properties
285+
:status: valid
286+
:tags: manual
287+
:complies: std_req__iso26262__software_743
288+
289+
For each component the scheduling properties shall be defined.

0 commit comments

Comments
 (0)