[Your Feature Name] Architecture Inspection Checklist		status: draft security: YES safety: ASIL_B
tags: template, feature_name realizes: wp__sw_arch_verification
doc__feature_name_arc_inspection		Generic Document

Attention

The above directive must be updated according to your Feature.

• Modify Your Feature Name to be your Feature Name

• Modify id to be your Feature Name in lower snake case preceded by doc__ and followed by _arc_inspection

• Adjust status to be valid

• Adjust safety, security and tags according to your needs

Architecture Inspection Checklist

Purpose

The purpose of the software architecture checklist is to ensure that the design meets the criteria and quality as defined per project processes and guidelines for feature and component architectural design elements. It helps to check the compliance with requirements, identify errors or inconsistencies, and ensure adherence to best practices. The checklist guides evaluation of the architecture design, identifies potential problems, and aids in communication and documentation of architectural decisions to stakeholders.

Checklist

Please note that it is mandatory to fill in the “passed” column with “yes” or “no” for each checklist item. Additionally, provide remarks explaining why it is passed or not passed. In case of “no”, a link to the issue tracking system must be added in the last column. See also Review and Inspection Concept for further information about reviews in general and inspection in particular.

Table 59 Architecture Design Review Checklist

Review Id	Acceptance criteria	Type	Guidance	passed	Remarks	Issue link
ARC_01_01	Is the traceability from software architectural elements to requirements, and other level architectural elements (e.g. component to interface) established according to the “Relations between the architectural elements” as described in Architecture Process (doc_concept__arch_process)?	automated	Trace should be checked automatically by tool support in the future. It will be removed from the checklist once the requirement (Correlations of the architectural building blocks (gd_req__arch_build_blocks_corr)) is implemented. Refer to Tool Requirements for the current status.
ARC_01_02	If the architectural element is related to any supplier manuals (including safety and security), are the relevant parts covered?	manual	If the architecture makes use of supplied elements, their manuals (like safety) have to be considered (i.e. its provided functionality matches the expectation and assumptions are fulfilled). Note that in case of safety component this means that assumed Technical Safety Requirements and AoUs of the safety manual are covered.
ARC_01_03	Is the architectural element traceable to the lower-level artifacts as defined by the work product traceability?	automated	Will be removed from checklist once the requirement (Correlations of the architectural building blocks (gd_req__arch_build_blocks_corr)) is implemented by automated tool check. See Tool Requirements. Details of possible linking can be depicted from traceability concept.
ARC_02_01	Is the software architecture design compliant with the overall feature architecture?	manual	On component level check against the feature architecture, on feature level check other features with common components used.
ARC_02_02	Is appropriate and comprehensible operation and interface naming present in the architectural design?	manual	Check Architectural Design Guideline (gd_guidl__arch_design)
ARC_02_03	Are the correctness of data flow and control flow within the architectural elements considered?	manual	For example, examine definitions, transformations, integrity, and interaction of data; check error handling, data exchange between elements, correct response to inputs, and documented decision making. Note: Consistency is ensured by the process/tooling, by defining each interface only once.
ARC_02_04	Are the interfaces between the software architectural element and other architectural elements well defined?	manual	Check if the interface handles undefined behavior or errors; can established protocols be used; are the interfaces for inputs, outputs, and error codes documented; is loose coupling considered and only limited exposure; can unit or integration tests be written against the interface; data amount transferred; ensure no sensitive data is exposed;
ARC_02_05	Does the software architectural element consider the timing constraints (from the parent requirement)?	manual	If there are strict timing requirements, a programming time estimation should be performed and deadline supervision should be considered.
ARC_02_06	Is the documentation of the software architectural element, including textual and graphical descriptions (e.g., UML diagrams), clear and complete?	manual	Use of semi-formal notation is expected for architectural elements with an allocated ASIL level. Is the architecture template correctly filled?
ARC_03_01	Is the architectural element modular and encapsulated?	manual	Check, for example, that only minimal interfaces are used. The design should be object oriented. Interfaces and interactions are clearly defined. Usage of access types (private, protected) is properly set. Limited global variables.
ARC_03_02	Is the suitability of the software architecture for future modifications and maintainability considered?	manual	Check for, for example, loose coupling, separation of concerns, high cohesion, versioning strategy for interfaces, decision records, and use of established design patterns.
ARC_03_03	Are simplicity and avoidance of unnecessary complexity present in the software architecture?	manual	Indicators of complexity include: the number of use cases (corresponding to dynamic diagrams) allocated to a single design element, the number of interfaces and operations in an interface, function parameters, global variables, complex types, and limited comprehensibility. Note: If any of the numbers above exceed 3, a design rationale is mandatory (for all types).
ARC_03_04	Is the software architecture design following best practices and design principles?	manual	Refer to architectural guidelines and recommendations within the project documentation.
ARC_04_01	If your software architectural design includes processes with different safety ratings (QM/ASIL), is freedom from interference for shared resources (CPU time, shared memory, etc.) ensured? See also ARC_04_03. Note: see software_7411 (std_req__iso26262__software_7411) and software_749 (std_req__iso26262__software_749) with Annex D for partitioning to ensure freedom from interference. Note: Modules should not mix ASIL and QM processes unless justified otherwise; therefore, this question is only relevant on the feature level.	manual	Check whether your architecture design complies with project guidelines to establish freedom from interference between components. This can be achieved, for example, by using a hypervisor or an OS that supports partitioning with an MMU or specific scheduling mechanisms, as well as safety mechanisms like watchdogs or program flow monitoring. Also check if the operating system supports freedom from interference between the processes and make sure an “Assumption of Use requirement” for this exists in your project. For example, see score aou_req__platform__process_isolation.
ARC_04_02	Does the software architectural design consider its feasibility with respect to the required resources for the embedded software, especially for time-critical aspects like startup time, but also including RAM, ROM, non-volatile memory, communication bandwidth, and processing time limits according to the requirements or foreseeable customer needs? See also ARC_02_05. Note: see software_7413 (std_req__iso26262__software_7413)	manual	Check if there are any limits for resource consumption or timing aspects in your project, such as startup time, communication bandwidth, or memory usage. If such limits exist, ensure that your architecture takes these limits into account, especially with respect to scalability. For this, make an estimation of the required resources based on the architectural design and a prototypical implementation or a measurement of an existing implementation, and compare it to the defined limits or planned scalability. Check if any bottlenecks are present in the architecture that could lead to resource overuse or timing violations.
ARC_04_03	If your software architectural design includes processes and tasks, are their scheduling policies and priorities (at least the necessary relationships between them) defined to ensure that timing requirements are met? Please note that the particular priorities or priority ranges will probably be defined by the project handbook or the software development plan. Note: see software_743 (std_req__iso26262__software_743)	manual	Provide a rationale for these scheduling policies and priorities, or explain why they are not needed.