map and tailor iso21434 work products #483
Conversation
tailor work products not in scope map work products in scope to achieve 100% coverage Replase #482, has not merged correctly
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 |
|
@sunildevda kindly also provide your feedback on this PR. |
sunildevda
left a comment
sunildevda
left a comment
There was a problem hiding this comment.
added a finding. could you please check
| :status: valid | ||
| :tags: doc_lifecycle_model_2 | ||
| :complies: std_wp__iso26262__management_651, std_wp__iso26262__management_751, std_wp__iso26262__system_652, std_wp__iso26262__system_653, std_wp__iso26262__system_654, std_wp__iso26262__system_655, std_wp__iso26262__system_656, std_wp__iso26262__system_657, std_wp__iso26262__system_751, std_wp__iso26262__system_752, std_wp__iso26262__system_851, std_wp__iso26262__system_852, std_wp__iso26262__software_652, std_wp__iso26262__software_1052, std_wp__iso26262__software_1151, std_wp__iso26262__software_1152, std_wp__iso26262__software_app_c_52, std_wp__iso26262__software_app_c_54, std_wp__iso26262__software_app_c_57, std_wp__iso26262__support_551, std_wp__iso26262__support_552, std_wp__iso26262__support_553, std_wp__iso26262__support_554, std_wp__iso26262__support_555, std_wp__iso26262__support_1351, std_wp__iso26262__support_1352, std_wp__iso26262__support_1353, std_wp__iso26262__support_1451, std_wp__iso26262__support_1452, std_wp__iso26262__support_1551, std_wp__iso26262__support_1651, std_wp__iso26262__analysis_551, std_wp__iso26262__analysis_552, std_wp__isopas8926__4522 | ||
| :complies: std_wp__iso26262__management_651, std_wp__iso26262__management_751, std_wp__iso26262__system_652, std_wp__iso26262__system_653, std_wp__iso26262__system_654, std_wp__iso26262__system_655, std_wp__iso26262__system_656, std_wp__iso26262__system_657, std_wp__iso26262__system_751, std_wp__iso26262__system_752, std_wp__iso26262__system_851, std_wp__iso26262__system_852, std_wp__iso26262__software_652, std_wp__iso26262__software_1052, std_wp__iso26262__software_1151, std_wp__iso26262__software_1152, std_wp__iso26262__software_app_c_52, std_wp__iso26262__software_app_c_54, std_wp__iso26262__software_app_c_57, std_wp__iso26262__support_551, std_wp__iso26262__support_552, std_wp__iso26262__support_553, std_wp__iso26262__support_554, std_wp__iso26262__support_555, std_wp__iso26262__support_1351, std_wp__iso26262__support_1352, std_wp__iso26262__support_1353, std_wp__iso26262__support_1451, std_wp__iso26262__support_1452, std_wp__iso26262__support_1551, std_wp__iso26262__support_1651, std_wp__iso26262__analysis_551, std_wp__iso26262__analysis_552, std_wp__isopas8926__4522, std_wp__isosae21434__assessment_15331, std_wp__isosae21434__assessment_15531 |
There was a problem hiding this comment.
because std_wp__isosae21434__assessment_15331 and std_wp__isosae21434__assessment_15531 are out of scope, i think even std_wp__isosae21434__assessment_15831 should be also out of scope. As to give a meaning value, we would need system know how which is missing as out of context middleware platform provider.
There was a problem hiding this comment.
because std_wp__isosae21434__assessment_15331 and std_wp__isosae21434__assessment_15531 are out of scope, i think even std_wp__isosae21434__assessment_15831 should be also out of scope. As to give a meaning value, we would need system know how which is missing as out of context middleware platform provider.
As a consequence of your proposal, would we not even then have to cancel std_wp__isosae21434__assessment_15931?
The intention here is to make assumptions of use, thus also on impact, e.g. safety.
There was a problem hiding this comment.
the way i see it, giving "quantitative values" is tricky without having system know how -> without knowing the damage scenario at the system/vehicle level.
std_wp__isosae21434__assessment_15931 is still possible (to large extent) based on the "qualitative" assessment of the risk.
But at same time, dont think this point is critical. we can see how things goes and if needed adapt it later. or like you mentioned we assume things (which we write down clearly) and based on this we give a quantitative value.
tailor work products not in scope
map work products in scope to achieve 100% coverage
Replase #482, has not merged correctly