No visibility shown in skill class diagram

[DannyDakota]

Visibility not shown. Inconsistent

[nus-se-script]

Team's Response

No details provided by team.

The 'Original' Bug

[The team marked this bug as a duplicate of the following bug]

Diagram missing visibility

Note from the teaching team: This bug was reported during the Part II (Evaluating Documents) stage of the PE. You may reject this bug if it is not related to the quality of documentation.

---

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

---

_{[original: nus-cs2103-AY2122S2/pe-interim#1477] [original labels: severity.Medium type.DocumentationBug]}

Their Response to the 'Original' Bug

[This is the team's response to the above 'original' bug]

Visibility can be omitted as they are optional.

Items for the Tester to Verify

❓ Issue duplicate status

Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)

• I disagree

Reason for disagreement: [replace this with your explanation]

---

❓ 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.VeryLow]

• I disagree

Reason for disagreement: [replace this with your explanation]

---