1. CS5540 HCI Assignment 4 Designing a Special Needs Nathan Black Taeho Kim 8 Dec 2004

2. User Group  We chose our user group to be mechanics in a workshop.  Often mechanics only have one computer to work on and display information to the customer.  Often using keyboard, or mouse is difficult due to the work environment.

3. Goal  Hide sensitive information from the customers.  Present information to customer in easy to read manner.  Allow keyboard only use

4. Overview  Babo Work Order allows entering of a work order by the mechanic and editing data. Properties of the work order are along the top.  A Note Item View is along the bottom left. It displays items in the work order, such as parts, labor done, and other notes.  Notes can be added, edited, and deleted via the buttons along the right  All the data elements use an appropriate UI control that constrict the range of the data to appropriate values, providing correct mapping.

5. Work Order View  Customer and Car info at top  Mapping like dates use a Date Picker

6. Item List  Uses Tree List View to give an ordering to items  Add, Edit, Delete – and only highlight when appropriate

7. Note Edit/Add  Modal dialog (forcing function, forces user to complete or cancel the action)  Options for the appropriate type of note enable and disable accordingly

8. Customer View  Hides costs of parts (dealer cost), and notes marked as private  Presents information in a invoice format

9. Peer Reviews  At the time our project was reviewed, we had text box in most every place for input, and had few buttons disabling correctly when their function was not valid in that state  They suggested more appropriate mapping and to have a more descriptions on the customer view, as the customer is the least familiar with the software

10. Modifications  We changed our buttons and other controls to correctly disable and enable according to the state and data entered  We added more descriptions on the customer view dialog  We hide the note tree view on the main window when the customer view is up as to prevent the customer from peaking at data they should not see

11. Re-Evaluation  Changes made helped the user a lot. What options are possible where are evident. Forcing functions and mapping are thorough and consistent.  Some pictures and icons could be added to the interface  Peer Review done by Kyung Seog Oh and Gib Reimschussel

12. Summary  Mechanics can now have an easy way to display information to customers  Customers see a invoice like summary of their work order  Mechanics can use the keyboard only if they wish (ie hands are too greasy)  Data is constrained by user interface elements, and very intuitive