Process Development Community [2025-06-12]

[masc2023]

Agenda:
Check participants and introduce new members
Align on Agenda for today

Plan, Discuss ongoing PRs, Activities
Safety Analysis merged
Recap: eclipse-score/process_description#27
Status Quality Management, eclipse-score/process_description#21, Quality Plan, #1211

Participants:
@PandaeDo
@MaximilianSoerenPollak
Leonardo Rossetti
@pahmann
@markert-r
@kroehnd
@AlexanderLanin
@FScholPer

Meeting Minutes:
Discussed Planning for Tool Management, target would be to have at least for 01.10.2025 the overall tool list, which evaluation result and at least one sample tool qualification executed.

Quality Management Walk Through on next tuesday meeting
Review Trustable Software Framework, may used from Baselib Feature Team, for component json_parser for scoring it,
compare https://github.com/orgs/eclipse-score/discussions/1225

QA session for Safety Analysis

Remaining questions for Requirements, Architecture
https://eclipse-score.github.io/docs-as-code/pr-67/docs-as-code/requirements.html#requirements
https://github.com/eclipse-score/process_description/issues?q=is%3Aissue%20state%3Aopen%20author%3AAlexanderLanin

Will invite for Review Meeting on next tuesday, 4pm, 17.06, @AlexanderLanin , plus process team

[AlexanderLanin]

my personal meeting minutes, not well structured but all the decisions

Note: I'll take these into docs-as-code requirements, so they might contradict process until it is adapted

safety_analysis
• unique id: -> level = feature name & component name
• title
• mitigation? is it a list? a separate type? a link type? -> optional link to feature requirement or aou
• -> new: either mitigation or issue must be set
• mitigation_issue: optional link to github issue. -> optional
• sufficient: mandatory free text -> yes|no
• argument: mandatory free text -> move to content. Mandatory.
• status: invalid, valid
• verifies: link to arch diagram (see questions there)

other:
• gd_req__saf__linkage –> inverse link of linkage_check. Note: check will be reworked:
o Saf only to dynamic
o DFA to dynamic or static
• gd_req__saf__linkage_fulfill -> will be deleted
• needs typically have a content. Sometimes called a description. Does it reflect any of the fields above? -> argument moved to content
• : link to auo -> include into mitigation (on same level)
• gd_req__saf__linkage_safety -> skip

new: Assumption of use -> split into feature & component -> up to tool team