Add covers flag to meta model to link aou by FScholPer · Pull Request #489 · eclipse-score/docs-as-code

FScholPer · 2026-04-14T14:44:57Z

📌 Description

Adds Covers flag for linking aou to requirements(https://eclipse-score.github.io/process_description/main/process_areas/requirements_engineering/guidance/requirements_process_reqs.html#gd_req__req_linkage_aou)

🚨 Impact Analysis

This change does not violate any tool requirements and is covered by existing tool requirements
This change does not violate any design decisions
Otherwise I have created a ticket for new tool qualification

✅ Checklist

Added/updated documentation for new or changed features
Added/updated tests to cover the changes
Followed project coding standards and guidelines

Frank Scholter Peres frank.scholter_peres@mercedes-benz.com, Mercedes-Benz Tech Innovation GmbH
Provider Information

github-actions · 2026-04-14T14:45:30Z

License Check Results

🚀 The license check job ran with the Bazel command:

bazel run --lockfile_mode=error //src:license-check

Status: ⚠️ Needs Review

Click to expand output

[License Check Output]
Extracting Bazel installation...
Starting local Bazel server (8.4.2) and connecting to it...
INFO: Invocation ID: 585067ff-9e4c-47c9-8d1f-f4f49b620a95
Computing main repo mapping: 
Loading: 
Loading: 0 packages loaded
Loading: 0 packages loaded
WARNING: Target pattern parsing failed.
ERROR: Skipping '//src:license-check': no such target '//src:license-check': target 'license-check' not declared in package 'src' defined by /home/runner/work/docs-as-code/docs-as-code/src/BUILD
Analyzing: 0 targets (1 packages loaded)
ERROR: no such target '//src:license-check': target 'license-check' not declared in package 'src' defined by /home/runner/work/docs-as-code/docs-as-code/src/BUILD
INFO: Elapsed time: 5.148s
INFO: 0 processes.
ERROR: Build did NOT complete successfully
ERROR: Build failed. Not running target

github-actions · 2026-04-17T12:45:29Z

The created documentation from the pull request is available at: docu-html

aschemmel-tech

matches metamodel and process requirement gd_req__req_linkage_aou

AlexanderLanin · 2026-05-06T10:38:53Z

 ]
 ```

+## SEooC Traceability and AoU Linking


So far the metamodel is not described at all in docs-as-code, thats the first element which has a description. If thats something we should have, this seems like a good start. But if not, then we dont need this either.

@MaximilianSoerenPollak @a-zw

That makes no sense to me. Such documentation belongs into the process docs. Repeating it here just invites trouble via inconsistencies.

Undo all the changes in this file.

AlexanderLanin · 2026-05-06T10:42:55Z

+     Feature Requirements             covers     Assumptions of Use (AoU)
+     Component Requirements           covers     Assumptions of Use (AoU)


I'm not sure this will work.

Feature requirements are in score repo?!
Component requirements are in "dependable module" repos?!
Where are the assumptions of use? In score or in "dependable module" repos, or both?

Is this actually described somewhere by now? Sorry, I'm not up to date here.

Latest decision is dec_rec__platform__feature_delivery:

Feature architecture and component artifacts are moved to SW-Module repositories. Feature requirements and logical feature interfaces remain in the S-CORE [platform] repository.

The answer here is "both" I suppose. My understanding is that we do not distinguish between "platform" and "module" for AoUs but we do for requirements. Thus, feature requirements in platform repo cover AoUs in the platform repo and component requirements in module repos cover AoUs in module repos (potentially other module repos though).

AlexanderLanin · 2026-05-06T10:44:09Z

+  **Process reference**: :need:`gd_req__req_linkage_aou` — Requirements SHALL be linked to AoU
+  via covers if they already cover these.


Let's not repeat that here, it's already covered by satisfies link.

AlexanderLanin · 2026-05-06T10:46:50Z

+
+
+.. Positive Test: feat_req pointing to an aou_req via covers is valid.
+#EXPECT-NOT: feat_req__covers__good_1.covers (['aou_req__covers__target']): does not follow pattern `^aou_req__.*$`.


I hope that error message is not accurate?! 😆
So it will not appear anyway. Therefore this test doesn't actually test anything.

Recommendation:

No errors regarding covers link: #EXPECT-NOT: covers

a-zw · 2026-05-06T11:49:24Z

 ]
 ```

