Diagram missing visibility

[DannyDakota]

Filter class diagram did not include visibility of the fields and methods. Visibility should be shown to allow the developer a better understanding of the underlying implementation.

This is inconsistent with the class diagram in edit feature that showcases the visibility

[nus-pe-bot]

Team's Response

Visibility can be omitted as they are optional.

Items for the Tester to Verify

❓ Issue response

Team chose [response.Rejected]

• I disagree

Reason for disagreement: I disagree with the developer team that this should be rejected. Firstly, as developers, it is important to know the accessibility of each attribute so that they can understand the underlying implementation of the application. In addition and as I have mentioned, there is no standardisation of the class diagrams in the developer as the first diagram, the edit class diagrams shows visibility. If i was a potential reader and I was scrolling through the developer guide, seeing that edit has visibility of the methods and attributes shown, when I refer to other class diagrams I would expect these to be shown as well. In this sense, the developer is hindered as he would then have to refer to the specific code to determine the accessibility of these operations and/or attributes.

---

❓ Issue severity

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

• I disagree

Reason for disagreement: I rate this as medium severity still as whenever the developer wants to get a higher-level view of the underlying implementation. He won't be able to derive much from the class diagram as he would ultimately still have to refer to the code to obtain the accessibility of the methods and/or attributes. This inconveniences the developer as the diagram is essentially not well integrated to aid the developer in understanding the application.

---