Process Requirements

Please notice, that detail design description files (within MarkDown or RestructuredText) are optional. Also diagrams are optional, but if they are created, they shall have the following attributes to ensure consistency and traceability.

Static Diagram for Unit Interactions		status: valid
tags: manual_prio_1, mandatory, implementation, implementation version: 1 complies: std_req__iso26262__software_843, std_req__iso26262__software_844, std_req__iso26262__software_845, std_req__aspice_40__SWE-3-BP1 satisfies: wf__sw_detailed_design
The static diagram shall represent the units and their relationships using UML notations.
gd_req__impl_static_diagram		Process Requirements

Diagram Attributes

Diagram attribute: UID		status: valid
tags: manual_prio_1, attribute, mandatory, implementation, implementation version: 1 complies: std_req__iso26262__software_843, std_req__iso26262__software_844, std_req__iso26262__software_845, std_req__aspice_40__SWE-3-BP2 satisfies: wf__sw_detailed_design
Each diagram shall have a unique name. It shall consist of three parts: type of diagram structural element keyword describing the content of the diagram Consider the project’s naming convention.
gd_req__impl_diagram_uid		Process Requirements

Diagram attribute: title		status: valid
tags: manual_prio_1 attribute, mandatory, implementation, implementation version: 1 complies: std_req__iso26262__software_843, std_req__iso26262__software_844, std_req__iso26262__software_845, std_req__aspice_40__SWE-3-BP3, std_req__aspice_40__SWE-3-BP4 satisfies: wf__sw_detailed_design
The title of the diagram shall provide a short summary of the description, but is not an “additional” requirement. This means for example that the word “shall” is not allowed in the title for all diagram.
gd_req__impl_diagram_title		Process Requirements

Diagram attribute: description		status: valid
tags: manual_prio_1, attribute, mandatory, implementation, implementation version: 1 complies: std_req__iso26262__support_6421, std_req__iso26262__support_6425 satisfies: wf__sw_detailed_design
Each diagram shall have a description.
gd_req__impl_diagram_description		Process Requirements

Diagram Checks

Diagram mandatory consistency		status: valid
tags: prio_2_manual, attribute, check, implementation, implementation version: 1 complies: std_req__iso26262__support_6421, std_req__iso26262__support_6425 satisfies: wf__sw_detailed_design
It shall be checked if all diagrams are consistent with the source code and the design principles outlined in the development plan. This includes checking that the naming of the units, their interfaces and functions in any diagrams or descriptions matches the naming in the source code to ensure traceability. That means the diagrams and descriptions should not be outdated and be consistent with the source code and not introduce new terminology or concepts that are not present in the code.
gd_req__impl_diagram_consistency		Process Requirements

Unit Attributes

Unit naming		status: valid
tags: manual_prio_1, attribute, mandatory, implementation, implementation version: 1 complies: std_req__iso26262__software_843, std_req__aspice_40__SWE-3-BP1 satisfies: wf__sw_detailed_design
Each unit shall have a proper naming, which is unique within the component and follows a consistent naming convention. The name should be descriptive and reflect the functionality of the unit to ensure traceability and understandability. The naming convention should be defined in the project guidelines and consistently applied across all units.
gd_req__impl_unit_naming		Process Requirements

Unit description		status: valid
tags: manual_prio_1, mandatory, implementation, implementation version: 1 complies: std_req__iso26262__support_6421, std_req__iso26262__support_6425 satisfies: wf__sw_detailed_design
Each unit shall have a description in the source code.
gd_req__impl_unit_description		Process Requirements

Interface Attributes

Interface naming		status: valid
tags: manual_prio_1, mandatory, implementation, implementation version: 1 complies: std_req__iso26262__software_843, std_req__aspice_40__SWE-3-BP1 satisfies: wf__sw_detailed_design
Each interface shall have a proper naming, which is unique within the component and follows a consistent naming convention. The name should be descriptive and reflect the functionality of the interface to ensure traceability and understandability. Consider the project’s naming convention.
gd_req__impl_interface_naming		Process Requirements

Interface description		status: valid
tags: manual_prio_1, mandatory, implementation, implementation version: 1 complies: std_req__iso26262__support_6421, std_req__iso26262__support_6425 satisfies: wf__sw_detailed_design
Each interface shall have a description in the source code if the source code does not already provide sufficient information. It should provide a clear and comprehensive explanation of the interface’s purpose, its inputs and outputs, and how it interacts with other units or components. The description should be sufficient to allow users of the interface to understand how to interact with it without needing to read the implementation details. It should also include any relevant information about the expected behavior, constraints, and any assumptions made in the design of the interface. The documentation should be maintained and updated as the implementation evolves to ensure it remains accurate and useful.
gd_req__impl_interface_description		Process Requirements

Dependency Analysis

Dependency Analysis		status: valid
tags: prio_2_automation, implementation, implementation version: 1 complies: std_req__iso26262__software_942 satisfies: wf__sw_verify_implementation
For each component a dependency tree view shall be created to support design inspection and Safety Analysis. It shall show the libraries used by the component (i.e. which libraries are linked to the component, defined as CI build tool target) up to the leaves of the tree.
gd_req__impl_dependency_analysis		Process Requirements

Complexity Analyses

Design Complexity Analysis		status: valid
tags: prio_3_automation, model, check, implementation, implementation version: 1 complies: std_req__iso26262__software_743, std_req__aspice_40__SWE-3-BP3
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): Lines of Code per function: 100 / 200 Lines of Code per file : 2000 / 4000 Cyclomatic complexity per function: 10 / 20 Number of parameters per function: 5 / 7 Number of public interfaces per component: 3 / 10 The project may specify own limits for the complexity measures in the project guidelines, if there is a rationale for deviating from the default limits. Therefore the tooling shall support configuration of the limits globally for the project and per component, if the component wants to use own lower (more strict) limits.
gd_req__impl_complexity_analysis		Process Requirements