Open Fallman2 opened 9 months ago
Seeing that this diagram was generated with PlantUML, the position of the arrow labels could not be controlled and hence this is a limitation of PlantUML.
The severity has also been adjusted to very low, since this issue pertains to cosmetics, specifically the spacing of arrows or the potential incorporation of additional colours for clearer differentiation.
Team chose [response.Rejected
]
Reason for disagreement: Although PlantUML is limited in the placements of arrow labels and the arrows themselves, it is still possible to control these placements to an extent. Additionally, even though PlantUML has these limitations, that does not mean that the bug should be allowed to continue to exist. Instead, it should be taken into consideration that PlantUML is limited in these aspects and instead, the diagram can be split into multiple diagrams to show a more detailed explanation of the structure to ensure that it is not confusing to potential developers. An alternatives to PlantUML can also be considered if developers want to continue putting all these classes into this class diagram. Since this may not be the main focus compared to the rest of the work done up to v1.4, I feel that this bug can be considered NotInScope. However, given that the diagram is decidedly confusing in its current implementation, I do not believe that this bug should be rejected.
The class diagram of the model in the DG is unclear as multiplicities and role labels are placed on the same side of each arrow. This results in the "all" and "filter" roles being potentially misattributed to other arrows or the multiplicity not being clear as it is too far from the arrow.