On the knowledge required to understand a program
Published 27 November 2002
Richard J. Clayton, Spencer Rugaber, L. Wills
Citations33
Generate an AI Snapshot to get a quick, structured summary of this paper.
Study Snapshot
ObjectiveStudy objective
MethodsResearch methodology
PopulationPopulation studied
Sample sizeSample sizes
OutcomesStudy outcomes here
ResultsStudy results comes here
LimitationsResearch study limitations comes here
A concise AI-generated summary of the paper will appear here once you click Generate AI Snapshot.
TL;DR
A pilot study was conducted wherein a short, but complex, program was examined looking for knowledge atoms, the units from which program understanding is built, and the resulting atoms were categorized along three orthogonal axes of knowledge type, design decision used, and type of analysis required to uncover the atom.
Abstract
This paper is concerned with the units of knowledge used in understanding programs. A pilot study was conducted wherein a short, but complex, program was examined looking for knowledge atoms, the units from which program understanding is built. The resulting atoms were categorized along three orthogonal axes of knowledge type, design decision used, and the type of analysis required to uncover the atom. The results are discussed relative to several approaches to program understanding taken from the research literature.
Keywords
Computer Science
Computing Machinery and Intelligence (1950)
6,197 Citations2004Alan Turing
IEEE Transactions on Software EngineeringEmpirical Studies of Programming Knowledge
868 Citations1984Elliot Soloway, Kate Ehrlich
Two empirical studies attempt to evaluate the hypothesis that expert programmers have and use two types of programming knowledge: programming plans, which are generic program fragments that represent stereotypic action sequences in programming, and rules of programming discourse, which capture the conventions in programming and govern the composition of the plans into programs.
Software Practice and ExperienceAn empirical study of FORTRAN programs
682 Citations1971Donald E. Knuth
The principal conclusion which may be drawn is the importance of a program ‘profile’, namely a table of frequency counts which record how often each statement is performed in a typical run; there are strong indications that profile‐keeping should become a standard practice in all computer systems, for casual users as well as system programmers.
Software Psychology: Human Factors in Computer and Information Systems
618 Citations1980Ben Shneiderman
International Journal of Parallel ProgrammingSyntactic/semantic interactions in programmer behavior: A model and experimental results
384 Citations1979Ben Shneiderman, Richard E. Mayer
A cognitive framework for describing behaviors involved in program composition, comprehension, debugging, modification, and the acquisition of new programming concepts, skills, and knowledge is presented.
IEEE SoftwareDelocalized Plans and Program Comprehension
246 Citations1986Stanley Letovsky, Elliot Soloway
How to Read a Book
224 Citations1940Mortimer J. Adler, Charles Lincoln Van Doren
IEEE SoftwareRecognizing a program's design: a graph-parsing approach
202 Citations1990Charles Rich, Frederick W. B. Li
A prototype, the Recognizer, is described that automatically finds all occurrences of a given set ofCliches in a program and builds a hierarchical description of the program in terms of the cliches it finds.
Computational IntelligenceAutomatic program debugging for intelligent tutoring systems
105 Citations1987William R. Murray
The research presented provides a methodology and implementation for the diagnosis and correction of nontrivial recursive programs by repairing induction proofs in the Boyer‐Moore logic.
Communications of the ACMA memory-based approach to recognizing programming plans
103 Citations1994Alex Quilici
This work is interested in recognizing common ol$xts and operations in C programs and replacing them with libraries containing human-generated object-oriented code written in C ++, and automatically extracting object- oriented design knowledge to support translating C programs to C ++.
IEEE Transactions on Software EngineeringUnderstanding and Documenting Programs
88 Citations1982Victor R. Basili, Harlan D. Mills
The goal was to simulate a practicing programmer in a program maintenance environment using the techniques of program design adapted to program understanding and documentation; that is, given a program, a specification and correctness proof were developed for the program.
IEEE SoftwareRecognizing design decisions in programs
78 Citations1990Spencer Rugaber, S.B. Ornburn +1 more
The authors present a characterization of design decisions that is based on the analysis of programming constructs that underlies a framework for documenting and manipulating design information to facilitate maintenance and reuse activities.
Automated Software EngineeringAutomated program understanding by concept recognition
58 Citations1994W. Kozaczynski, Jim Q. Ning
An approach to automated concept recognition and its implementation is described, which uses a concept model and a library of concept recognition rules to describe what the concepts are and how to recognize them from lower-level concepts.
Automatic Control Understanding for Natural Programs
42 Citations1991John Hartman
A practical method for bottom-up control concept recognition in large, unstructured imperative programs and it was shown how the method and UNPROG can be used for empirical study of programs at the conceptual level.
Plan analysis of programs
42 Citations1988Stanley Letovsky
The results indicated that an acute bout of eccentric muscle damage does not accentuate training-induced gains in strength and did not enhance the response to conventional strength training and significantly compromised strength gains for several weeks.
IEEE Transactions on Software EngineeringA knowledge-based approach to the analysis of loops
36 Citations1996Salwa K. Abd–El–Hafiz, Victor R. Basili
A knowledge-based analysis approach that generates first order predicate logic annotations of loops is presented and a consistent and rigorous functional abstraction of the whole loop is synthesized from the specifications of its individual events.
Lecture notes in computer scienceUsing attributed flow graph parsing to recognize clichés in programs
24 Citations1996Frederick W. B. Li
This paper uses a flow graph formalism, which is closely related to hypergraph formalisms, to represent programs and cliches and uses attributed flow graph parsing to automate recognition.
Understanding Interleaved Code
19 Citations2007Spencer Rugaber, Kurt Stirewalt +1 more
Automated Software EngineeringUnderstanding interleaved code
14 Citations1996Spencer Rugaber, Kurt Stirewalt +1 more
The experiences in developing tools to detect specific classes of interleaving in this software are described, driven by the need to enhance a formal description of this software library's components, which aids in the automated component-based synthesis of software using the library.
SMARTech Repository (Georgia Institute of Technology)An Example of Program Understanding
3 Citations1998Spencer Rugaber
An example of program understanding i n action is looked at, where a student is assigned responsibility for maintaining a program written in the FORTRAN language and concerned with finding the roots of functio.