Missing Activity diagram for display

[NeoHW]

[nus-pe-script]

Team's Response

The inclusion of an activity diagram is certainly nice to have, but the current content provided in the DG is sufficient in describing the display feature.

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

• [x] I disagree

Reason for disagreement: While textual descriptions may cover the basic functionality, they often lack the depth and clarity provided by visual representations like activity diagrams. Unlike textual descriptions, activity diagrams offer a comprehensive visual overview of the various processes and states involved in the display feature's functionality. This comprehensive view aids in understanding not only the primary flow of actions but also exception handling, parallel processes, and decision points within the system, which is not apparent from the textual descriptions alone. Without the inclusion of an activity diagram, readers may struggle to grasp the full scope of the display feature, potentially leading to misconceptions or incomplete understanding.

Moreover, activity diagrams serve as valuable documentation for future reference, aiding in onboarding new team members and facilitating discussions regarding system behaviour and improvements.

• This is clearly a documentation issue and not a flaw (e.g. missing feature, suboptimal design, known bug). Furthermore, none of the condition are fulfilled for it to be a NotInScope.
• There was no mention that the diagram was intentionally omitted/coming in future or similar to other commands diagrams.

---