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 :need:`std_req__iso26262__software_7413`
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
The config allows the user to configure some resources such as the ring buffer size or the slot size, this should be documented with some element like an assumption of use.
What
The architecture checklist has the following point:
The config allows the user to configure some resources such as the ring buffer size or the slot size, this should be documented with some element like an assumption of use.
Acceptance Criteria (DoD)
How
No response