Repository navigation
Conversation
Resolves: eclipse-score/process_description#813 Signed-off-by: Philipp Ahmann <philipp.ahmann@de.bosch.com>
github-project-automation
Bot
added this to
S-CORE Roadmap and TLC - Technical Lead Circle
Contributor
|
Documentation preview for this pull request is available at: |
masc2023
reviewed
Oct 30, 2026
| components or software changes. A specific selection of sub sets is not planned. The fact that all existing and | ||
| automated tests get executed continuously covers the approach to identify regressions. | ||
|
|
||
| Additionally, manual and non-functional verification activities should be carried out on regular basis, |
Contributor
There was a problem hiding this comment.
manual test, non-functional verification is also manual, also in general all manual verification activities should or shall?
masc2023
reviewed
Oct 30, 2026
| Verification of non-functional requirements | ||
| ------------------------------------------- | ||
|
|
||
| Similar to the rare case of manual test execution also some requirements may not be verifiable by test but by analysis. |
Contributor
There was a problem hiding this comment.
but by other manual verification methods, e.g. checklist based analysis?
masc2023
reviewed
Oct 30, 2026
| Similar to the rare case of manual test execution also some requirements may not be verifiable by test but by analysis. | ||
|
|
||
| To verify such a non-functional or not feasibly testable requirement, the respective links for traceability need to be | ||
| established as for any other automated test case. Therefore, the documentation for non-functional verification uses |
Contributor
There was a problem hiding this comment.
any other manual or automated test cases, as manual test also still exists
masc2023
reviewed
Oct 30, 2026
| established as for any other automated test case. Therefore, the documentation for non-functional verification uses | ||
| the same templates as any other automated or manual test and especially includes the Record Properties. | ||
|
|
||
| The Record Properties for non-functional verification should be testtype `requirements-based` and derivation technique `requirement-analysis`. |
Contributor
There was a problem hiding this comment.
would not be better manual-requirement-verification, is there only analysis existing, e.g. for Process Requirements, Audit or Assessment is also possible method
masc2023
reviewed
Oct 30, 2026
|
|
||
| The Record Properties for non-functional verification should be testtype `requirements-based` and derivation technique `requirement-analysis`. | ||
|
|
||
| The non-functional verification requires a script to be provided which describes the analysis steps performed and their result. |
Contributor
There was a problem hiding this comment.
Would it not be easier, if a standard method from our process framework is used, and just link to it?
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Resolves: eclipse-score/process_description#813