%0 Book %1 petre98 %A Petre, M. %A Blackwell, A. %A Green, T. %B Software Visualization: Programming as a mult %C Cambridge MA %D 1998 %I MIT Press %K engineering modeling software cognition visualization %P 453--480 %T Cognitive Questions in Software Visualization %U http://www.cl.cam.ac.uk/~afb21/publications/book-chapter.html

@book{petre98, added-at = {2006-03-24T16:34:33.000+0100}, address = {Cambridge MA}, author = {Petre, M. and Blackwell, A. and Green, T.}, biburl = {https://www.bibsonomy.org/bibtex/2d7bb7c05cbcbe77c27707c7faf634d97/neilernst}, citeulike-article-id = {121589}, comment = {- "even simple tools can improve software comprehension, if they're the right ones" - "no simple generating function" I think a tool like ontoviz tries to suggest there is. Ontoviz does not encourage user exploration, merely presents a fairly static graph. - "reading the perceptual qualities of data is a real skill" question of suitability: 1) What sort of visualisation -- depiction, description, presentation, abstraction -- 2 is suitable for which information 3 and which uses 4 by which users? - are things like indented and highlighted code a viz? - KE have worked with text files a long time so perhaps the viz aspect is a harder sell - why do experts use SW viz: 1)externalize images of thought 2) download memory 3) focus for communication 4) tools for thinking 5) harness computer as collaborator in problem solving - why do non-experts use SW viz: 1) be like an expert 2) see how expert reasons 3) force novices into expert-like paradigms 4) visualization of execution 5) other ways of seeing relationships what is an expert in our context - p. 5 lower down never assume what comes from an expert's mind is appropriate for non-experts - p.7 what experts demand from a viz tool: control, scale, speed, truth (accuracy) - p8 what model - do users have preformed ways of working that might help us design visualizations and abstract lower level details? problems interacting (editing) highlevel abstractions - Have to make a large assumption about how people work p9 "descriptions of visualization systems rarely specify any particular task that they are intended to support" - p10 axioms of info representation: 1) finding info is easier when the form sought has a cognitive fit with that presented 2) "if the presentation is designed to highlight some kinds of information, then it is likely to obscure other kinds" - p12 text 1-d, pictures 2-d (what about time in both?) - p13 "rather than rushing to the latest technology... a more economical line of research might be to discover how much can be achieved by the subtle application of two (dimensions)." - p14 role of user's capabilities - at interpretation are two representations (text +...) better than one? (less screen space, no swithcing, no need to determine equivalencies)}, description = {sdasda}, interhash = {5ddebca92da42f68ab5b8a5097ee7c0f}, intrahash = {d7bb7c05cbcbe77c27707c7faf634d97}, keywords = {engineering modeling software cognition visualization}, pages = {453--480}, priority = {0}, publisher = {MIT Press}, series = {Software Visualization: Programming as a mult}, timestamp = {2006-03-24T16:34:33.000+0100}, title = {Cognitive {Q}uestions in {S}oftware {V}isualization}, url = {http://www.cl.cam.ac.uk/~afb21/publications/book-chapter.html}, year = 1998 }