-
Notifications
You must be signed in to change notification settings - Fork 16
update tailoring of iso26262 #464
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -18,7 +18,8 @@ Guideline | |
| .. gd_guidl:: Requirements Guideline | ||
| :id: gd_guidl__req_engineering | ||
| :status: valid | ||
| :complies: std_req__isopas8926__44421, std_req__isopas8926__44422, std_req__isopas8926__44423 | ||
| :complies: std_req__isopas8926__44421, std_req__isopas8926__44422, std_req__isopas8926__44423, | ||
| std_req__iso26262__software_app_c_41, std_req__iso26262__software_app_c_43 | ||
|
|
||
| This document describes the general guidances for requirements based on the concept which is defined in :need:`[[title]]<doc_concept__req_process>`. | ||
|
|
||
|
|
@@ -264,7 +265,8 @@ Tailoring | |
| .. gd_guidl:: Requirements Tailored | ||
| :id: gd_guidl__req_tailored | ||
| :status: valid | ||
| :complies: std_req__iso26262__system_6423, std_req__iso26262__system_6424, std_req__iso26262__system_6425, std_req__iso26262__software_643, std_req__iso26262__software_644, std_req__iso26262__software_646 | ||
| :complies: std_req__iso26262__system_6423, std_req__iso26262__system_6424, std_req__iso26262__system_6425, std_req__iso26262__software_643, std_req__iso26262__software_644, std_req__iso26262__software_646, | ||
| std_req__iso26262__analysis_641, std_req__iso26262__analysis_642, std_req__iso26262__analysis_643, std_req__iso26262__analysis_644 | ||
|
|
||
| This part of the guideline links to all the requirements which are not fulfilled by the | ||
| requirements engineering process. Make sure these are tailored out in the safety/security/quality plans | ||
|
|
@@ -274,3 +276,4 @@ Tailoring | |
|
|
||
| - 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 | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 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).
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @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
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Covered with this #469 |
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,44 @@ | ||
| .. | ||
| # ******************************************************************************* | ||
| # Copyright (c) 2025 Contributors to the Eclipse Foundation | ||
| # | ||
| # See the NOTICE file(s) distributed with this work for additional | ||
| # information regarding copyright ownership. | ||
| # | ||
| # This program and the accompanying materials are made available under the | ||
| # terms of the Apache License Version 2.0 which is available at | ||
| # https://www.apache.org/licenses/LICENSE-2.0 | ||
| # | ||
| # SPDX-License-Identifier: Apache-2.0 | ||
| # ******************************************************************************* | ||
|
|
||
| Guideline | ||
| ========= | ||
|
|
||
| Tool Qualification | ||
| ================== | ||
|
|
||
| .. gd_guidl:: Tool Qualification | ||
| :id: gd_guidl__tool_qualification | ||
| :status: valid | ||
| :complies: std_req__iso26262__support_11491, std_req__iso26262__support_11492 | ||
|
|
||
| | The tool qualification shall be based on the method validation of the software tool. | ||
|
|
||
| Tailoring | ||
| ========= | ||
|
|
||
| .. gd_guidl:: Tool Requirements Tailored | ||
| :id: gd_guidl__tool_req_tailored | ||
| :status: valid | ||
| :complies: std_req__iso26262__support_11471, std_req__iso26262__support_11472, std_req__iso26262__support_11473, std_req__iso26262__support_11474, | ||
| std_req__iso26262__support_11481, std_req__iso26262__support_11482, std_req__iso26262__support_11483 | ||
|
|
||
|
|
||
| This part of the guideline links to all the requirements which are not fulfilled by the | ||
| tool management process. Make sure these are tailored out in the safety plans | ||
| for your project (documented in the PMP). Reasoning given below must be confirmed there. | ||
|
|
||
| The reasoning is: | ||
|
|
||
| - Some methods for tool qualification are not applied |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -142,7 +142,7 @@ Tailoring | |
| :id: gd_guidl__verification_req_tailored | ||
| :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, | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. need also to include reasoning below
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @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
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Covered with this #468 |
||
| std_req__iso26262__software_1141, std_req__iso26262__software_1142, std_req__iso26262__software_1143, std_req__iso26262__software_1144 | ||
|
|
||
| This part of the guideline links to all the requirements which are not fulfilled by the | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.