User Interface Design

General Interaction
s/n	Criteria to look into for grading	Excellent	Good	Average	Bad
1	Consistent format e.g. menu, display, command input.		*
2	Offer meaningful feedbacks.		*
3	Ask for verification of any non-trivial destructive action (e.g. confirm deletion before execution).		*
4	Permit reversal of most action.			*
5	Reduce amount of information that must be memorized in between action.		*
6	Forgive mistakes (protect against user errors)			*
7	Categorizes activities by function (pull down menu for cohesive placement of related commands and actions)		*
8	Help facilities				*
Summary : The interaction of the system is generally good except that help facilities is minimal due to time constraint of the schedule. Reversal for action like undo action should be added as well. We still need to improve on our coverage on the anticipation of the various type of user errors.
Back to Top

Information display
s/n	Criteria to look into for grading	Excellent	Good	Average	Bad
1	Display relevant information to the current context.		*
2	Use of presentation format e.g. graphs or charts				*
3	Use consistent labels, standard abbreviation, and colors in display.		*
4	Produce meaningful and helpful messages to user			*
5	Separate windows for different information and action.		*
Summary : The display of the system is generally good except that presentation charts like graphs are absent because in the system there isn't much statistics involved but rather there is a report generated for the user to use it to analyze and identify the peak period for the carpark.
Back to Top

Data input
s/n	Criteria to look into for grading	Excellent	Good	Average	Bad
1	Minimize number of user input (reduce amount of typing by user).			*
2	Maintain consistency between information display and data input.		*
3	User can select his preferred type of inputs for particular action. (E.g. search record by name rather than id or contact no but they are still available for selection)		*
4	Deactivate commands that are inappropriate in the current context. (Disable delete action during creation of record)		*
5	Able to recover for error inputs to made corrections.			*
6	User need not specified engineering input. (Do not need to enter .00 for dollars, cm, km or liters etc)			*
Summary : The input to the system is generally average as user has to enter many details e.g. when creating of new member we need to enter all his /her information. Correction to mistake still need refinements. For the engineering input, we had kept these type of input to minimal.
Back to Top

Summary :

The whole system still require refinement in the user error area such that error state can be recovered rather than exiting the system immediately. User input need to be kept to minimal but not compromising to remove relevant details of user. The overall system will look more attractive with more graphics added on so that users can enjoy the tour on the system more interesting and enjoyable.