Skip to content

Commit a5f46ed

Browse files
committed
changing the word to platform integration test to match it to wording of other artifacts.
1 parent f45a389 commit a5f46ed

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

process/general_concepts/score_building_blocks_concept.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ enabling of feature integration for different use cases and domains. This includ
2727
applications. Thus the intention is, that the platform can be developed as a Safety
2828
Element out of Context (**SEooC**) (green box, top, 1 column). The objectives of the platform are
2929
expressed as concrete **Stakeholder Requirements** (blue box, top, 2nd column), which can be tested
30-
by provided **platform integration tests** (blue box, top, 5nd column) for reference hardware platforms. The
30+
by provided **Platform Integration Tests** (blue box, top, 5nd column) for reference hardware platforms. The
3131
platform consists of **Features** (yellow box, middle, 2nd column).
3232

3333
Further the project provides **Software Modules** (red box, middle, 1st column), which can also be

process/process_areas/verification/workproducts.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ Platform
3636
:status: valid
3737
:complies: std_wp__iso26262__support_952
3838

39-
platform integration testing verifies Stakeholder Requirements performed on reference HW.
39+
Platform integration testing verifies Stakeholder Requirements performed on reference HW.
4040
Depending on the nature of the project, respective tailoring (e.g. for reduced requirements
4141
coverage) has to be reflected in the :need:`wp__verification_plan` and :need:`wp__platform_safety_plan`.
4242

0 commit comments

Comments
 (0)