You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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>`.
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.
230
230
231
231
.. gd_req:: Architecture linkage requirement
232
232
:id: gd_req__arch_linkage_requirement
@@ -271,3 +271,19 @@ Checks for Architectural Design
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