Input and output considerations (1)
General users should be in control of the dialogue at all times, be able to easily recover from errors, and not be required to input more information than is necessary for successful task performance.
Command reuse if the same sets of commands are used repeatedly during a work session, the system should provide a way of reusing the commands without requiring the user to type them again. [EXAMPLE giving users a command history list from which they can select a previously used command]
Command queuing users should be provided with the capability to key in a series of commands (command queuing or stacking) rather than wait for the system to execute each individual command. [NOTE separators should be provided to separate command strings (see above under separators)]
Error correction if errors occur, re-entry, or editing, should be required preferably for the erroneous portion of the command and associated parameters.
Editing (a) users should be allowed to edit commands prior to execution; (b) if the application has a text editor, the same text editing conventions used in the text editor should be apply to command dialogue editing.
Misspelling if appropriate for the task and system constrains allow, the system should provide for interpretation and acceptance of misspelled commands unless there is ambiguity as to what command was intended.