Skip to content

Conversation

@aschemmel-tech
Copy link
Contributor

Ref: Resolves: #98

@aschemmel-tech aschemmel-tech marked this pull request as draft July 4, 2025 12:04
@aschemmel-tech aschemmel-tech force-pushed the aschemmel-tech-process-req-table branch from 66a75f9 to b8f0d35 Compare July 4, 2025 12:05
@github-actions
Copy link

github-actions bot commented Jul 4, 2025

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

@aschemmel-tech aschemmel-tech marked this pull request as ready for review July 4, 2025 12:33
masc2023
masc2023 previously approved these changes Jul 4, 2025
Copy link
Contributor

@masc2023 masc2023 left a comment

Choose a reason for hiding this comment

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

Checked only CHM, PRM, TLM and general, gave some comments about draft and priority

:id: gd_req__change__attr_affected_wp
:status: valid
:tags: chm, attribute, mandatory
:status: draft
Copy link
Contributor

Choose a reason for hiding this comment

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

why is that draft? I assume, that we have an impact analysis tool, which gives us affected elements and thus indirectly also the work products to enter her?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I set this to draft, because from the description I could not several questions: Shall it be manual/automated? As a (new) Feature Request is also a Change Request, what would I put here? ... So I think it could not be implemented without refinement.

:id: gd_req__change__tool_impact_analysis
:status: valid
:tags: chm, check, tool
:tags: prio_3_automation, check, tool
Copy link
Contributor

Choose a reason for hiding this comment

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

Why Prio 3, would assume that is good to show in audit, how we can do impact analysis with that?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

As you say "is good" - but I would expect we can pass the audit without this. And also expect significant effort if we cannot take over an existing tool.

Copy link
Contributor

@PandaeDo PandaeDo left a comment

Choose a reason for hiding this comment

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

Fine for me.

Copy link
Contributor

@MaximilianSoerenPollak MaximilianSoerenPollak left a comment

Choose a reason for hiding this comment

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

I had some questions / comments

@aschemmel-tech aschemmel-tech force-pushed the aschemmel-tech-process-req-table branch from 9f29519 to 76f5db9 Compare July 8, 2025 08:37
Copy link
Contributor

@hoe-jo hoe-jo left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Contributor

@MaximilianSoerenPollak MaximilianSoerenPollak left a comment

Choose a reason for hiding this comment

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

Looks okay from tooling team side.

Copy link
Contributor

@kroehnd kroehnd left a comment

Choose a reason for hiding this comment

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

Looks good to me

@aschemmel-tech aschemmel-tech merged commit 5bce5ca into main Jul 10, 2025
5 checks passed
@aschemmel-tech aschemmel-tech deleted the aschemmel-tech-process-req-table branch July 10, 2025 12:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Req Eng: Tool Requirements Implemented

8 participants