From eda837a19c4556023b5d04801b29fae745d69591 Mon Sep 17 00:00:00 2001 From: Andreas Zwinkau Date: Wed, 23 Sep 2026 15:42:04 +0200 Subject: [PATCH] fix: missing 'satisfies' link --- .../implementation/guidance/implementation_process_reqs.rst | 1 + 1 file changed, 1 insertion(+) diff --git a/process/process_areas/implementation/guidance/implementation_process_reqs.rst b/process/process_areas/implementation/guidance/implementation_process_reqs.rst index 4b7f92847e..b5566cb937 100644 --- a/process/process_areas/implementation/guidance/implementation_process_reqs.rst +++ b/process/process_areas/implementation/guidance/implementation_process_reqs.rst @@ -190,6 +190,7 @@ Complexity Analyses :status: valid :version: 1 :tags: implementation, prio_3_automation, model, check + :satisfies: wf__sw_detailed_design[version==1] :complies: std_req__iso26262__software_743[version==1], std_req__aspice_40__SWE-3-BP3[version==1] A complexity analysis for the components shall be performed by automated tool support. 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 SW Verification Report. As default an exceeds of the following limits shall be reported for the complexity measures (ASIL B / QM):