Linux Safety Architecture methodology #9
Conversation
This file contains 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
Collaborator
reiterative
commented
May 25, 2022
reiterative
commented
- Based on methodology proposed in Safety Architecture WG minutes WW21
* From Safety Architecture WG minutes WW21 Signed-off-by: Paul Albertella <[email protected]>
reiterative
force-pushed
the
pa-architetcure-methodology
branch
from
dd6ab94 to
28d76d8
Compare
paolonig
reviewed
Jun 21, 2022
| @@ -0,0 +1,17 @@ | |||
| # Kernel Safety Architecture Methodology | |||
There was a problem hiding this comment.
from Gab: I think we need to align this methodology with the pull request: #3
| * Functionalities allocated to each functional block (NOTE: only functionalities that are meaningful for fulfilling the allocated requirement) | ||
| * For each of the identified functionalities the role of the interfaces shall be described (under which conditions they are invoked) | ||
| * Safety Analysis: Do an STPA analysis and define derived safety requirements for each of the functional blocks as in 3) | ||
| * Iterate: Evaluate functional blocks complexity vs allocated safety requirements and eventually iterate back in 1) or stop here if not needed (complexity is acceptable) |
There was a problem hiding this comment.
From Gab: the stop criteria should be rephrased as "the are comprehensive and complete architectural mitigation measure to satisfy the allocated safety requirement or the complexity is acceptable"
|
|
||
| * Safety Requirement Definition: an initial safety requirement must be allocated to the Kernel as a whole from the safety concept of domain specific WGs. | ||
| * Scope Identification: given a safety requirement, the code functionally supporting such requirement must be comprehensively identified | ||
| * Initial partitioning into functional blocks: one or more functional blocks in the scope of the code above must be identified and for each of these blocks we should describe: |
There was a problem hiding this comment.
from Gab: is the name "functional block" correct or it should be replaced by "controllers" (to meet the STPA terminology)?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.