Releases: eclipse-score/process_description
v1.4.0
v1.4.0
Module Name: process_description
Release Tag: v1.4.0
Origin Release Tag: v1.3.1
Release Commit Hash: d057079
Release Date: 2025-12-09
Overview
The module process_description provides a process model establishing organization rules for developing open source software in the automotive industry, which can be used in safety and security context.
The process model provides processes, which conform to state-of the art standards
ASPICE 4.0
ISO 26262
ISO 21434
ISO PAS 8926
This is the third official release, version v1.4.0.
Previous release was v1.3.1.
Disclaimer
This release note does not "release for production", as it does not come with a safety argumentation and a performed safety assessment.
The work products compiled in the safety package are created with care according to a process satisfying standards, but the project, being a non-profit and open source organization, can not take over any liability for its content.
New Features
Process model gives compliance with ISO 26262, ISO 21434, ISOPAS 8926 and ASPICE 4.0 (https://eclipse-score.github.io/process_description/main/index.html).
Initial Security Analysis Process
Project Lead Role replaces Technical Project Lead Role (removed)
The process model contains
General concepts e.g. for Building Blocks and their traceability
Process meta model for proper modeling
Process areas covering the required standards
Roles, Work Products, Workflows defining the process areas
Standard overview and coverage information
Folder templates for simplifying deployment for users
Improvements
- Add score_sync_toml extension by @ubmarco in #238
- Add explanation that components with safety rating have an red border. by @RolandJentschETAS in #239
- Add security attribute to template folder by @masc2023 in #395
- Remove Technical Lead Role by @masc2023 in #396
- Create Req Inspection Template in Folders by @aschemmel-tech in #229
- Align Verification to Problem Resolution process area structure by @pahmann in #400
- Add links to pmp by @RolandJentschETAS in #399
- Improvement: fix linking by @RolandJentschETAS in #402
- Update safety mgt templates after piloting by @aschemmel-tech in #401
- Improvement: Add check for needextend by @PandaeDo in #406
- rework release templates by @masc2023 in #232
- Improvement: Safety Analysis for ML 2 by @PandaeDo in #408
- initial draft of new process area security analysis by @masc2023 in #403
- update readme, form and content by @masc2023 in #404
- Add SW component qualification to verification by @pahmann in #412
- Remove concrete tool name from verification process by @pahmann in #407
- Improvement 397 remove create empty puml requirement by @RolandJentschETAS in #413
- update general concpets by @masc2023 in #415
- fix remaining review findings and other issues by @RolandJentschETAS in #414
- Update implementation status requirement process reqs by @aschemmel-tech in #419
- Improvement: Implementation, ML2 by @PandaeDo in #241
- Bugfix: Overview picture restore after PR by @PandaeDo in #423
- process introduction explanation by @RolandJentschETAS in #424
- fix header spelling by @RolandJentschETAS in #425
- Safety management update - Repeat by @aschemmel-tech in #433
- Proposal to switch responsibility in safety training to Project Lead by @attifunel in #422
- add linkage to process requirements by @RolandJentschETAS in #431
- Fix safety management roles and escalation by @aschemmel-tech in #434
- Bump score_docs_as_code to 2.2.0 by @PhilipPartsch in #442
- Improvement: Safety Management ML 2 by @PandaeDo in #437
- Update tool verification report template by @alekseyborisyukvalidas in #432
- release v1.4.0 by @masc2023 in #444
- update release management by @masc2023 in #446
New Contributors
- @attifunel made their first contribution in #422
- @alekseyborisyukvalidas made their first contribution in #432
Full Changelog: v1.3.2...v1.4.0
Bug Fixes
- bugfix doc-as-code version upgrade to v2.0.3 by @masc2023 in #417
- Correct reference in module verification report by @pahmann in #421
- Correct Release Mgt Responsibles by @aschemmel-tech in #411
Compatibility
For a detailed list checkout here: https://github.com/eclipse-score/process_description/blob/main/MODULE.bazel
Major dependencies:
Doc-as-code: v2.2.0
Performed Verification
Initial Safety Audit by external assessor teams for every process area.
Known Issues
Issue 1: Standard requirements and work products are not yet fully mapped to the process model, https://eclipse-score.github.io/process_description//main/standards/index.html
Issue 2: Safety package containing external Audit report not available, due to open improvement proposals/recommendation from external assessor team, #77
Issue 3: Maturity level 1 achieved, but deploying is still ongoing also auditing per external auditor to achieve higher maturity levels,
#77, https://eclipse-score.github.io/process_description/main/index.html
Upgrade Instructions
not applicable for this release
Contact Information
For any questions or support, please contact the SW Process Development Community (https://github.com/orgs/eclipse-score/discussions/108) or raise an issue/discussion.
Contributors
Assets 2
v1.3.2
What's Changed
Other Changes
- 🐛 Add score_sync_toml extension by @ubmarco in #238
- Add explanation that components with safety rating have an red border. by @RolandJentschETAS in #239
- Add security attribute to template folder by @masc2023 in #395
- Remove Technical Lead Role by @masc2023 in #396
- Create Req Inspection Template in Folders by @aschemmel-tech in #229
- Align Verification to Problem Resolution process area structure by @pahmann in #400
- Add links to pmp by @RolandJentschETAS in #399
- Improvement: fix linking by @RolandJentschETAS in #402
- Update safety mgt templates after piloting by @aschemmel-tech in #401
- Improvement: Add check for needextend by @PandaeDo in #406
- rework release templates by @masc2023 in #232
- Improvement: Safety Analysis for ML 2 by @PandaeDo in #408
- initial draft of new process area security analysis by @masc2023 in #403
- update readme, form and content by @masc2023 in #404
- Add SW component qualification to verification by @pahmann in #412
- Remove concrete tool name from verification process by @pahmann in #407
- Improvement 397 remove create empty puml requirement by @RolandJentschETAS in #413
- Correct Release Mgt Responsibles by @aschemmel-tech in #411
- update general concpets by @masc2023 in #415
- fix remaining review findings and other issues by @RolandJentschETAS in #414
- bugfix doc-as-code version upgrade to v2.0.3 by @masc2023 in #417
New Contributors
- @ubmarco made their first contribution in #238
- @RolandJentschETAS made their first contribution in #239
Full Changelog: v1.3.1...v1.3.2
Contributors
Assets 2
v1.3.1
Module Name: process_description
Release Tag: v1.3.1
Origin Release Tag: v1.3.0
Release Commit Hash: 270e0ed
Release Date: 2025-11-10
Overview
The module process_description provides a process model establishing organization rules for developing open source software in the automotive industry, which can be used in safety and security context.
The process model provides processes, which conform to state-of the art standards
- ASPICE 4.0
- ISO 26262
- ISO 21434
- ISO PAS 8926
This is the second official release, version v1.3.1.
Previous release was v1.3.0.
Disclaimer
This release note does not "release for production", as it does not come with a safety argumentation and a performed safety assessment.
The work products compiled in the safety package are created with care according to a process satisfying standards, but the project, being a non-profit and open source organization, can not take over any liability for its content.
New Features
Process model gives compliance with ISO 26262, ISO 21434, ISOPAS 8926 and ASPICE 4.0 (https://eclipse-score.github.io/process_description/main/index.html).
The process model contains
- General concepts e.g. for Building Blocks and their traceability
- Process meta model for proper modeling
- Process areas covering the required standards
- Roles, Work Products, Workflows defining the process areas
- Standard overview and coverage information
- Folder templates for simplifying deployment for users
Improvements
- Remove TL Role from implementation and documentation process description by @PandaeDo in #226
- Update score_docs_as_code to 2.0.0 by @a-zw in #237
Full Changelog: v1.3.0...v1.3.1
Bug Fixes
not applicable for this release
Compatibility
For a detailed list checkout here: https://github.com/eclipse-score/process_description/blob/main/MODULE.bazel
Major dependencies:
- Doc-as-code: v2.0.0
Performed Verification
Initial Safety Audit by external assessor teams for every process area.
Known Issues
Issue 1: Standard requirements and work products are not yet fully mapped to the process model, https://eclipse-score.github.io/process_description//main/standards/index.html
Issue 2: Safety package containing external Audit report not available, due to open improvement proposals/recommendation from external assessor team, #77
Issue 3: Maturity level 1 achieved, but deploying is still ongoing also auditing per external auditor to achieve higher maturity levels,
#77, https://eclipse-score.github.io/process_description/main/index.html
Upgrade Instructions
not applicable for this release
Contact Information
For any questions or support, please contact the SW Process Development Community (https://github.com/orgs/eclipse-score/discussions/108) or raise an issue/discussion.
Contributors
Assets 2
v1.3.0
Module Name: process_description
Release Tag: v1.3.0
Origin Release Tag: first release
Release Commit Hash: abdfcc8
Release Date: 2025-11-07
Overview
The module process_description provides a process model establishing organization rules for developing open source software in the automotive industry, which can be used in safety and security context.
The process model provides processes, which conform to state-of the art standards
- ASPICE 4.0
- ISO 26262
- ISO 21434
- ISO PAS 8926
This is the first official release, version v1.3.0.
Disclaimer
This release note does not "release for production", as it does not come with a safety argumentation and a performed safety assessment.
The work products compiled in the safety package are created with care according to a process satisfying standards, but the project, being a non-profit and open source organization, can not take over any liability for its content.
New Features
Process model gives compliance with ISO 26262, ISO 21434, ISOPAS 8926 and ASPICE 4.0 (https://eclipse-score.github.io/process_description/main/index.html).
The process model contains
- General concepts e.g. for Building Blocks and their traceability
- Process meta model for proper modeling
- Process areas covering the required standards
- Roles, Work Products, Workflows defining the process areas
- Standard overview and coverage information
- Folder templates for simplifying deployment for users
Improvements
not applicable for this release
Bug Fixes
not applicable for this release
Compatibility
For a detailed list checkout here: https://github.com/eclipse-score/process_description/blob/main/MODULE.bazel
Major dependencies:
- Doc-as-code: v1.4.0
Performed Verification
Initial Safety Audit by external assessor teams for every process area.
Known Issues
Issue 1: Standard requirements and work products are not yet fully mapped to the process model, https://eclipse-score.github.io/process_description//main/standards/index.html
Issue 2: Safety package containing external Audit report not available, due to open improvement proposals/recommendation from external assessor team, #77
Issue 3: Maturity level 1 achieved, but deploying is still ongoing also auditing per external auditor to achieve higher maturity levels,
#77, https://eclipse-score.github.io/process_description/main/index.html
Upgrade Instructions
not applicable for this release
Contact Information
For any questions or support, please contact the SW Process Development Community (https://github.com/orgs/eclipse-score/discussions/108) or raise an issue/discussion.
v1.2.1
What's Changed
- Improvement: Update Documentation Management Process by @PandaeDo in #180
- Process: Remove S-CORE links and tools from Req Mgt by @aschemmel-tech in #182
- fix examples to enforce linking to req by @antonkri in #185
- Process: Req Eng - types tracing updates by @aschemmel-tech in #188
- Process: Add workflows for AoU and Process Req by @aschemmel-tech in #190
- Process: Link all Iso26262 reqs by @aschemmel-tech in #183
- Process: Fix some warings for new doc-as-code by @aschemmel-tech in #192
- Upgrade Doc-as-code and initial setup of process management by @masc2023 in #184
- Add SW-Platform AoU work product by @masc2023 in #197
- correct ISO26262 links in verification process by @pahmann in #199
- clarify from until attributes by @masc2023 in #201
- upgrade doc-as-code to version v1.4.0 by @masc2023 in #202
New Contributors
Full Changelog: v1.2.0...v1.2.1
Contributors
Assets 2
v1.2.0
What's Changed
- Add decision record template to process by @aschemmel-tech in #155
- downgrade aspect-rules-py-version and solve copyright redundance by @Aymen-Soussi-01 in #162
- Remove unused module aspect_rules_py and increase tooling version by @Aymen-Soussi-01 in #163
- Make inspections always a second step by @aschemmel-tech in #165
- update introduction process overview image by @masc2023 in #166
- update life cycle concept by @masc2023 in #157
- Explicit definition of test result and test log handling by @PhilipPartsch in #150
- Update CODEOWNER by @masc2023 in #171
- Improvement: Requrements validity for milestones by @aschemmel-tech in #172
- update change management by @masc2023 in #167
- Process: Release Mgt add getstrt and RASIC by @aschemmel-tech in #174
- Improvement: Add illustration to impact analysis process req by @aschemmel-tech in #148
- Improvement: Add priority to manual process reqs by @aschemmel-tech in #176
- increase version to 1.2 by @masc2023 in #175
- Improvement: Clean config mgt from tools by @aschemmel-tech in #177
New Contributors
- @PhilipPartsch made their first contribution in #150
Full Changelog: v.1.1.2...v1.2.0
Contributors
Assets 2
v1.1.2
What's Changed
- Bugfix: Process requirements for safety analysis by @PandaeDo in #154
- allow tool requirements to link to stakeholder requirements by @AlexanderLanin in #156
- Fixing test properties for python by @MaximilianSoerenPollak in #159
- Update default and custom Bazel modules by @Aymen-Soussi-01 in #160
- Update version of score_process to 1.1.2 to prepare for new release by @Aymen-Soussi-01 in #161
New Contributors
- @Aymen-Soussi-01 made their first contribution in #160
Full Changelog: v1.1.1...v1.1.2
Contributors
Assets 2
v1.1.1
ℹ️ This version contains many changes to the IDs of requirements.
What's Changed
- Bugfix: Remove component test from metamodel by @aschemmel-tech in #147
- Changed ID according to new rules by @MaximilianSoerenPollak in #146
Full Changelog: v1.1.0...v1.1.1
Contributors
Assets 2
v1.1.1-Beta
⚠️ This release uses a Temporary Release of Docs-As-Code. If possible, do not use this.
What's Changed
- Bugfix: Remove component test from metamodel by @aschemmel-tech in #147
- Changed ID according to new rules (in docs as code) by @MaximilianSoerenPollak in #146
Full Changelog: v1.1.0...v1.1.1-Beta
Contributors
Assets 2
v1.1.0
Release Notes
CODEOWNER file activated (only committer of Develop Process Community are able to merge contributions)
Problem Resolution Process updated, Problem Report Template defined, ready-to-use for all other modules
Safety Analysis updated
General concept adapted according latest metamodel changes
Updated to latest Doc-as-code version, v1.0.0, Metamodel aligned
Initial Security Management added
Many small bug fixes, see below What's changed
What's Changed
- bump version to 1.0.1 by @AlexanderLanin in #39
- provide trustable framework template by @masc2023 in #27
- drop score (platform) dependency by @AlexanderLanin in #45
- fix review findings during tool requirements review by @masc2023 in #44
- update requirements formulations as reported by tool team by @masc2023 in #50
- Verification Process Requirements Tooling alignment by @aschemmel-tech in #42
- Add exceptions for tool requirements by @masc2023 in #51
- update overview image by @masc2023 in #43
- Implementation process tooling team feedback fixes by @aschemmel-tech in #56
- arch: bugfix process reqs by @hoe-jo in #46
- Add notice by @MaximilianSoerenPollak in #102
- Audit action correction release mgt by @aschemmel-tech in #100
- Standard links correction: Release Mgt by @aschemmel-tech in #104
- Remove ASIL D from processes by @aschemmel-tech in #105
- Improvement: Process requirements alignment by @aschemmel-tech in #99
- Config Mgt Audit fixes by @aschemmel-tech in #107
- Improvement: correct config mgt start page by @aschemmel-tech in #110
- Audit action correction: release no production by @aschemmel-tech in #108
- Remove HSI work product by @aschemmel-tech in #112
- initial security management by @masc2023 in #92
- prepare new release by @masc2023 in #113
- fix wrong links to work products by @masc2023 in #114
- increase doc-as-code version by @masc2023 in #115
- Add safety mechanism to process by @aschemmel-tech in #116
- Complete Iso26262 wp linking by @aschemmel-tech in #119
- update README by @masc2023 in #120
- Update prm by @masc2023 in #122
- update tool management according audit findings by @masc2023 in #123
- bugfix: add missing requirements description by @masc2023 in #127
- Add CODEOWNER file for process_description by @aschemmel-tech in #128
- Adapt process ownership in workflows by @aschemmel-tech in #129
- Fix issues in process requirements by @aschemmel-tech in #121
- Update LICENSE and NOTICE files by @AlexanderLanin in #131
- update tool management by @masc2023 in #130
- resolve audit findings for problem resolution by @masc2023 in #125
- update 1-bugfix issue template to align with version in score by @masc2023 in #133
- Adapt Safety responsibilities by @aschemmel-tech in #136
- removing s-core and place holder links by @masc2023 in #139
- Improvement: Filter in safety plans at folder template by @PandaeDo in #142
- Upgrade to Docs-As-Code 1.0 by @MaximilianSoerenPollak in #143
- Adding tags to aspice & updating piecharts by @MaximilianSoerenPollak in #137
- updating traceability model by @masc2023 in #141
- process: improve process description safety analysis by @PandaeDo in #54
- prepare new release 1.1.0 by @masc2023 in #132
New Contributors
- @AlexanderLanin made their first contribution in #39
- @hoe-jo made their first contribution in #46
Full Changelog: v1.0.0...v1.1.0
