Spohrer, J. C., Soloway, E. and Pope, E. (1985), A goal/plan analysis of buggy Pascal programs. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
An Assessment of Visual Representations for the `Flow of.. - Chattratichart, al. (2000) (Correct)
....of one over the others. There are several empirical studies with mixed results on whether flowcharts aid program comprehension and debugging (Shneiderman, et al. 1977; Brooke and Duncan 1980a, 1980b; Gilmore and Smith 1984) Cunniff et al. 1986) compared the number of bugs and the bug types (see Spohrer et al. 1985) made on nine programming problems written in FPL (First Programming Language) by six students to those obtained by the experiments on Pascal programs written by novice programmers at the Yale University. FPL, a graphical programming language developed at Columbia University for novice ....
Spohrer, J. C., Soloway, E. and Pope, E. (1985), A goal/plan analysis of buggy Pascal programs.
Uncovering Effects of Programming Paradigms: Errors in Two.. - Tukiainen (2000) (Correct)
....could also explain B1. The paradigm forces a user to think globally of the solution, i.e. to plan and design the solution before starting the implementation. This causes a lot of mental load for novices and is against the novices preferred strategy to think locally of the solution (e.g. see Spohrer et al. 1985) for a discussion of Pascal novice strategies) This error manifests itself in the tasks where there is a chain of goals, i.e. tasks 1 and 4. The number of concepts that is required to successfully use Basset is quite high. The concepts of structures, the types of the structures, the modification ....
Spohrer, J. C., Soloway, E., & Pope, E. (1985). A Goal/Plan Analysis of Buggy Pascal Programs.
A Pragmatic Survey of Automated Debugging - Ducassé (1993) (1 citation) (Correct)
....checks the program source and or the program behavior against the bug rules. The parts of the program which conform to these rules are suspect. The rules used to detect the errors provide some explanation about the possible error. Many error classifications have been proposed for example in [4, 11, 30, 29, 33, 18] but none of them provide a framework satisfactory enough to guide the design of an (almost) complete set of stereotyped errors. Errors are collected on a pragmatic basis only. Error recognition may be totally helpless to diagnose some errors and thus can only be used as a complementary ....
J.C. Spohrer, E. Soloway, and E. Pope. A goal/plan analysis of buggy Pascal programs. Human-computer Interaction, 1(2):163--207, 1985.
Why HyperTalk Debugging is More Painful than it Ought To Be - Eisenstadt (1993) (4 citations) (Correct)
.... Why are there so many apparent pitfalls There have been numerous psychological studies of programming and debugging (e.g. Brooks, 1980; Gould Drongowski, 1974; Kahney Eisenstadt, 1982; Katz Anderson, 1988; Pennington, 1987; Shneiderman, 1980; Sime, et al. 1973; Soloway Iyengar, 1986; Spohrer et. al, 1985; Vesey, 1989) but much less emphasis has been placed on the phenomenology of debugging. Knuth (1989) focused on the latter point by keeping a detailed record of all the errors that occurred during the ten year development of TeX. Self reports and log books like that of Knuth are valuable sources ....
Spohrer, J. C., Soloway, E., & Pope, E. (1985). A Goal/Plan Analysis of Buggy Pascal Programs. Human-Computer Interaction, 1(2):163-207.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC