soc-se-bot
commented
11 months ago Team's Response
Thank you for your suggestion. However, our team, who are also the developers and maintainers of this application, believes that providing details for the attributes of a patient (similar to how AB3 shows the classes for the patient attributes in their class diagram for the Model) is helpful to the understanding of the component's structure. We had to include the Patient attributes (Name, IcNumber classes etc.) as attributes as opposed to boxes/classes (like how Tag and Record are shown) in the UML class diagram as we felt like this is more readable and takes up less space. Hence, we regret not accepting your suggestion!
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
Unnecessary low level details about the Patient class are included in the class diagram for the model component, which is not really required at the high-level of abstraction followed in the rest of the diagram.