EPIC: Define and Align Tools with Process Requirements

[masc2023]

What

Align tools with process requirements
Align mandatory, optional process requirements (e.g. mandatory links defined in process and optional in the tool)

How

Create sub-issue for each topic

• Doc-as-code #541

Estimates for realization

Depending on the topic

Category

• Affects Detailed Design

Requirements / Architecture

• Requirements / Architecture are not affected by this change?

[Chidananda-Swamy]

@masc2023
I'm Interested to take up this epic

[masc2023]

@masc2023 I'm Interested to take up this epic

Thanks for volunteering @Chidananda-Swamy, are you able to join next Tuesday Safety Community Meeting, then we could discuss it and assign it to you?

[Chidananda-Swamy]

@masc2023 I'm Interested to take up this epic

Thanks for volunteering @Chidananda-Swamy, are you able to join next Tuesday Safety Community Meeting, then we could discuss it and assign it to you?

@masc2023
Thanks for the response.
Sure, Will plan to attend the meeting.

[aschemmel-tech]

Process requirements overview: https://eclipse-score.github.io/process_description/main/standards/process_reqs_list/index.html
to match with the list provided by the docs-as-code tool: https://eclipse-score.github.io/docs-as-code/main/internals/requirements/process_overview.html

[aschemmel-tech]

check mandatory/optional process requirements against the implementation in https://github.com/eclipse-score/docs-as-code/blob/main/src/extensions/score_metamodel/metamodel.yaml

[aschemmel-tech]

This issue is also connected to eclipse-score/score#2469, which can be used to document any PR needed in the score repository for the above changes.