nus-pe-bot
commented
3 years ago Team's Response
Thank you for the comments; however, our team is not seeing this as an high severity issue.
The reason being, firstly, the project requirement is to create a CLI-based application.
We understand there are many commands for the user to keep track of; hence that's why it's part of the project requirements as a developer to develop a User Guide to allow users to understand how to use our application and the various types of commands. We are not enforcing user to keep track or memorise every command they can perform.
In response to the part on long commands, there was no constraint on how long or short our commands should be. Since the app is optimised for fast-typer, we believe that having long commands shouldn't pose an issue to fast-typers as well? Not to mention, we have a lot of different commands and having shorter commands may cause even more potential mix up and typos. It was a developer POV to weigh the pros and cons and decide whether should we adopt longer commands or shorter commands operations. Which ultimately, our group came to a decision to adopt a longer command to ensure accuracy; there was no constraint on the length of commands given by the module requirement.
We will take in your comments in our future project reference but this is definitely not a feature flaw at high severity.
Furthermore, this bug was filed during Part II (Evaluating Documents) and we have to reject is as it is not related to documentation quality.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
Great app but personally i feel like there are too many commands for the user to keep track off. The commands are too long to type which took quite a big of time. An example will be the different add commands.