Activity Diagram for `copy` command is too complicated

[cx0810]

The activity diagram for copy in the Developer Guide takes up 2 pages. It is very hard for readers to view the diagram.

[nus-se-bot]

Team's Response

I feel that each part of the diagram is necessary and essential to show how the command was implemented, so it is not possible to shorten the diagram. I tried putting the diagram horizontally, but it became too wide for the documentation. I also feel that this makes the implementation much clearer to developers as it provides a visual aid to understanding the workflow of the command.

Items for the Tester to Verify

❓ Issue response

Team chose [response.Rejected]

• I disagree

Reason for disagreement: The activity diagram is very repetitive (e.g. creating predicate and CopyCommand) and complicated. While it shows the exact workflow of the command, there is no need to elaborate on each action in detail in the activity diagram.

---