search

KSanjith / pe

0 stars 0 forks source link

Format of command syntax is both confusing and greatly slows down speed of typing #2

Open KSanjith opened 4 days ago

KSanjith commented 4 days ago

Details: The use of /, and ~ symbols for each different parameter makes typing the command out take much longer, and is hard to follow. For example, the example given in the UG is `add income 10000 commission /2023-01-23/ bonus* ~monthly~` Which for most users would be uncomfortable and tedious to type due to the multiple different symbols. Additionally, it is easy to mix up and use the wrong symbol for the parameters, which leads to invalid commands ot incorrectly entered commands, both of which take up the user's time to rectify.

nus-se-bot commented 1 day ago

Team's Response

Dear tester,

The team has discussed and decided to categorize this bug as not in scope. The following are the justifications:

  1. The characters are keyboard accessible normal special characters which should be of no issues to most fast typist to access. We feel that there could possibly be other implementation alternative but the increase in efficiency for these users should be marginal.

  2. Our program guides the user on the correct format every time there is an invalid input for the command.

image.png

  1. As per most user to new programs, they should face similar issues of forgetting the format of program commands, this included. We do not feel that this is an issue unique to our program. Thus we could possibly change the implementation but this is of a low priority and is postponed to after v2.1.

    Items for the Tester to Verify

    :question: Issue response

Team chose [response.NotInScope]

Reason for disagreement: Dear Dev Team, I disagree with your assessment that this issue should be labelled as NotInScope.

Firstly, based on the course website (see Screenshot 1),

it is expected that the input formats will be optimized to get things done fast

for this project. As such, there is an expectation that for the current version v2.1, the commands such be optimized for fast typing. However, the design decision of your group to include 3 completely different special characters, that are each in vastly different parts of the keyboard, and two of which (* and ~) requires pressing the shift key first, goes against the need to optimize for fast typing. As clearly mentioned in the course website, such a design decision should be considered a FeatureFlaw.

Additionally, I would disagree with your assessment that the

the increase in efficiency for these users should be marginal.

For example, if the syntax for frequency was changed from ~monthly~ to f/monthly, the time taken to type the command would be much faster due to neither f nor / requiring pressing the shift key, and since they are both far more commonly typed characters than ~. The same can be said for the *TAG* command syntax.

As such, I have to disagree that my earlier bug report falls under the NotInScope category. Instead, it should be accepted as a valid issue for the current iteration of the application.

Screenshot 1: image.png