+## SEooC Traceability and AoU Linking


That makes no sense to me. Such documentation belongs into the process docs. Repeating it here just invites trouble via inconsistencies.

Undo all the changes in this file.

a-zw · 2026-05-06T11:52:29Z

+     Feature Requirements             covers     Assumptions of Use (AoU)
+     Component Requirements           covers     Assumptions of Use (AoU)


Latest decision is dec_rec__platform__feature_delivery:

Feature architecture and component artifacts are moved to SW-Module repositories. Feature requirements and logical feature interfaces remain in the S-CORE [platform] repository.

The answer here is "both" I suppose. My understanding is that we do not distinguish between "platform" and "module" for AoUs but we do for requirements. Thus, feature requirements in platform repo cover AoUs in the platform repo and component requirements in module repos cover AoUs in module repos (potentially other module repos though).

a-zw · 2026-05-06T11:54:52Z

+  covers:
+    incoming: covered by
+    outgoing: covers
+    # req-Id: gd_req__req_linkage_aou
+    # Requirement-to-AoU linking per SCORE process specification


Suggested change

covers:

incoming: covered by

outgoing: covers

# req-Id: gd_req__req_linkage_aou

# Requirement-to-AoU linking per SCORE process specification

# req-Id: gd_req__req_linkage_aou

covers:

incoming: covered by

outgoing: covers

a-zw · 2026-05-06T11:58:58Z

+  **Purpose**: In SEooC (Safety Element Out of Context) development, AoU capture the
+  operational context and constraints that validate safety cases. Requirements "cover"
+  (are bound to) specific assumptions.
+


Suggested change

**Purpose**: In SEooC (Safety Element Out of Context) development, AoU capture the

operational context and constraints that validate safety cases. Requirements "cover"

(are bound to) specific assumptions.

No need to be chatty here. The reference to gd_req__req_linkage_aou is sufficient "purpose".

FScholPer added 2 commits April 13, 2026 14:25

add covers Auo flag and documentation

cdde467

added tests

755ccba

FScholPer requested review from AlexanderLanin, MaximilianSoerenPollak, dcalavrezo-qorix and nradakovic as code owners April 14, 2026 14:44

github-project-automation Bot added this to INF - Infrastructure Community Apr 14, 2026

github-project-automation Bot moved this to Backlog in INF - Infrastructure Community Apr 14, 2026

Merge branch 'main' into add_covers_meta_model

addc974

FScholPer and others added 3 commits April 14, 2026 15:03

fix test and remove negative tests

131b062

Merge branch 'main' into add_covers_meta_model

b788509

removed about from content wording

1e8fc60

Merge branch 'main' into add_covers_meta_model

6bd0f04

aschemmel-tech reviewed Apr 29, 2026

View reviewed changes

Merge branch 'main' into add_covers_meta_model

4eff90a

AlexanderLanin reviewed May 6, 2026

View reviewed changes

a-zw suggested changes May 6, 2026

View reviewed changes

		Feature Requirements covers Assumptions of Use (AoU)
		Component Requirements covers Assumptions of Use (AoU)

		Process reference: :need:`gd_req__req_linkage_aou` — Requirements SHALL be linked to AoU
		via covers if they already cover these.



		.. Positive Test: feat_req pointing to an aou_req via covers is valid.
		#EXPECT-NOT: feat_req__covers__good_1.covers (['aou_req__covers__target']): does not follow pattern `^aou_req__.*$`.

	Purpose: In SEooC (Safety Element Out of Context) development, AoU capture the
	operational context and constraints that validate safety cases. Requirements "cover"
	(are bound to) specific assumptions.

Conversation

FScholPer commented Apr 14, 2026

📌 Description

🚨 Impact Analysis

✅ Checklist

Uh oh!

github-actions Bot commented Apr 14, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

License Check Results

Uh oh!

github-actions Bot commented Apr 17, 2026

Uh oh!

aschemmel-tech left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

github-actions Bot commented Apr 14, 2026 •

edited

Loading