Cannot Swap Order of Options - User Inconvenience

[Jonoans]

Users seem to be unable to swap the order of options passed to the program:

For example, we can do add /n Random /d 12/06/2019 /s ABC130 /q 52 /p 12.90

but not add /d 12/06/2019 /s ABC130 /q 52 /p 12.90 /n Random - name at end.

This seems inconvenient for the user in that it gives no meaning to the option specifiers /n, /d and so on except for just being something a user MUST type in order for the command to work.

[nus-pe-bot]

Team's Response

Concerns not related to the features at this version, as there is a specified format to be followed. However, as for the idea that it gives no meaning to the order, maybe it might be useful to consider the real-life application of this? In pharmacies/drug-related offices, the inventory staff usually start with looking at name, and the necessary information only comes after. For example, expiry date is quite crucial, so it is right after name. It just helps with convenience the most to add the name, and the corresponding information after.

Understandable concern. Perhaps in future iterations it can be included - but currently, it isn't really a flaw of our feature as the add command works exactly as intended and specified, nor does it significantly impede our actual target users who usually follow a routine when managing the inventory and key in specific orders so as to not get mixed up.

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

• [ ] I disagree

Reason for disagreement: [replace this with your explanation]

---