Hard to define NFR of user ease of understanding

[alvinlim277]

Hard to achieve considering the multitude of commands and also difficult to define.

[soc-se-bot]

Team's Response

It can be assessed as follows: get new users to determine what the command is, based on the command name and the capabilities that our app has. The success of this NFR can be gauged by the accuracy of the user's explanation.

One way that fails this NFR is by implementing the commands as follows:

• cr for create. Is this create or change request?
• dl for delete. Is this delete or download?

This NFR is necessary to ensure that the naming of the command is unambiguous.

This is not necessarily hard to achieve. By ensuring that all commands are self-explanatory, it can fulfil the NFR. Furthermore, we only have a limited number of commands:

• create
• add
• edit
• delete
• filter
• sort
• undo
• redo
• open
• email
• list
• exit
• help
• clear

Even if we add more in the future, it will not be that many such that it is "hard to achieve".

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

• [ ] I disagree

Reason for disagreement: [replace this with your explanation]

---