Process Requirements -> Tool - Area "Implementation"

[aschemmel-tech]

Discussion on June-30
Alexander Lanin
Maximilian Sören Pollak
Alexander Schemmel

Q: Unit is not a C++ Class. The reasoning is great, but the mapping to C++ classes doesn't make sense. I can have 10 units with 0 classes, or 1 unit and 20 classes.
A: There really is not such a statement in the process description, leave as is.

Q: Unit test isolation is misunderstood? unit tests do not test units in isolation. That would imply mocking and is an anti pattern. Instead unit tests run isolated from other unit tests = they can run in parallel. Testing units in isolation is an anti pattern.
A: Action Process Community: describe/clarify in UT concept that testing without mocking is desirable (and allowed even when integrating external libraries).

• For the last two see https://docs.google.com/presentation/d/1_jMe9v_qOjrHA_h1dWa-r80w2RkNVCIUkjVlDFowFmw/edit?usp=sharing

Q: Formal UML has been dead for 20 years? We typically use UML-like diagrams, but not formal UML.
A: Action Process Community: we need to add a guideline which UML elements (arrows fulll/half, ...) we use and what those mean.

Q: nit-picking: Static View refers to class diagrams. Modern C++ is moving away from classes. How about a "unit diagram" instead?
A: Cannot be decided by processe community - in the end we will need a C++ and a Rust community to decide on these kind of topics.

Q: security, safety for each unit? isn't it always the same for one component?
status for each unit... what is that? how to fill?

A: Action Process Community: security, safety and status will be deleted for Units

Q: "From here onwards the needs are defined in the source code and will be automatically generated and linked via doxygen." --> unit descriptions shall be generated into docs-as-code? That's tremendous overhead. Do we really really need this? Do we need them as needs, or can we link to generate doxygen documentation?
A: Action Tooling Community: alternatives shall be evaluated (one alterantive would be that a source_code_linker link would be used from unit definition in DD document to the source code comment describing the unit.

postpned to July-02:
Q: IMPL_01_02: SOLID is a pattern for novice developers. One of many patterns. Are you sure this belongs into the checklist? Oh and the given "guidance" does not match what SOLID is about!
A: Agreed in process community to delete IMPL_01_02

Q: IMPL_01_05: "Check the automated dependency analysis." -> what automated dependency analysis? First time I'm hearing about it :D
A: dependency tree tooling: added preocess requirement

Q: no explanation just how many diagrams are needed. Typically a cryptic "sufficient diagrams" is mentioned in processes.
A: Do not agree. In implementation concept are clearly mentioned what diagrams are expected. Same for architecture_guidance where it is described when dynamic views are not needed "Do not use dynamic views, ..." - Will improve https://eclipse-score.github.io/process_description/main/process_areas/implementation/implementation_concept.html#static-view and also dyn-view similar with architecture.

Q: req: gd_req__static_diagram, gd_req__dynamic_diagram please remove PlantUML. It's not suitable for complex diagrams. We'll need to use Draw.IO in such cases.
A: Removed tool completely for the process requirement.

Q: wp__sw_implementation_inspection: "valid" is unclear. 100% completed? Then nothing will get merged.
A: Goal is to be always releasable, so the concept is to do an inspection with every pull-request and not post-pone it to some later time "just before the release".

See also eclipse-score/process_description#56.

[AlexanderLanin]

Discussion 2025-07-02
@PandaeDo @aschemmel-tech @MaximilianSoerenPollak @AlexanderLanin

• Units do not need any attributes
• Units do not need to be modelled/shown in sphinx
• Detailed Design (= static and dynamic diagrams) need to link to units (= link to source code).
• Potentially we add something like # @uid unit-123 into the source code, so it can be used from docu as if we had a need with that name.
• Kind of an inverse source_code_linker
• Doxygen (C++) is not required.
• Same approach for Rust (and Python).