process: improve impact analysis #642
Open
+117
−88
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
License Check Results🚀 The license check preparation job ran successfully. Status: Click to expand output |
|
The created documentation from the pull request is available at: docu-html |
PandaeDo
reviewed
Mar 12, 2025
|
|
||
| This section describes in detail which steps need to be performed for a Change Request. | ||
| This section describes in detail which steps need to be performed for a Change Request. They may |
There was a problem hiding this comment.
I think the sentence helps only when criteria are mentioned like changes with the same impact shall be combined. With separated impact shall be described in multiple change requests.
There was a problem hiding this comment.
Did not get your point, Impact analysis is to be done in the created Change Request, and document, after that you may know the impact on affected work products and generate multiple issues, which is one of the complex examples here
https://eclipse-score.github.io/score/main/platform_management_plan/change_management.html
There was a problem hiding this comment.
Sorry. My comment is to the second sentence "They may be combined in on Change Request or split to multiple Change Requests, if necessary." When both is possible we can delete it or better give some criteria when we aspect the split or the combination.
There was a problem hiding this comment.
Give some criteria
There was a problem hiding this comment.
Proposal: Changes with the same impact may be combined in one Change Request. If they cause different impact split it into multiple Change requests.
There was a problem hiding this comment.
Lets talk latest tomorrow in our meeting, I think we have not the same understanding here
PandaeDo
reviewed
Mar 12, 2025
...cess/process_areas/change_management/guidance/change_management_impact_analysis_template.rst
Outdated
Show resolved
Hide resolved
masc2023
force-pushed
the
masc2023_improve_chm_impact_analysis
branch
2 times, most recently
from
555d540 to
dd80c63
Compare
Impact Analysis Template modified Template shall be copied to Issue for planning Add missing compliance mapping to ISO 26262, ASPICE Add Change Management Plan Work Product, realized as part of Platform Management Plan Resolves: #621
masc2023
force-pushed
the
masc2023_improve_chm_impact_analysis
branch
from
dd80c63 to
5a51a01
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Impact Analysis Template modified
Template shall be copied to Issue for planning
Resolves: #621