Open riccoljy opened 1 week ago
We did not find the UniqueTagList component to be important enough to be included in the UML diagram, as the value to be added is insignificant, and would cause the diagram to be more cluttered. We included it in the first diagram as there was a mention about the usage of tags in our architecture, as seen in the screenshot below.
Team chose [response.Rejected
]
Reason for disagreement: Upon reviewing the group's code, their AddressBook
does not even include a UniqueTagList
. Their project does have a seedu.address.model.person.UniquePersonList
and a seedu.address.model.event.UniqueEventList
, which makes the 2nd image accurate but the 1st inaccurate.
The only instance of UniqueTagList appearing is in the UML diagrams, and not in any actual implementation.
Seems to be inconsistencies for Model UML diagram