Multistep commands that are not one liners should not be allowed

[Barbaracwx]

[nus-pe-bot]

Team's Response

What do you mean by multistep commands are not allowed? Like for the team project? If so, could you share the link with me please?

Items for the Tester to Verify

:question: Issue response

Team chose [response.IssueUnclear]

• [x] I disagree

Reason for disagreement: The concept of 'multistep commands' refers to the process of taking multiple sequential actions or inputs to accomplish a task, as opposed to condensing those steps into a single, more comprehensive command. In this context, it pertains to the way users interact with the system to input event-related information.

Currently, the system requires users to input event details—such as event name, start time, and end time—separately in multiple steps. This method significantly slows down the input process and impedes efficient testing procedures. As per the guidelines outlined in our textbook regarding features that impede testing and slow down inputs, such approaches are discouraged.

The proposed solution involves the adoption of a more streamlined and efficient input method. Instead of prompting users with individual questions or steps to enter event details, we suggest implementing a single command format. For instance, a command format such as 'add /n /d /st /et' could be introduced. Here, '/n' represents the name of the event, '/d' represents the date of the event, '/st' denotes the start time of the event, and '/et' signifies the end time of the event.

By embracing this one-liner command approach, users can input all necessary event details at once, significantly expediting the data entry process and facilitating easier testing. This change aligns with best practices outlined in the textbook regarding efficient input methods and helps mitigate delays associated with multistep input processes.

---