Skip to content

Align platform testing to process description naming #2225

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.

Sign up for GitHub

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

Merged
masc2023 merged 1 commit into from
Nov 21, 2025
Merged

Align platform testing to process description naming #2225

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/platform_management_plan/safety_management.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -92,7 +92,7 @@ The following ISO 26262 defined safety work products are not relevant for the S
Note that stakeholder requirements (:need:`std_wp__iso26262__system_651`) are in scope of the project,
to be able to cover System and HW related failures which are usually covered by SW (e.g. end to end protection for ECU external communication).
But those are the "Assumed Technical Safety Requirements" of the SW platform SEooC and do not need to be tested by SEooC supplier.
I.e. the system testing is out of scope. Note that S-CORE will implement platform test of stakeholder requirements for demonstration,
I.e. the system testing is out of scope. Note that S-CORE will implement Platform Integration Test of stakeholder requirements for demonstration,
but these are not intended to be completely covering the stakeholder requirements.
There will be SW integration tests of feature requirements, as required by ISO 26262 part 6-10.
These may be reused by the users on their HW platform to cover Technical Safety Requirements towards the SW platform.
Expand Down
2 changes: 1 addition & 1 deletion docs/platform_management_plan/software_verification.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -130,7 +130,7 @@ There are the following different levels of integration and verification defined
These tests serve as an optional base for the integrator and will also be part of the
:need:`wp__verification_platform_ver_report`, but more on an informative character. The full scope
of clause 11 is tailored out accordingly for S-Core. Practically, this means S-CORE will implement
platform test of stakeholder requirements for demonstration, but these are not intended to completely
Platform Integration Test of stakeholder requirements for demonstration, but these are not intended to completely
covering all stakeholder requirements.

Verification Methods
Expand Down