There is widespread anecdotal evidence that expert programmers make use of visual mental images when they are designing programs. This evidence is used to justify the use of diagrams and visual programming languages during software design. This paper reports the results of two studies. In the first, expert programmers were directly questioned regarding the nature of their mental representations while they were engaged in a design task. This investigative technique was used with the explicit intention of eliciting introspective reports of mental imagery. In the second, users of a visual programming language responded to a questionnaire in which they were asked about cognitive processes. The resulting transcripts displayed a considerable number of common elements. These suggest that software design shares many characteristics of more concrete design disciplines. The reports from participants in the two studies, together with previous research into imagery use, indicate potential...

Visual programming languages aim to broaden the use of diagrams within the software industry, to the extent that they are integrated into the programming language itself. As a result, they provide an ideal opportunity to study the benefits of diagrams as an external representation during problem solving: not only is programming a challenging problem-solving activity, but the effect of diagram usage can be directly assessed by comparing performance while using a visual programming language to performance with a standard textual language. There have been several misconceptions amongst visual language researchers regarding the role of diagrams in software design, but these are being addressed by empirical studies and by new theories of notation design derived from studies of visual programming. Based on this research, the authors are able to recommend several new directions for research into thinking with diagrams. Keywords: diagrams, diagrammatic reasoning, visual programming, ...

Software visualization is nifty stuff; but is it the powerful cognitive tool it is often assumed to be? This chapter attempts to moderate the understandable enthusiasm for software visualization and to raise some of the questions for which the discipline doesn't yet have answers. The chapter is structured as a list of questions with discussion. The questions are not a comprehensive analysis of cognitive challenges in software visualization. Rather, the chapter attempts to provide a list sufficiently provocative to give designers pause, in order: (a) to establish that good software visualization isn't simply a matter of mimicking paper-based tasks or doing what is technically easy---and certainly isn't `solved' yet; but also (b) even simple tools can improve software comprehension, if they're the right ones.

Research into the psychology of programming has been mostly related to textual programs. The application of the theory of programming to visual programs could be further supported by empirical evidence. Graphical readership, a skill that cannot be ignored in visual programming, has been little explored; similarly the case with regard to the effect of paradigm shift on novice programmers. Our research addresses some of these issues. This paper presents empirical evidence drawn from our experiments of first year students interacting with graphical programs. Results of these experiments provide support for the match-mismatch hypothesis, a control flow bias among novice programmers, and the possibility that prior experience with construction toys such as Lego is one of the determinants for graphical readership.