CS295J/Literature to read for week 5.11: Difference between revisions
< CS295J
No edit summary |
Steven Gomez (talk | contribs) No edit summary |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 3: | Line 3: | ||
* [http://dl.acm.org/citation.cfm?id=1070747 An Insight-Based Methodology for Evaluating Bioinformatics Visualizations], Saraiya, North, and Duca, TVCG 2005 | * [http://dl.acm.org/citation.cfm?id=1070747 An Insight-Based Methodology for Evaluating Bioinformatics Visualizations], Saraiya, North, and Duca, TVCG 2005 | ||
: (Owner: [[User:Steven Gomez|Steven Gomez]]) | : This paper describes an evaluation methodology based on insights gained from exploratory visualization tools. There are several drawbacks related to the difficulty of the method (e.g., coding insights), but an insight-based evaluation or some variation might be a good choice for the brain diagram tool. I wonder if it's possible to use predictive modeling to code insights (e.g., finding "Aha" moments using GSR or other features) to semi-automate some parts of the methodology that make it hard to use. (Owner: [[User:Steven Gomez|Steven Gomez]]) | ||
* [http://vis.cs.brown.edu/~trevor/Papers/Kaptelinin-1994-ATI.pdf Activity Theory: Implications for Human-Computer Interaction], Kaptelinin | * [http://vis.cs.brown.edu/~trevor/Papers/Kaptelinin-1994-ATI.pdf Activity Theory: Implications for Human-Computer Interaction], Kaptelinin | ||
: (Owner: [[User:Hua Guo|Hua]]) | : (Owner: [[User:Hua Guo|Hua]]) | ||
* [http://www.sciencedirect.com/science/article/pii/S1071581996900713 User analysis in HCI: the historical lesson from individual differences research],ANDREW DILLON | |||
: (Owner: [[User:Wenjun Wang|Wenjun]]) | |||
Latest revision as of 15:52, 6 October 2011
- Spanning Seven Orders of Magnitude: A Challenge for Cognitive Modeling, John Anderson, 2002
- (Owner: David)
- An Insight-Based Methodology for Evaluating Bioinformatics Visualizations, Saraiya, North, and Duca, TVCG 2005
- This paper describes an evaluation methodology based on insights gained from exploratory visualization tools. There are several drawbacks related to the difficulty of the method (e.g., coding insights), but an insight-based evaluation or some variation might be a good choice for the brain diagram tool. I wonder if it's possible to use predictive modeling to code insights (e.g., finding "Aha" moments using GSR or other features) to semi-automate some parts of the methodology that make it hard to use. (Owner: Steven Gomez)
- (Owner: Hua)
- (Owner: Wenjun)