Skip to content

Add AoU forwarding functionality#283

Open
castler wants to merge 4 commits into
mainfrom
js_add_aou_forwarding
Open

Add AoU forwarding functionality#283
castler wants to merge 4 commits into
mainfrom
js_add_aou_forwarding

Conversation

@castler

@castler castler commented Jun 20, 2026

Copy link
Copy Markdown
Contributor

With this PR it is possible to forward AoUs to your dependent if you are not able to copy with it.

@github-actions

Copy link
Copy Markdown

Coverage Report

Coverage report was generated.

Full report can be downloaded from the CI artifacts (expand Artifacts at the bottom of the run).

Overall coverage rate:

lines......: 82.7%
functions......: 49.0%

@castler castler force-pushed the js_add_aou_forwarding branch from c08ba68 to 34879c6 Compare June 20, 2026 13:39
@github-actions

Copy link
Copy Markdown

Coverage Report

Coverage report was generated.

Full report can be downloaded from the CI artifacts (expand Artifacts at the bottom of the run).

Overall coverage rate:

lines......: 82.7%
functions......: 49.0%

@castler castler force-pushed the js_add_aou_forwarding branch from 34879c6 to df2504d Compare June 20, 2026 13:57
@castler castler marked this pull request as ready for review June 20, 2026 14:00
castler and others added 4 commits June 20, 2026 16:38
Implement automatic and chain-forwarding of Assumptions of Use (AoU)
between dependable elements:

- Add ForwardedAoUInfo provider carrying own and chain-forwarded AoU
  lobster entries as depsets
- Add aou_lobster field to AssumptionsOfUseInfo for lobster extraction
  from AoU TRLC sources
- Extend dependable_element rule to collect own AoUs from deps,
  receive chain-forwarded AoUs, and emit ForwardedAoUInfo
- Add aou_forwarding attribute accepting a YAML file that selects
  which received AoUs to forward further (with mandatory justification)
- Add aou_forwarding_to_lobster.py tool for filtering received AoUs
  based on the forwarding YAML (supports versioned lobster tags)
- Add lobster_aou.yaml config for lobster-trlc extraction of AoU records
- Extend lobster_de.conf.tpl with Forwarded AoUs tier

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Test the aou_forwarding_to_lobster filter logic:
- Filtering by AoU ID from forwarding YAML
- Error on non-existent AoU ID
- Versioned tag matching (req Pkg.Name@1 matches aou_id Pkg.Name)
- Full versioned ID matching

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Extend the examples with a three-level forwarding chain:

  other_seooc (defines TimingConstraint and SpaceConstraint AoUs)
      ↑ deps
  safety_software_seooc_example (chain-forwards TimingConstraint)
      ↑ deps
  integrator_seooc (receives forwarded AoUs, has own requirements)

- Add AoU TRLC sources to other_seooc and wire assumptions_of_use
- Add aou_forwarding.yaml to seooc for chain-forwarding
- Create integrator_seooc with assumed system requirements, feature
  requirements, and component requirements

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Tool requirements (TRLC):
- Add Forward_AoU_To_Dependees use case
- Add potential errors: AoU_Silently_Dropped, Invalid_Forwarding_YAML_Accepted
- Add tool requirements: Forward_Own_AoUs_To_Dependees,
  Chain_Forward_Received_AoUs, Reject_Unknown_AoU_In_Forwarding_YAML,
  Include_Forwarded_AoUs_In_Traceability

User documentation:
- Extend requirements.md with AoU Forwarding section explaining both
  automatic and chain-forwarding mechanisms
- Add aou_forwarding attribute to dependable_element in rule_reference.rst
- Add Forwarded AoUs to the dependable element concept in general.md

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

1 participant