Skip to content

fix: Restore accidentally deleted requirements #730

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
a-zw wants to merge 1 commit into
base: main
Choose a base branch
from
+49 −0
Open

fix: Restore accidentally deleted requirements #730

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
49 changes: 49 additions & 0 deletions process/process_areas/implementation/guidance/implementation_process_reqs.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -81,6 +81,55 @@ Diagram Attributes

.. _detailed_design_linkage:

Diagram Linkage

@masc2023 masc2023 Jun 30, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Compared it with https://eclipse-score.github.io/process_description/main/general_concepts/score_building_blocks_concept.html
seems ok, but the word Diagram is somehow misleading, should that not be called Detailed Design?

'''''''''''''''

.. gd_req:: Diagram Linkage check Component ID
:id: gd_req__impl_diagram_check_id
:status: valid
:version: 1
:tags: prio_2_automation, attribute, automated
:complies: std_req__iso26262__support_6421[version==1], std_req__iso26262__support_6425[version==1]
:satisfies: wf__sw_detailed_design[version==1]

Each diagram shall be linked to the corresponding component id via the attribute belongs_to.

@RolandJentschETAS RolandJentschETAS Jun 30, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

In detail design / implementation exists no sphinx elements anymore. There this requirement should be moved into the architecture process requirements.


.. gd_req:: Diagram Linkage Component ID

@RolandJentschETAS RolandJentschETAS Jun 30, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

See above. Shall be moved to architecture process requirements.

:id: gd_req__impl_diagram_linkage_id
:status: valid
:version: 1
:tags: prio_2_automation, attribute, automated
:complies: std_req__iso26262__support_6421[version==1], std_req__iso26262__support_6425[version==1]
:satisfies: wf__sw_detailed_design[version==1]

Each diagram shall be automatically linked (inverse direction) to the corresponding component id via the "belongs by" linkage.

@pahmann pahmann Jun 30, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

belongs by sounds a bit strange to me.
Options: contains, owns, has.
Eventually also "consists of" may be an option.

@masc2023 masc2023 Jun 30, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

It is according meta model, thus fine, should not be changed


.. gd_req:: Diagram Linkage includes
:id: gd_req__impl_diagram_check_includes
:status: valid
:version: 1
:tags: prio_2_automation, attribute, automated
:complies: std_req__iso26262__support_6421[version==1], std_req__iso26262__support_6425[version==1]
:satisfies: wf__sw_detailed_design[version==1]

Each diagram shall be linked to the corresponding

@RolandJentschETAS RolandJentschETAS Jun 30, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

This requirement can be removed. We have no sphinx needs in implementation / detail design anymore. Existing (optional) implementation diagrams (plantuml or drawio) are linked by path / filename to the unit. They are located in the docs folder of the component. The units are mentioned in the diagram as names of "boxes". There is no automation needed.

- SW Unit
- SW Unit Interface
Comment on lines +116 to +117

@a-zw a-zw Jun 30, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I'm sure the first two requirements should be restored, but I'm not sure about the other two since these seem to be quite specifically about units.

On the other hand, docs-as-code currently implements relations like "mod_view_sta includes comp".

@masc2023 masc2023 Jun 30, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

See above

Image

via the attribute includes.

.. gd_req:: Diagram Linkage includes
:id: gd_req__impl_diagram_linkage_includes
:status: valid
:version: 1
:tags: prio_2_automation, attribute, automated
:complies: std_req__iso26262__support_6421[version==1], std_req__iso26262__support_6425[version==1]
:satisfies: wf__sw_detailed_design[version==1]

Each diagram shall be automatically linked (inverse direction) to the corresponding

@RolandJentschETAS RolandJentschETAS Jun 30, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Should be removes. See above.

- SW Unit
- SW Unit Interface
via the "included by" linkage.

Diagram Checks
''''''''''''''

Expand Down
Loading