Team's Response

This is indeed something that we could have included to aid reader comprehension, and we will take note of it. However, the link and unlink commands are only a small component of the features that we have added, not one of the major features. The biggest component of our application is the ability to track events, as well as their schedules. Additionally, the omission does not disrupt functionality; it reduces clarity in the documentation.

Items for the Tester to Verify

:question: Issue severity

Team chose [severity.Low] Originally [severity.Medium]

[x] I disagree

Reason for disagreement: Severity Low should apply only to rare cases. In this case, it is more appopriate for the severity to be Medium as all readers who reads the documentation would be subjected to this documentation bug.

However, as a Developer trying to improve or redesign the application, the lack of documentation makes it hard for the reader to actually understand how this link and unlink is implemented and how it is stored in the storage. Furthermore, there is no additional elaboration for the implementation of this feature anywhere in the DG.

It is also stated that this is the main challenge the group faced but no supporting documentation is provided for future developers.

I would also disagree with the team's argument that this is not a major component given the fact that they have mentioned the feature as one of their value propositions.

Given the substantial lack of information provided in the DG supporting this feature, the severity should be at least Medium.

HanB1n / pe

Incomplete UML class diagram for the storage component #6

Team's Response

Items for the Tester to Verify

:question: Issue severity