Start
Etap praktyczny czerwiec 2007 z komentarzem, Czerwiec 2007
Etap 1, Szkoła, Liceum, Chemia, Olimpiada chemiczna, 53. Olimpiada
Etap 0, Szkoła, Liceum, Chemia, Olimpiada chemiczna, 51. Olimpiada
Evans , Gabrielle Evans
Eternity of Sound and the Science of Mantras by Pt Shriram Sharma Acharya tr by Dr Rajani Joshi (2003), Magia orientalna
Europejskie zgrupowanie interesów gospodarczych. Komentarz Adamus Rafał PEŁNA WERSJA, Nauka
etr2 mikrokontroler1, PW Transport, II rok, Elektrotechnika 3 lab, opracowania
Evanovich Janet - Namiętności 16 - Znów do sypialni, Romanse i romanse
Erich von Daniken - Wspomnienia z przyszlosci, ۊ۟ۊ E - B O O K, Erich Von Daniken
Estymacja parametrów na poziomie małych obszarów stosowana w reprezentacyjnych badaniach rolniczych Bartosińska Dorota ebook, Inne
  • zanotowane.pl
  • doc.pisz.pl
  • pdf.pisz.pl
  • nea111.xlx.pl

  • Etap 3 9, teoria BHP

    [ Pobierz całość w formacie PDF ]
    Heuristic Evalualtion - A System Checklist
    1. Visibility of System Status
    The system should always keep user informed about what is going on, through appropriate feedback within reasonable time.
    #
    Review Checklist
    Yes No N/A
    Comments
    1.1
    Does every display begin with a title or header that describes screen contents?
    O O O
    1.2
    Is there a consistent icon design scheme and stylistic treatment across the system?
    O O O
    1.3
    Is a single, selected icon clearly visible when surrounded by unselected icons?
    O O O
    1.4
    Do menu instructions, prompts, and error messages appear in the same place(s) on each menu?
    O O O
    1.5
    In multipage data entry screens, is each page labeled to show its relation to others?
    O O O
    1.6
    If overtype and insert mode are both available, is there a visible indication of which one the user is
    in?
    O O O
    1.7
    If pop-up windows are used to display error messages, do they allow the user to see the field in
    error?
    O O O
    1.8
    Is there some form of system feedback for every operator action?
    O O O
    1.9
    After the user completes an action (or group of actions), does the feedback indicate that the next
    group of actions can be started?
    O O O
    1.10 Is there visual feedback in menus or dialog boxes about which choices are selectable?
    O O O
    1.11 Is there visual feedback in menus or dialog boxes about which choice the cursor is on now?
    O O O
    1.12 If multiple options can be selected in a menu or dialog box, is there visual feedback about which
    options are already selected?
    O O O
    1.13
    Is there visual feedback when objects are selected or moved?
    O O O
    1.14
    Is the current status of an icon clearly indicated?
    O O O
    Page 1
    © Usability Analysis & Design, Xerox Corporation, 1995
    #
    Review Checklist
    Yes No N/A
    Comments
    1.15
    Is there feedback when function keys are pressed?
    O O O
    1.16 If there are observable delays (greater than fifteen seconds) in the system’s response time, is the
    user kept informed of the system's progress?
    O O O
    1.17
    Are response times appropriate to the task?
    O O O
    1.18
    Typing, cursor motion, mouse selection: 50-1 50 milliseconds
    O O O
    1.19
    Simple, frequent tasks: less than 1 second
    O O O
    1.20
    Common tasks: 2-4 seconds
    O O O
    1.21
    Complex tasks: 8-12 seconds
    O O O
    1.22
    Are response times appropriate to the user's cognitive processing?
    O O O
    1.23 Continuity of thinking is required and information must be remembered throughout
    several responses: less than two seconds.
    O O O
    1.24 High levels of concentration aren't necessary and remembering information is
    not required: two to fifteen seconds.
    O O O
    1.25
    Is the menu-naming terminology consistent with the user's task domain?
    O O O
    1.26 Does the system provide
    visibility:
    that is, by looking, can the user tell the state of the system and
    the alternatives for action?
    O O O
    1.27
    Do GUI menus make obvious which item has been selected?
    O O O
    1.28
    Do GUI menus make obvious whether deselection is possible?
    O O O
    1.29 If users must navigate between multiple screens, does the system use context labels, menu maps,
    and place markers as navigational aids?
    O O O
    Page 2
    © Usability Analysis & Design, Xerox Corporation, 1995
    2. Match Between System and the Real World
    The system should speak the user’s language, with words, phrases and concepts familiar to the user, rather than system-
    oriented terms. Follow real-world conventions, making information appear in a natural and logical order.
    #
    Review Checklist
    Yes No N/A
    Comments
    2.1
    Are icons concrete and familiar?
    O O O
    2.2
    Are menu choices ordered in the most logical way, given the user, the item names, and the task
    variables?
    O O O
    2.3
    If there is a natural sequence to menu choices, has it been used?
    O O O
    2.4
    Do related and interdependent fields appear on the same screen?
    O O O
    2.5
    If shape is used as a visual cue, does it match cultural conventions?
    O O O
    2.6
    Do the selected colors correspond to common expectations about color codes?
    O O O
    2.7
    When prompts imply a necessary action, are the words in the message consistent with that action?
    O O O
    2.8
    Do keystroke references in prompts match actual key names?
    O O O
    2.9
    On data entry screens, are tasks described in terminology familiar to users?
    O O O
    2.10
    Are field-level prompts provided for data entry screens?
    2.11
    For question and answer interfaces, are questions stated in clear, simple language?
    O O O
    2.12 Do menu choices fit logically into categories that have readily understood meanings?
    O O O
    2.13
    Are menu titles parallel grammatically?
    O O O
    2.14
    Does the command language employ user jargon and avoid computer jargon?
    O O O
    2.15
    Are command names specific rather than general?
    O O O
    2.16
    Does the command language allow both full names and abbreviations?
    O O O
    2.17
    Are input data codes meaningful?
    O O O
    2.18
    Have uncommon letter sequences been avoided whenever possible?
    O O O
    2.19 Does the system automatically enter leading or trailing spaces to align decimal points?
    O O O
    2.20
    Does the system automatically enter a dollar sign and decimal for monetary entries?
    O O O
    Page 3
    © Usability Analysis & Design, Xerox Corporation, 1995
    #
    Review Checklist
    Yes No N/A
    Comments
    2.21
    Does the system automatically enter commas in numeric values greater than 9999?
    O O O
    2.22
    Do GUI menus offer activation: that is, make obvious how to say
    “now do it"?
    O O O
    2.23 Has the system been designed so that keys with similar names do not perform opposite (and
    potentially dangerous) actions?
    O O O
    2.24 Are function keys labeled clearly and distinctively, even if this means breaking consistency rules?
    O O O
    Page 4
    © Usability Analysis & Design, Xerox Corporation, 1995
    3. User Control and Freedom
    Users should be free to select and sequence tasks (when appropriate), rather than having the system do this for them. Users
    often choose system functions by mistake and will need a clearly marked “emergency exit” to leave the unwanted state without
    having to go through an extended dialogue. Users should make their own decisions (with clear information) regarding the
    costs of exiting current work. The system should support undo and redo.
    #
    Review Checklist
    Yes No N/A
    Comments
    3.1
    If setting up windows is a low-frequency task, is it particularly easy to remember?
    O O O
    3.2
    In systems that use overlapping windows, is it easy for users to rearrange windows on the screen?
    O O O
    3.3
    In systems that use overlapping windows, is it easy for users to switch between windows?
    O O O
    3.4
    When a user's task is complete, does the system wait for a signal from the user before processing?
    O O O
    3.5
    Can users type-ahead in a system with many nested menus?
    O O O
    3.6
    Are users prompted to confirm commands that have drastic, destructive consequences?
    O O O
    3.7
    Is there an "undo" function at the level of a single action, a data entry, and a complete group of
    actions?
    O O O
    3.8
    Can users cancel out of operations in progress?
    O O O
    3.9
    Are character edits allowed in commands?
    O O O
    3.10
    Can users reduce data entry time by copying and modifying existing data?
    O O O
    3.11
    Are character edits allowed in data entry fields?
    O O O
    3.12 If menu lists are long (more than seven items), can users select an item either by moving the cursor
    or by typing a mnemonic code?
    O O O
    3.13 If the system uses a pointing device, do users have the option of either clicking on menu items or
    using a keyboard shortcut?
    O O O
    3.14
    Are menus broad (many items on a menu) rather than deep (many menu levels)?
    O O O
    3.15 If the system has multiple menu levels, is there a mechanism that allows users to go back to
    previous menus?
    O O O
    Page 5
    © Usability Analysis & Design, Xerox Corporation, 1995
    [ Pobierz całość w formacie PDF ]
  • zanotowane.pl
  • doc.pisz.pl
  • pdf.pisz.pl
  • jaczytam.opx.pl
  • 
    Wszelkie Prawa Zastrzeżone! Oto smutna prawda: cierpienie uszlachetnia. Design by SZABLONY.maniak.pl.