Open T-Wan-Lin opened 1 year ago
Thank you for the suggestion, but we think that it is more useful for developers to have a glance at the UI methods that are used extensively throughout the program. Moreover, UML formatting is followed for the developer to understand the diagram.
Team chose [response.Rejected
]
Reason for disagreement: As per the module website:
In the Ui Class diagram, there are many exception message print methods, you could have selected those that were more representative of the class which aids in your explanation of what the Ui class does. This logic applies to the rest of the messages. Furthermore, developers usually have access to the source code, so it would not be necessary to showcase everything in the DG as they can cross-reference to the source code.
Is a class diagram for Ui necessary? It is rather long and would get outdated quickly (if you were to update it), given the many methods you have. The sequence diagram for Ui is much more meaningful in the DG