Improvement: rework ffi requirements checklist #539
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
RolandJentschETAS
requested review from
PandaeDo,
aschemmel-tech,
masc2023 and
pahmann
as code owners
|
The created documentation from the pull request is available at: docu-html |
aschemmel-tech
requested changes
Jan 27, 2026
Contributor
aschemmel-tech
left a comment
aschemmel-tech
left a comment
There was a problem hiding this comment.
see inline comments
| - | ||
| * - ARC_04_01 | ||
| - If software partitioning (different operating system processes) is used to implement freedom from interference between the processes with different rating (QM/ASIL), is effectiveness evidence generated during integration and verification tests? | ||
| - If your software architectural design includes processes with different safety rating (QM/ASIL) are freedom from interference for shared resources (cpu time, shared memory, ...) are ensured? See also ARC_04_03. |
Contributor
There was a problem hiding this comment.
duplicate "are" - remove one
| - | ||
| a) the usage of shared resources (cpu time, shared memory, ...) are checked in a way that freedom from interference between the processes is ensured, | ||
| b) check if the operating system supports freedom from interference between the processes | ||
| Check lso if the operating system supports freedom from interference between the processes. |
| - Is an upper estimation of the required resources (RAM, ROM, non volatile memory, communication) available and documented? | ||
| - 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 forseeable customer needs? See also ARC_02_05. | ||
|
|
||
| Note: see :need:`std_req__iso26262__software_7411` |
Contributor
There was a problem hiding this comment.
I think you wanted to link to 7413 ?
| - manual | ||
| - | ||
| - | ||
| - |
Contributor
There was a problem hiding this comment.
missing entry here for "Guidance" - how to do this? Maybe also explaining why we do only on Feature architecture?
| - | ||
| a) the usage of shared resources (cpu time, shared memory, ...) are checked in a way that freedom from interference between the processes is ensured, | ||
| b) check if the operating system supports freedom from interference between the processes | ||
| Check lso if the operating system supports freedom from interference between the processes. |
Contributor
There was a problem hiding this comment.
Add someting like "This should also be required already by an AoU in you project's platform assumptions and checked there."
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The software architecture checklists in the freedom from interference area of the ISO26262 is reworked for clearer understanding of the checkpoints.