Skip to content

Conversation

@Deepa1-Patil
Copy link

fix wording

…h-patch-2

Improvement: Add types details to requirements_concept
@Deepa1-Patil Deepa1-Patil requested a review from pahmann as a code owner October 29, 2025 08:58
Element out of Context (**SEooC**) (green box, top, 1 column). The objectives of the platform are
expressed as concrete **Stakeholder Requirements** (blue box, top, 2nd column), which can be tested
by provided **Platform Tests** (blue box, top, 5nd column) for reference hardware platforms. The
by provided **platform integration tests** (blue box, top, 5nd column) for reference hardware platforms. The
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we take Platform Integration Tests as they are kind of a fixed statement and it would match also line 29 which calls it Stakeholder Requirements and not stakeholder requirements

* - Requirements Type
- The requirement type defines which category the requirement relates to. Following categories are defined: [Functional, Interface, Process, Non-Functional]

- Functional: If implemented can be verified by a test (unit, integration)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a good addition, but it may be an additional change not related to the ticket.
If we get additional comments on this, the simple change of words would be delayed due to new content being provided. A split could make sense. Let us have a quick chat about it.

:complies: std_wp__iso26262__support_952

Platform Testing verifies Stakeholder Requirements performed on reference HW.
platform integration testing verifies Stakeholder Requirements performed on reference HW.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Definitely here we need a capital P as it is a start of a sentence.

@pahmann
Copy link

pahmann commented Oct 30, 2025

fix wording

Based on your description "fix wording" you could have a naming description like changing the wording to platform integration test to match it to the wording of other artifacts.

Element out of Context (**SEooC**) (green box, top, 1 column). The objectives of the platform are
expressed as concrete **Stakeholder Requirements** (blue box, top, 2nd column), which can be tested
by provided **platform integration tests** (blue box, top, 5nd column) for reference hardware platforms. The
by provided **Platform Integration Tests** (blue box, top, 5nd column) for reference hardware platforms. The
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just spotted 5nd which should be 5th

@Deepa1-Patil Deepa1-Patil force-pushed the feature/issue_164_rename_platform_test branch from a5f46ed to e10154a Compare November 5, 2025 12:58
@AlexanderLanin
Copy link
Member

We cannot modify our main branch here. Please retarget the PR to where it should go.

resolves: eclipse-score#164
Signed-off-by: Patil Deepa (ETAS-ECM/XPC-Fe2) <[email protected]>
@Deepa1-Patil Deepa1-Patil force-pushed the feature/issue_164_rename_platform_test branch from e10154a to 8235b8c Compare November 5, 2025 13:33
@pahmann
Copy link

pahmann commented Nov 5, 2025

We cannot modify our main branch here. Please retarget the PR to where it should go.

We do not want to merge this. We wanted to have upfront review on changes, before we go to S-CORE unprepared. This PR will be closed very soon.

@pahmann
Copy link

pahmann commented Nov 5, 2025

PR transferred to S-CORE project as internal review successfully conducted.
See: eclipse-score#233

@pahmann pahmann closed this Nov 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants