Refine test level in PMP #2350
Refine test level in PMP #2350
Conversation
Further refinement for audit Deviation_13 and Action_43. Part of: eclipse-score/process_description#80 Signed-off-by: Philipp Ahmann <Philipp.Ahmann@de.bosch.com>
pahmann
requested review from
PhilipPartsch,
aschemmel-tech and
masc2023
as code owners
|
The created documentation from the pull request is available at: docu-html |
| #. feature requirements | ||
|
|
||
| 3. Platform testing (on reference hardware) | ||
| 3. **Testing of the embedded software** as Platform Integration Testing (on reference hardware) |
There was a problem hiding this comment.
Check, eclipse-score/process_description#464, embedded SW is tailored out std_wp__iso26262__software_1052, update of PMP pending (we deliver source code, not an embedded software), would rephrase it to Software integration verification platform level to verify the integration of features .....,
There was a problem hiding this comment.
Compare here, #2352
See also current statement in Safety Plan
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.
But if these are sufficiently also covering the TSRs must be analyzed and decided by the user.
There was a problem hiding this comment.
Consider also here: https://github.com/eclipse-score/process_description/pull/464/changes#r2623000202
Still missing some Standard Requirements, some are only relevant for embedded SW, which is not in scope, what is for the others?
|
|
||
| **Note:** These three levels translate to the levels of ISO 26262 part 6 clauses 9 to 11. The platform | ||
| testing will be executed by the integrator. S-CORE project only executes tests on reference hardware. | ||
| **Note:** These three levels from 1 to 3 translate to the levels of ISO 26262 part 6 clauses 9 (unit) to 11 (embedded software). |
There was a problem hiding this comment.
See above, embedded SW is not in our scope.
| #. feature requirements | ||
|
|
||
| 3. Platform testing (on reference hardware) | ||
| 3. **Testing of the embedded software** as Platform Integration Testing (on reference hardware) |
There was a problem hiding this comment.
Consider also here: https://github.com/eclipse-score/process_description/pull/464/changes#r2623000202
Still missing some Standard Requirements, some are only relevant for embedded SW, which is not in scope, what is for the others?
PandaeDo
left a comment
PandaeDo
left a comment
There was a problem hiding this comment.
No additional findings from my side. But I agree on those from Markus
Signed-off-by: Philipp Ahmann <philipp.ahmann@de.bosch.com>
pahmann
force-pushed
the
pahmann/verification-level-alignment
branch
from
0bcbba1 to
69d3f79
Compare
Signed-off-by: Philipp Ahmann <philipp.ahmann@de.bosch.com>
Further refinement for audit Deviation_13 and Action_43 which was covered already by earlier commits.
Action taken:
Part of: eclipse-score/process_description#80