Skip to content

Conversation

@pahmann
Copy link
Member

@pahmann pahmann commented Dec 16, 2025

While the derivation technique mostly name the right technique out of the pool of available options in the process description the actual derivation method name do not follow the process_description and platform management plan guideline. This PR fixes the terminology for existing derivation techniques.

The "DerivationTechnique" called "Analyzing architecture and design" is kept untouched in this PR as this is not in the list of derivation techniques of S-CORE.

Fixes #64

The "DerivationTechnique" called "Analyzing architecture and design" is untouched as this is not in the list of derivation techniques of S-CORE

Fixes #64

Signed-off-by: Philipp Ahmann <philipp.ahmann@de.bosch.com>
@github-actions
Copy link

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

@pahmann pahmann requested a review from PiotrKorkus December 17, 2025 09:49
@pahmann
Copy link
Member Author

pahmann commented Jan 9, 2026

@castler, @hoe-jo, @LittleHuba, @ramceb, @nradakovic, @4og
anyone willing to take a look at this PR?
This was issued to make baselibs a bit more process compliant.

@4og
Copy link
Member

4og commented Jan 15, 2026

Hi @pahmann, thanks for the PR and sorry for the delayed response. We use baselibs internally and aim to keep our code aligned with S-CORE. Since this change affects many files, we need some time to ensure it doesn’t break anything on our side.

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.

Baselibs DerivationTechnique does not match naming convention of PMP verification plan

3 participants