1999
DOI: 10.1006/ijhc.1998.0236
|View full text |Cite
|
Sign up to set email alerts
|

Mental representations of expert procedural and object-oriented programmers in a software maintenance task

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

3
37
0

Year Published

2001
2001
2015
2015

Publication Types

Select...
5
3
1

Relationship

1
8

Authors

Journals

citations
Cited by 51 publications
(40 citation statements)
references
References 30 publications
3
37
0
Order By: Relevance
“…For example, maintenance personnel often successfully modify software without understanding it fully (see, for example, Corritore and Wiedenbeck 1999, Littman et al 1986, Pennington 1987b. Further, given the size of many industrial applications, it seems unlikely that maintenance personnel could devote the time necessary to develop a complete understanding of the entire application in the course of conducting a modification.…”
Section: Introductionmentioning
confidence: 99%
“…For example, maintenance personnel often successfully modify software without understanding it fully (see, for example, Corritore and Wiedenbeck 1999, Littman et al 1986, Pennington 1987b. Further, given the size of many industrial applications, it seems unlikely that maintenance personnel could devote the time necessary to develop a complete understanding of the entire application in the course of conducting a modification.…”
Section: Introductionmentioning
confidence: 99%
“…Studies show that efforts applied on maintenance are mainly targeted to the comprehension part [11].…”
Section: Related Literaturementioning
confidence: 99%
“…Program comprehension requires that the maintainer represent the software mentally [15,16]. A number of models have been proposed to describe the cognitive processes by which program comprehension may be achieved.…”
Section: Analysability Of Object-oriented Softwarementioning
confidence: 99%
“…Pennington's model) are based on experiences of very small programs or parts of a program with 200 or lines of code or fewer. Corritore and Wiedenbeck describe an empirical study that investigated the mental representations of maintainers when working on software developed by expert procedural and object-oriented programmers [15]. In this study, the program being maintained consisted of about 800 lines of code, and hence was considered to be rather large.…”
Section: Analysability Of Object-oriented Softwarementioning
confidence: 99%