1 / 47

Project Review of “ iLo” the Item Locator System

Project Review of “ iLo” the Item Locator System. Project Review Outline. Project Description System Requirements Navigation Map User Analysis Discussion Visual Design Main Menu Design Screen Prototypes Summary Comments Plans. Project Description. “iLo” –Item Locator Device

dawn-mack
Télécharger la présentation

Project Review of “ iLo” the Item Locator System

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Project Review of “iLo” the Item Locator System

  2. Project Review Outline • Project Description • System Requirements • Navigation Map • User Analysis Discussion • Visual Design • Main Menu Design • Screen Prototypes • Summary Comments • Plans Tuyen Lam (tuyenlam@usc.edu) Tom Myhres (myhres@usc.edu) Pauline Tomison (tomison@usc.edu)

  3. Project Description “iLo” –Item Locator Device • Mobile device – envisioned as PDA-like • Provides new capability of finding items easily, for example, like in a grocery or hardware store • Provides new capability for item lists, for example, wood deck kit, grocery list • Provides new inventory management tool • Assumptions: • Most users frustrated by locating items in unfamiliar stores • Most users have some kind of shopping list • Inventory control could be made easier with this device Tuyen Lam (tuyenlam@usc.edu) Tom Myhres (myhres@usc.edu) Pauline Tomison (tomison@usc.edu)

  4. System Requirements The system shall • accept item ID as input barcodes, voice commands, keyboard • have an item description for each item in the current database • be able to search for an item based on an attribute and display the results. • each item in the database shall have the following attributes: • Item identification code, barcode #, Stock Keeping Unit (SKU) # or other, name, quantity, location, unit price, expiration data • be able to display the current inventory and its current location • be able to locate an item based on its current location • provide a method of removing Items from Item List once located • Using items lists, related items are groups together, e.g. dairy • Item Lists shall be managed in the following ways. • Browse / Display currently available Item Lists • Create a new Item List • Delete an Item List • Save an Item List • Add an item to the Item List • Remove an item from the Item List • Display items on an Item List Note: For a complete listing, please refer to the System Requirements Document [0] Tuyen Lam (tuyenlam@usc.edu) Tom Myhres (myhres@usc.edu) Pauline Tomison (tomison@usc.edu)

  5. Navigation Map (1) Tuyen Lam (tuyenlam@usc.edu) Tom Myhres (myhres@usc.edu) Pauline Tomison (tomison@usc.edu)

  6. Navigation map (2) • Notes: • Login Task • Not required for typical user • Required for: • Typical users to retrieve & save shopping lists • Privileged users to access maintenance task • Display Mode provides different controls for viewing information • ex. envisioned display modes include: inventory list, item detail, maps, etc. • Find Mode allows user to find items by several methods, ex. barcodes, item or brand name, etc. • Help Mode displays simple help information. • List Mode allows: • Adding, changing and deleting lists. • Import lists from a Universal Serial Bus (USB) device like a “thumb drive” or the Internet • Maintenance Mode allows privileged users to: • Modify system information • View system usage information. Tuyen Lam (tuyenlam@usc.edu) Tom Myhres (myhres@usc.edu) Pauline Tomison (tomison@usc.edu)

  7. User Analysis User Characteristics: • Users – everyday people 18+ years • System Developers, Maintainers & Administrators (privileged users) • Managers and stocking clerks (privileged users) • Government agencies – regulatory purposes User Tasks: • Physically locate an item or items • Use keyboard, touch-screen and/or voice recognition system (VRS) to operate device • Search for (find), select and review item information • Login/logout • Maintain lists – add / upload, change and delete lists User Workload: • Use device while actively locating item(s), managing time, and managing immediate surroundings (kids, aisles, etc) • Ease of use and speed are central to the system • Subjective satisfaction is of modest importance; frequent use will facilitate retention • Operator fatigue, stress and burnout are considered for users, especially privileged users User Environmental Considerations: • Indoors – system will be used in doors in a variety of stores, e.g. grocery store, home improvement • Personal Digital Assistant (PDA) style system – for easy of use, scrolling, size • Working alone – one user at a time will be able to login and use the system • Scrolling – Will be able to scroll through the list/inventory for specific items • Color – use color when appropriate. If color is used, provide other visual cues for color-blind users Tuyen Lam (tuyenlam@usc.edu) Tom Myhres (myhres@usc.edu) Pauline Tomison (tomison@usc.edu)

  8. Dialog Styles (1) Menus: • The device will employ menus for typical (novice) user as it the most frequently matched dialog style. Menus require little or no training, are self explanatory, make both semantics and syntax explicit, does not require the user to remember commands, requires fewer key strokes – less user error and it facilitates easier error handling, and enhancements are visible as soon as the updates are uploaded. For privileged users a command interface will be available. Privileged users are listed in paragraph 1.a above. Fill-in Forms: • Fill-in forms are used sparingly in our project, primarily for login and searching for items. Reasons for this include additional reading and typing skills. Fill-in forms are self-explanatory and reduce the need for manuals. Fill-in forms require little or no training, and make both semantics and syntax explicit, are efficient in their use of screen – real estate and can accommodate parameters with many values. Direct Manipulation; • The system will employ some direct manipulation. It is intuitive, WYSIWYG – allows our users to focus on task semantics, rather than on the system semantics and syntax. It is flexible and allows for easily reversible actions, and provides context and instant visual feedback. In addition, direct manipulation exploits human use of visual and spatial cues, and requires low typing skills and visual feedback means less opportunity for user errors, which makes it ideal for our system. It replaces typing with pointing/selecting, and provides the user immediate visibility of the results of an action. Direct manipulation allows control/display compatibility, less syntax reduces errors, and direct manipulation facilitates faster learning and higher retention. It encourages the user to explore other functionality of the system. Command Language: • System will provide command language only to privileged users (previously identified). Command language requires a positive attitude towards the system. Privileged users are much more likely to have this than typical users. Privileged users will gain thorough knowledge of the system through training and use. Function Keys: • The system will utilize soft function keys (labels onscreen). Physical function keys will be considered for very frequent actions. Function keys are self-explanatory, easy to use and flexible; require little human memory, little or no onscreen real estate needed, and they limit the typing the user has to do. The soft functions keys may change depending on the mode. Question and Answer User Interface (Q &A UI) • Question and Answer interface will be employed in the voice mode. User can identify and item or pose a single question to the system and the system will respond. The response will go to the screen and optionally by voice since device users are typically in a public environment and may not want to call too much attention to themselves. The Q & A interface is easy to use and is applicable for our system since typically low-motivated and less experienced users will use the system. In addition, Q & A requires little training and it provides history mechanism or other techniques for flexibility. Natural language • Natural language will sparingly or possibly not at all in our system. See voice responses in Q&A above. Tuyen Lam (tuyenlam@usc.edu) Tom Myhres (myhres@usc.edu) Pauline Tomison (tomison@usc.edu)

  9. Dialog Styles (2) Tuyen Lam (tuyenlam@usc.edu) Tom Myhres (myhres@usc.edu) Pauline Tomison (tomison@usc.edu)

  10. Dialog Styles (3) Tuyen Lam (tuyenlam@usc.edu) Tom Myhres (myhres@usc.edu) Pauline Tomison (tomison@usc.edu)

  11. Tasks Analysis Tuyen Lam (tuyenlam@usc.edu) Tom Myhres (myhres@usc.edu) Pauline Tomison (tomison@usc.edu)

  12. Tasks Analysis (2) Select A Task From the Main Menu The user can select tasks from the following main menu/tasks items. • Login • Display Control • Find (Selecting find) • Help • List Maintenance • System Maintenance (for privileged users only) FindThe user can find items in a variety of ways by selecting from the following options. • Barcode entry - user scans in barcode using a barcode reader. • After the users scans the bar code the item’s information is displayed • For a visual description see the Prototype screen shoot • Keyboard entry – user manually enters a search key via a “QWERTY” keyboard ; soft-keys or “Graffiti”™ • Item Lists – user selects from the available Item Lists; items on the Item List are displayed to the user. • Voice recognition system (VRS) - user manually speaks the search key to the system. A list of possible matches or a response message is displayed to the user. • Use the Main menu Icon to return to the Main Menu Tuyen Lam (tuyenlam@usc.edu) Tom Myhres (myhres@usc.edu) Pauline Tomison (tomison@usc.edu)

  13. Tasks Analysis (3) Bar code Scan Bar code Select Bar code Keyboard Use Fill in form to enter item information Item info displayed Item List Find Item Information is displayed Pick an item From the list Return to Main Menu Voice Clearly Speak Name of item Tuyen Lam (tuyenlam@usc.edu) Tom Myhres (myhres@usc.edu) Pauline Tomison (tomison@usc.edu)

  14. I/O Devices I/O Device Considerations: • Web – used to upload a list of items using e-mail, which then can be downloaded to the device in the store (requires login). • Easy interface, most users are familiar with e-mail, uploading and downloading information from the web • USB port – lists of items can be uploaded through a USB port. • Voice recognition – for users that have disabilities. • Pen – to select items from the menu • This is a device similar to a PDA. Using a Pen makes it easy to interface with the device. Tuyen Lam (tuyenlam@usc.edu) Tom Myhres (myhres@usc.edu) Pauline Tomison (tomison@usc.edu)

  15. Visual Design - Style Guides (1) • No externally imposed standards, rules or models • Ex. Department of Defense (DoD) Standards • Dialog styles • Preferred: menus, function keys, fill-in forms & direct manipulation (ex. tab format) • Not preferred: command & natural language • Navigation • Current level in upper-left screen • Main menu icon in upper-right screen • Each level has a color similar to icon on main menu • Icons / symbols • Text subtitle identifies function • Familiar & international symbols used when possible, ex: • ? for help; + and – (plus and minus) signs • Wrench for “maintenance task” • Unique (by task) colors to avoid confusion • Icon selection box • Visual cue for thumb-wheel operation Tuyen Lam (tuyenlam@usc.edu) Tom Myhres (myhres@usc.edu) Pauline Tomison (tomison@usc.edu)

  16. Visual Design – Style Guides (2) • Colors • White screen background • Paper shopping list metaphor • Doesn’t overload user with color • Clean & professional look • Common conventions • Red for error or strong warning • Yellow for caution • Contrasting colors for readable text & icon recognition • Text • Font style either Verdana, Arial or Courier (very common fonts) • Product name always in same style: • iLo (lower-upper-lower Italics) – suggests “forward motion” • Encourages proper pronunciation • Terminology • Use consistently, ex. find not search; help not info; lists not shopping cart Tuyen Lam (tuyenlam@usc.edu) Tom Myhres (myhres@usc.edu) Pauline Tomison (tomison@usc.edu)

  17. Visual Design – Icons • Product logo / icon • iLo is short for item locator • Magnifying glass symbolizes find • “Find iLo & find what you need” ™ • Main menu icons • Main menu - house • Login - person profile • Display - 2 terminals with different displays • Find - magnifying glass (reinforces logo) • ? - help (common MS Windows icon) • List - paper list metaphor • Wrench - widely used for maintenance tasks Tuyen Lam (tuyenlam@usc.edu) Tom Myhres (myhres@usc.edu) Pauline Tomison (tomison@usc.edu)

  18. Display Find Help Maintenance List Main Menu Design • iLo - Basic concepts • Mobile device • PDA type (Personal Digital Assistant ) • Main Menu • Only one part of overall user-system interface (USI) Login Tuyen Lam (tuyenlam@usc.edu) Tom Myhres (myhres@usc.edu) Pauline Tomison (tomison@usc.edu) ?

  19. Main Menu Design Tuyen Lam (tuyenlam@usc.edu) Tom Myhres (myhres@usc.edu) Pauline Tomison (tomison@usc.edu) ?

  20. Prototype Screen ShotNavigation Map Tuyen Lam (tuyenlam@usc.edu) Tom Myhres (myhres@usc.edu) Pauline Tomison (tomison@usc.edu)

  21. Main Menu Login Login required for Privileged Users to access the Maintenance menu. Login also enables the Save option for the Item List menu. User ID Password Login to access the Maintenance Menu (for priviledge users only) and enable Save of Item Lists. Tuyen Lam (tuyenlam@usc.edu) Tom Myhres (myhres@usc.edu) Pauline Tomison (tomison@usc.edu)

  22. Prototype Screen ShotNavigation Map Tuyen Lam (tuyenlam@usc.edu) Tom Myhres (myhres@usc.edu) Pauline Tomison (tomison@usc.edu)

  23. ? Prototype Screen ShotDisplay Main Menu Display Map Mode Inventory Item Item List List of all the items in the database Tuyen Lam (tuyenlam@usc.edu) Tom Myhres (myhres@usc.edu) Pauline Tomison (tomison@usc.edu)

  24. ? Prototype Screen ShotDisplay (2) Main Menu Display User selects an item from the dropdown menu to see the item details Map Mode Inventory Item Item List Items Picture of item goes here Tuyen Lam (tuyenlam@usc.edu) Tom Myhres (myhres@usc.edu) Pauline Tomison (tomison@usc.edu)

  25. ? Prototype Screen ShotDisplay (3) Main Menu Display Map Mode Inventory Item Item List User selects an Item List and the items on that list will be selectable from the Items menu Item List Items Picture of item goes here Tuyen Lam (tuyenlam@usc.edu) Tom Myhres (myhres@usc.edu) Pauline Tomison (tomison@usc.edu)

  26. ? Prototype Screen ShotDisplay (4) Main Menu Display Map Mode Inventory Item Item List Select an item to locate Item location You are here User selects the item to locate. Item location will appear on the map Tuyen Lam (tuyenlam@usc.edu) Tom Myhres (myhres@usc.edu) Pauline Tomison (tomison@usc.edu)

  27. ? Prototype Screen ShotDisplay (5) Main Menu Display Map Mode Inventory Item Item List User selects from 2 output modes Textual Output Audio Output Tuyen Lam (tuyenlam@usc.edu) Tom Myhres (myhres@usc.edu) Pauline Tomison (tomison@usc.edu)

  28. Prototype Screen ShotNavigation Map Tuyen Lam (tuyenlam@usc.edu) Tom Myhres (myhres@usc.edu) Pauline Tomison (tomison@usc.edu)

  29. Prototype Screen ShotFind Main Menu Find Barcode Keyboard Item List Voice User scans in the barcode and it appears on this line. User selects OK to confirm or rescan. Picture of item goes here Tuyen Lam (tuyenlam@usc.edu) Tom Myhres (myhres@usc.edu) Pauline Tomison (tomison@usc.edu)

  30. Prototype Screen ShotFind (2) Main Menu Find Barcode Keyboard Item List Voice User can search on any of the fields available. Only fields that were modified by the user will be used in the search criteria. Tuyen Lam (tuyenlam@usc.edu) Tom Myhres (myhres@usc.edu) Pauline Tomison (tomison@usc.edu)

  31. Prototype Screen ShotFind (3) Main Menu Find Barcode Keyboard Item List Voice Item List List of current items in the selected Item List. Check marks can be used to flag an item has been found. Tuyen Lam (tuyenlam@usc.edu) Tom Myhres (myhres@usc.edu) Pauline Tomison (tomison@usc.edu)

  32. Prototype Screen ShotFind (4) Main Menu Find User speaks the item’s name to find the details of that item Barcode Keyboard Item List Voice Please clearly speak the name of the item to locate. Picture of item goes here Tuyen Lam (tuyenlam@usc.edu) Tom Myhres (myhres@usc.edu) Pauline Tomison (tomison@usc.edu)

  33. Prototype Screen ShotNavigation Map Tuyen Lam (tuyenlam@usc.edu) Tom Myhres (myhres@usc.edu) Pauline Tomison (tomison@usc.edu)

  34. Prototype Screen ShotHelp Main Menu Help User selects from the help topics and the text will appear below Tuyen Lam (tuyenlam@usc.edu) Tom Myhres (myhres@usc.edu) Pauline Tomison (tomison@usc.edu) ?

  35. Prototype Screen ShotNavigation Map Tuyen Lam (tuyenlam@usc.edu) Tom Myhres (myhres@usc.edu) Pauline Tomison (tomison@usc.edu)

  36. Prototype Screen ShotList Main Menu List Del Import Save User is able to add a new Item List and/or add new items to the Item List Add Item List Items Tuyen Lam (tuyenlam@usc.edu) Tom Myhres (myhres@usc.edu) Pauline Tomison (tomison@usc.edu)

  37. Prototype Screen ShotList (2) Main Menu List Del Import Save Add User is able to delete the selected Item List, clear the list, or remove items from the Item List Item List Tuyen Lam (tuyenlam@usc.edu) Tom Myhres (myhres@usc.edu) Pauline Tomison (tomison@usc.edu)

  38. Prototype Screen ShotList (3) Main Menu List User selects from the available places to upload the list of items from a file on the iLo device, from a removable device (ex. USB drive), or from iLo Online. Del Import Save Add Will prompt user to login if not already logged in. RemovableDevice iLoOnline iLo Tuyen Lam (tuyenlam@usc.edu) Tom Myhres (myhres@usc.edu) Pauline Tomison (tomison@usc.edu)

  39. Prototype Screen ShotList (4) Main Menu List Only available to users that are logged in. Will prompt for login if user tries to save and is not logged in. Del Import Save Add User can select where to save the modified Item List. RemovableDevice iLoOnline iLo Tuyen Lam (tuyenlam@usc.edu) Tom Myhres (myhres@usc.edu) Pauline Tomison (tomison@usc.edu)

  40. Prototype Screen ShotNavigation Map Tuyen Lam (tuyenlam@usc.edu) Tom Myhres (myhres@usc.edu) Pauline Tomison (tomison@usc.edu)

  41. Prototype Screen ShotMaintenance Main Menu Maintenance For Privileged Users only. Login required. Reprogram Settings Update Statistics The version # and the version date of the currently loaded iLo software is listed. A Privileged User can update to the latest iLo release via wireless connection to the iLo server. Version # Version date Update latest iLo program files Tuyen Lam (tuyenlam@usc.edu) Tom Myhres (myhres@usc.edu) Pauline Tomison (tomison@usc.edu)

  42. Prototype Screen ShotMaintenance (2) Main Menu Maintenance Reprogram Settings Update Statistics User selectable settings. Tuyen Lam (tuyenlam@usc.edu) Tom Myhres (myhres@usc.edu) Pauline Tomison (tomison@usc.edu)

  43. Prototype Screen ShotMaintenance (3) Main Menu Maintenance Reprogram Settings Update Statistics Updates the local database with new items and item information Download latest database files Allows the user to update fields in an item details. Also updates the database on the iLo server. Tuyen Lam (tuyenlam@usc.edu) Tom Myhres (myhres@usc.edu) Pauline Tomison (tomison@usc.edu)

  44. Prototype Screen ShotMaintenance (4) Main Menu Maintenance Reprogram Settings Update Statistics User selects from the available charts Chart of current statistics Tuyen Lam (tuyenlam@usc.edu) Tom Myhres (myhres@usc.edu) Pauline Tomison (tomison@usc.edu)

  45. Summary Comments • Comments / Issues / Complaints • None • Assumptions • Focus group needed prior to serious product development • Web-based prototypes would provide cheap, valuable feedback • Device can be produced cheaply • Lessons learned • Teamwork • Good inputs come from different experiences & views • It takes time to coordinate efforts • Baselines • Develop & use document templates • Use file version numbers for coordinating work • Have one person assemble & give consistent look & feel Tuyen Lam (tuyenlam@usc.edu) Tom Myhres (myhres@usc.edu) Pauline Tomison (tomison@usc.edu)

  46. Plans • Tools • Web-based prototype • Develop static prototype to show navigability • If time allows, add dynamic content: • Fill-in forms, tab-style menus, maps, etc. • Partially-populated inventory DB Tuyen Lam (tuyenlam@usc.edu) Tom Myhres (myhres@usc.edu) Pauline Tomison (tomison@usc.edu)

  47. References [0] Project Team Website: http://www-scf.usc.edu/~myhres/cs588 [1] The icon crisis's: Tiny pictures cause confusion [2] The Non-Designer’s Web Book [3] CSCI 588 Module 2 pg 101-107 [4] The Non-Designers Web Book [5] Techniques & Tools for Using Color in Computer Interface Design [6] Web Usability by Shneiderman [7] Recommended Main Menu Design [8] Top-10 Mistakes by Jacob Nielsen Tuyen Lam (tuyenlam@usc.edu) Tom Myhres (myhres@usc.edu) Pauline Tomison (tomison@usc.edu)

More Related