update tailoring of iso26262 #464
Conversation
masc2023
requested review from
PandaeDo,
PhilipPartsch,
aschemmel-tech and
pahmann
as code owners
|
The created documentation from the pull request is available at: docu-html |
masc2023
force-pushed
the
tailor_iso26262
branch
5 times, most recently
from
4df8ecf to
5cc820b
Compare
tailoring of std_wp__iso26262__software_1052, and std_req__iso26262__software_1041 tailoring of std_req__iso26262__software_11147*, std_req__iso26262__software_11148*, std_req__iso26262__software_11149* tailoring of std_req__iso26262__analysis_641 to std_req__iso26262__analysis_644 tailoring of std_req__iso26262__analysis_744 tailoring of std_req__iso26262__management_5431, std_req__iso26262__management_5433, std_req__iso26262__management_5434, std_req__iso26262__management_5435 tailoring of std_req__iso26262__management_6464 tailoring of std_req__iso26262__software_543 tailoring of tailoring of std_req__iso26262__software_841, std_req__iso26262__software_842, std_req__iso26262__software_844, std_req__iso26262__software_845 tailoring of std_req__iso26262__software_app_c_41, std_req__iso26262__software_app_c_42, std_req__iso26262__software_app_c_43, std_req__iso26262__software_app_c_44, std_req__iso26262__software_app_c_45
masc2023
force-pushed
the
tailor_iso26262
branch
from
5cc820b to
53fcb1b
Compare
| :status: valid | ||
| :complies: std_req__iso26262__software_945, | ||
| std_req__iso26262__software_1045, std_req__iso26262__software_1046, std_req__iso26262__software_1047, | ||
| std_req__iso26262__software_1041, std_req__iso26262__software_1045, std_req__iso26262__software_1046, std_req__iso26262__software_1047, |
There was a problem hiding this comment.
need also to include reasoning below
There was a problem hiding this comment.
@pahmann , see above, this requirements are not covered yet by verification, either you take them in your process area or you agree to tailor them out
|
|
||
| - for "system" standard requirements: see platform safety plan in PMP | ||
| - for "software" standard requirements: 644, 646: because they refer to (PMP) tailored work product, 643: because this refers to (PMP) tailored activity | ||
| - for "analysis" standard requirements: see platform safety plan in PMP |
There was a problem hiding this comment.
It is not clear why S-CORE may tailor this. This has to be explained here already and confirmed by the platform safety plan in PMP. Also this would need to be incorporated into another gd doc (e.g. the one for architecture).
There was a problem hiding this comment.
@PandaeDo , see above, still missing some standard requirements, not covered by safety analysis, either you take them in your process area or you agree to tailor them out
process/process_areas/process_management/process_management_workproducts.rst
Show resolved
Hide resolved
aschemmel-tech
left a comment
aschemmel-tech
left a comment
There was a problem hiding this comment.
Approve to unblock - open comments should be resolved
Bump the ISO26262 coverage to 100%
update tailoring of iso26262
tailoring of std_wp__iso26262__software_1052, and std_req__iso26262__software_1041
tailoring of std_req__iso26262__software_11147*, std_req__iso26262__software_11148*, std_req__iso26262__software_11149*
tailoring of std_req__iso26262__analysis_641 to std_req__iso26262__analysis_644
tailoring of std_req__iso26262__analysis_744
tailoring of std_req__iso26262__management_5431, std_req__iso26262__management_5433, std_req__iso26262__management_5434, std_req__iso26262__management_5435
tailoring of std_req__iso26262__management_6464
tailoring of std_req__iso26262__software_543
tailoring of
tailoring of std_req__iso26262__software_841, std_req__iso26262__software_842, std_req__iso26262__software_844, std_req__iso26262__software_845
tailoring of std_req__iso26262__software_app_c_41, std_req__iso26262__software_app_c_42, std_req__iso26262__software_app_c_43, std_req__iso26262__software_app_c_44, std_req__iso26262__software_app_c_45