ISTM 620 CH 11 review

menu interaction: pop-up menu

"dialogue box" -menu is displayed near the current cursor position -may provide list of actions relevant to current cursor position "copy, delete..." -may provide a list of values that can be clicked on to fill up a field

Guidelines for Structuring Data entry Fields: Help

-provide context sensitive help e.x. hit f1 to open a help menu

Guidelines for Structuring Data entry Fields: defaults

-provide default values when appropriate e.x. assume today's date

guidelines for human-computer design: feedback

-provide feedback for every user action (e.g., confirm that a record has been added, rather than simply putting another blank form on the screen).

Guidelines for Structuring Data entry Fields: format

-provide formatting examples e.x. symbols, decimals etc...

guidelines for human-computer design: ease

-should be simple to add information and navigate between screens (e.g., provide means to move forward, backward, and to specific screens, such as first and last).

validation techniques: missing data

-test for existence of data items in all fields of a record (e.g., Is there a quantity field on each line item of a customer order?)

validation techniques: size

-test for too few or too many characters (e.g., Is social security number exactly nine digits?)

validation techniques: class or composition

-test that data is proper type (e.g., all numeric, all alphabetic, all alphanumeric)

validation techniques: pictures/templates

-test to ensure data conforms to a standard format (e.g., Are hyphens in the right places for a student ID number?)

validation techniques: reasonableness

-test to ensure data is reasonable for the situation (e.g., pay rate for a specific type of employee)

validation techniques: range

-test to ensure data is within a proper range of values (e.g., Is a student's grade point average between 0 and 4.0?)

validation techniques: values

-test to make sure values come from a set of standard values (e.g., two-letter state codes)

validation techniques: expected values

-test to see if data is what is expected (e.g., match with existing customer names, payment amount, etc.)

validation techniques: combinations

-test to see if value of combo of two fields makes sense (e.g., Does the quantity sold make sense given the type of product?)

validation techniques: self-checking digits

-test where an extra digit is added to a numeric field

natural language interaction

-typing and voice in English -human-computer interaction in a conventional spoken language -goal is to make this as easy as possible -currently, this is not very effective

command language interaction

-users enter explicit statements to invoke operations in a system -places burden on user to remember complex syntax -new large-scale systems no longer rely on command language interfaces

object-based interaction

-uses icons -icons are graphic symbols that are easy to understand, take up little space and perform a job (cancel, save, edit) once pressed

guidelines for menu design

-wording -organization -length -selection -highlighting WOLSH

IF YOU SEE A QUESTION WITH 2 of the same answer choices

ITS NOT RIGHT

Graphical picture that represents specific functions within a system.

Icon

A method by which users interact with an information system

Interface

A human-computer interaction method whereby inputs to and outputs from a computer-based application are in a conventional spoken language such as English.

Natural language interaction

bad navigation

https://gyazo.com/240ae2140786875f0788aa767bf8e458

bad menu design

https://gyazo.com/6a6aa2918d8618b280cb830a2bf49fd8

good help screen

https://gyazo.com/7852dbf89b239dd3d4c0846488c3a5de -simple -organized with proper line breaks -provides examples of proper use

good menu design

https://gyazo.com/a6b7fad689017d0f9a8ed7263ba5fc46 -consistent organization -meaningful title -length does not go past 1 screen -selection choices should match skill and competency of users -how to select and consequences should be clear -highlighting should only be used to show selected item

good form navigation

https://gyazo.com/aeabb919c05ab679d43576cbe5d9ca5d -flexibility and cosistency.. move left right top to bottom -move freely to any field -dont save data unless explicitly say to

bad help screen

https://gyazo.com/d3b2c4c7d430912aa94c20f9195153d0

Guidelines for Structuring Data entry Fields: captioning

each field should have a proper caption e.x. radio button, line caption

Guidelines for Menu Design: wording

-meaningful titles, clear command verbs, mixed upper/lower case

Guidelines for Menu Design: highlighting

-minimal and used to convey the selected option

A menu-positioning method that places the access point of the menu near the top line of the display; when accessed, menus open by dropping down onto the display

Drop-down menu

Guidelines for Structuring Data entry Fields: entry

-never require entering of information that can be computed e.x. quantity sold * units instead of making them enter total

Guidelines for Menu Design: length

-not exceed length of the screen -add submenus to breakup long menus

Guidelines for Structuring Data entry Fields: justify

-numbers = right justified -text = left justified

menu interaction: drop down menu

-on a menu bar and when clicked on it provides options immediately below it e.x. file menu at the top of the Microsoft applications and web browsers

menu interaction

-how designers have accomplished the goal of ease of use -list of options where a user clicks and a specific command is invoked -most widely used form of interaction now bc of how easy they are to use -can vary in complexity and hierarchy

data error: truncating

-losing characters

data error: appending

-adding additional characters

guidelines for human-computer design: error handling

-all errors should be detected and reported with suggestions on how to proceed (e.g., suggest why such errors occur and what user can do to correct the error). -accept synonyms... t, true, T

guidelines for human-computer design: shortcuts and sequence

-allow advanced users to take shortcuts with special keys -make sure order makes sense (e.g. first name entered first then last name) (e.g., CTRL-C to copy highlighted text)

form interaction

-allows users to fill in blanks -good for web surfing (google advanced search) and the input and presentation of data (data retrieval) -ALSO good for ENTERING DATA into a system.. type data into the form and it maps it to correct place in the database

Guidelines for Structuring Data entry Fields: replacement

-automatically fill in value once users enter a specific amount of characters

Guidelines for Menu Design: selection

-consistent and reflect the knowledge of the user -how to select and consequences should be clear

Guidelines for Menu Design: organization

-consistent organizing principle

guidelines for human-computer design: reversal

-dialogues should allow the user to reverse actions and data should not be deleted without confirmation -(e.g., undo a deletion) -(e.g., display all the data for a record the user has indicated is to be deleted)

guidelines for human-computer design: consistency

-dialogues should be consistent in action and terminology (e.g., the same labels should be used for the same operations on all screens, and the location of the same information should be the same on all displays).

guidelines for human-computer design: closure

-dialogues should be logically grouped and have a beginning middle and end (e.g., the last in the sequence of screens should indicate that there are no more screens).

guidelines for human-computer design: control

-dialogues should make the user feel in control of the system (e.g., provide a consistent response time at a pace acceptable to the user).

Guidelines for Structuring Data entry Fields

-entry -defaults -units -replacement -captioning -format -justify -help

Guidelines for Structuring Data entry Fields: units

-make unit type clear e.x. dozens, dollars, lbs

deliverables and outcomes of designing interfaces and dialogues

1. narrative overview 2. sample design 3. testing and usability assessment

3 feedback methods

1. prompting cues: "ready for input _____" 2. status information 3. error and warning messages

A human-computer interaction method whereby users enter explicit statements into a system to invoke operations.

Command language interaction

The technique of placing "tabs" or sequenced links on a web page that show a user where he or she is within a site and where he or she has been.

Cookie crumbs

The sequence of interaction between a user and a system.

Dialogue

A formal method for designing and representing human-computer dialogues using box and line diagrams.

Dialogue diagramming

A highly intuitive human-computer interaction method whereby data fields are formatted in a manner similar to paperbased forms.

Form interaction

A human-computer interaction method in which a list of system options is provided and a specific command is invoked by user selection of a menu option.

Menu interaction

A human-computer interaction method in which symbols are used to represent commands or functions.

Object-based interaction

A menu-positioning method that places a menu near the current cursor position.

Pop-up menu

data error: transcripting

entering invalid data into a field

data error: transposing

reversing the sequence of one or more characters in a field