nus-pe-script
commented
7 months ago Team's Response
According to what the textbook says on activity diagram, there is no requirement of not including low-level details. These low-level details are necessary to show how different parts of the logic package works.
An example in the textbook is as follows:
"100th square reached" is an example of a low-level detail.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
The description of how classes handle the user input in such detail at the start of the diagram seems irrelevant to the activity diagram and could be condensed to something like "Prefix of user input". Maybe these low level details are better suited to a sequence diagram instead.