Process Development Community [2025-02-06]

[masc2023]

Agenda:
Check participants and introduce new members

Plan, Discuss ongoing PRs, Activities
Additional Working Meeting?
Roadmap/Planning to be defined, Audit to be included
Cross Functional Work Structure
Two step approach for workproducts review/inspection.
Iso 26262 references usage

Participants:
@FScholPer
@PandaeDo
@aschemmel-tech
@markert-r
Sateesh R.
Daniel Kroehnert
@hoe-jo
@PhilipPartsch
@masc2023

Meeting Minutes:
PRs for New Metamodel and updated changes in Score presented
https://github.com/orgs/eclipse-score/projects/7
#278

Input for Roadmap -> Requirements -> Architecture -> Implementation->Test (Milestone proposal E03/2025)
Requirements Process is more or less ready to transfer, where to start Score or Process Description? Blocker for processes publication in process_description repo to be fixed first with #230
Separate Planning Session (will be organized by @markert-r, Participants: Volker, Daniel, Alexander Schemmel, Markus)
Overview, Backlog, Monday 10th Feb, 1-2pm

Scheduling Working Meetings:
Tuesday, Starting from 11th Feb, 9-10am, Invite goes to all participants

ASPICE mapping could be started and incorporate in score, for the ISO standards Alex Schemmel will propose a solution without disclosing Iso26262 numbering/headings.

Two step approach for workproducts review/inspection was discussed, Philip wants to be able to put to a Pull-Request already mature requirements including all development artefacts including verifications. That is also possible with the process, we can describe this as alternative workflow. Also the question was if in the mainline there could be mixed statuses (valid or valid(inspected)) - yes this can be the case, but must be fixed before a "quaified" release.

Ongoing activities
@markert-r will setup a common meeting to discuss Tool Process/Management