Insufficient UML Diagram (2)

[wanjuin]

For MovieList feature, sequence diagram could be added to make it clear about the interactions between classes. For example, how the program list out the movie list.

It would be clearer to explain how are the list listed out with the filter using a sequence diagram.

[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]

Insufficient UML diagrams.

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.

---

Class diagrams could be added for each feature instead of just sequence diagram for add movie feature, remove movie feature and see detail feature. Addition of classdiagram would make it clearer in how classes are connected with one another.

---

_{[original: nus-cs2113-AY2223S2/pe-interim#1390] [original labels: severity.High type.DocumentationBug]}

Their Response to the 'Original' Bug

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

No details provided by team.

Items for the Tester to Verify

:question: 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]

---

## :question: Issue severity Team chose [`severity.VeryLow`] Originally [`severity.High`] - [x] I disagree **Reason for disagreement:** severity.Medium. Understanding that this flaw will not cause major problems to user / developer guide reading the DG, this could be labelled as a medium issue instead. This should not be severity.veryLow, this is because severity.veryLow should only be used for cosmetic problem whereas this issue is not cosmetic related. Hence, this should not be severity.veryLow. 

---