Open nus-pe-bot opened 1 week ago
Hi thanks for the suggestion, we understand that a few people may find the diagram a little messy. However, this is a plant UML limitation and there was no easy fix for this issue. If we were to remove certain details from this diagram, there would be important information lost. There was no easy way to split the information as there are no low levels details, the details are on the same level. Composition relations with name and phone are essential for the Person and Concert classes.
--
Section found: Model Component
Class diagram is quite cluttered and contains some unnecessary low level details (e.g. composition relations with Name, Phone, etc)
Suggestion: Split the class diagram into two or more diagrams, one showing the necessary high level components, the other showing the lower level details.
[original: nus-cs2103-AY2425S1/pe-interim#2167] [original labels: severity.Low type.DocumentationBug]