1
|
- Session 9
- INFM 718N
- Web-Enabled Databases
|
2
|
- Finishing up HCI
- Planning for weekly status reports
- Team meetings
- Testing
|
3
|
- Command Language
- Form Fill-in
- Menu Selection
- Direct Manipulation
- Natural Language
|
4
|
|
5
|
|
6
|
|
7
|
|
8
|
|
9
|
- Two attributes determine the position
- Can be dynamically selected from a list
- Numeric position attributes work best
- Other attributes can affect the display
- Displayed as color, size, shape, orientation, …
- Each point can represent a cluster
|
10
|
- IVEE/Spotfire/Filmfinder (Ahlberg & Shneiderman 93)
|
11
|
- http://www.philipglass.com/
|
12
|
- Design for monochrome displays
- Provides assured access for color blind users
- Add muted colors where they help
- Useful for rapid recognition of categories
- Limit to 4 colors per screen (7 per application)
- Pay attention to readability
- “Similar” colors look different on another display
- Different systems may have different defaults
|
13
|
- Don’t make icons too small
- Fitts’ Law: Time =3D f(distance, size)
- Size can be used to illustrate quantity
- Scale size coding by at least 1.5
- No more than 4 font sizes
|
14
|
- Drill down
- Mouseover tool tips, menu expansion
- Illustration
- Change over time, icon behavior (on mouseover)
- Display space reuse
- Visible transitions
- Attention management (once!)
|
15
|
- Informative feedback
- Easy reversal
- User in control
- Anticipatable outcomes
- Explainable results
- Browsable content
- Limited working memory load
- Query context
- Path suspension
- Alternatives for novices and experts
|
16
|
- Interdependence with process
- Co-design with search strategy
- Importance of response time
- System initiative
- Guided process
- Exposing the structure of knowledge
- Support for reasoning
- Meaningful dimensions
- Representation of uncertainty
- Synergy between querying and browsing
- Easily learned
- Familiar metaphors (timelines, ranked lists, maps)
|
17
|
- Progress to date
- Lessons learned
- Things you would like advice/ideas on
|
18
|
- Syntax errors
- Run time exceptions
- Cause system-detected failures at run time
- Logic errors
- Cause unanticipated behavior (detected by you!)
- Design errors
- Fail to meet the need (detected by stakeholders)
|
19
|
- Design walkthrough
- Does the design meet the requirements
- Code walkthrough
- Does the code implement the requirements?
- Functional testing
- Does the code do what you intended?
- Usability testing
- Does it do what the user needs done?
|
20
|
- You can’t test every possibility
- Several approaches
- Object-level vs. system-level
- Black box vs. white box
- Ad-hoc vs. systematic
- Broad vs. deep
- Choose a mix that produces high confidence
|
21
|
- Define one or more scenarios
- Based on the requirements (not your design!)
- Focus only on implemented functions
- Provide enough training to get started
- Usually with a little supervised practice
- Banish pride of authorship
- Best to put programmers behind one-way glass!
- Record what you see
- Notes, audiotape, videotape, key capture
|