The effects of paradigm on cognitive activities in design

Lee, Adrienne; Pennington, Nancy

doi:10.1006/ijhc.1994.1028

Cited by 40 publications

(45 citation statements)

References 28 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…On the basis of their observations the authors suggest that much of OOD in its earlier phases is driven by an understanding of the problem itself rather than by specialised design knowledge. On the contrary, the solutions of procedural designers are structured by generic programming constructs rather than by entities of the problem domain.Furthermore, it has been found that compared to procedural designers, OO designers produce more similar final solutions with similar objects and methods (Boehm-Davis & Ross, 1992;Lee & Pennington, 1994). This similarity could be attributed to a close mapping of the problem domain.…”

mentioning

confidence: 97%

“…Some preliminary results will be reported in 4.1.1. Computers, 1997, 9, p 47-72 http://www.elsevier.com/wps/find/journaldescription.cws_home/525445/description#description 9 to hope that the classes created in this way will be useful later on (Lee & Pennington, 1994;Pennington, Lee & Rehder, 1995) Novices behave this way not just because they follow a method learned in class but also because of environment constraints, i.e., order constraints which entail premature commitment (Green, 1989). …”

mentioning

confidence: 99%

“…With regard to the claims made about naturalness and ease of design in the OO paradigm, an important issue is whether the problem decomposition is driven by problem domain entities. In several comparative studies ( Lee & Pennington, 1994;Pennington, Lee & Rehder, 1995;Rosson & Gold, 1989) it has been shown that problem decomposition is driven by problem domain entities for OO expert designers whereas for procedural designers the decomposition is driven by generic programming constructs and specialised design knowledge.In Pennington's studies ( Lee & Pennington, 1994;Pennington, Lee & Rehder, 1995) it was found that expert OO designers analyse a situation through its objects. Compared to procedural design, less time is spent analysing the problem situation and more time is spent describing objects and their relationships.…”

mentioning

confidence: 99%

See 2 more Smart Citations

Assessing the cognitive consequences of the object-oriented approach: A survey of empirical research on object-oriented design by individuals and teams

Détienne¹

1997

Interacting with Computers

View full text Add to dashboard Cite

This paper presents a state-of-art review of empirical research on object-oriented (OO) design. Many claims about the cognitive benefits of the OO paradigm have been made by its advocates. These claims concern the ease of designing and reusing software at the individual level as well as the benefits of this paradigm at the team level. Since these claims are cognitive in nature, its seems important to assess them empirically. After a brief presentation of the main concepts of the OO paradigm, the claims about the superiority of OO design are outlined. Computers, 1997, 9, p 47-72 http://www.elsevier.com/wps/find/journaldescription.cws_home/525445/description#description 2 The core of this paper consists of a review of empirical studies of OOD. We first discuss results concerning OOD by individuals. On the basis of empirical work, we (1) analyse the design activity of novice OO designers, (2) compare OO design with procedural design and, (3) discuss a typology of problems relevant for the OO approach. Then we assess the claims about naturalness and ease of OO design. Published in Interacting withThe next part discusses results on OO software reuse. On the basis of empirical work, we (1) compare reuse in the OO versus procedural paradigm, (2) discuss the potential for OO software reuse and (3) analyse reuse activity in the OO paradigm. Then we assess claims on reusability.The final part reviews empirical work on OO design by teams. We present results on communication, coordination, knowledge dissemination and interactions with clients. Then we assess claims about OOD at the software design team level.In a general conclusion, we discuss the limitations of these studies and give some directions for future research. Computers, 1997, 9, p 47-72 Interactions with clients 6.4 Published in Interacting withAssessing claims about OOD in design teams Limitations and directions for future work ReferencesPublished in Interacting with Computers, 1997, 9, p 47-72 IntroductionThis paper presents a state-of-art review of empirical research on object-oriented (OO) design. OO technology has been accepted by both academia and industry in a very short time. Ten years ago, the few OO languages available were seen as interesting ideas. Since then, new languages have been designed and existing languages have been extended to become object-oriented. Many claims about the cognitive benefits of the OO paradigm have been made by its advocates. These claims concern the ease of designing and reusing software at the individual level as well as the benefits of this paradigm at the team level. Given the rapid acceptance of this new technology, it is imperative to understand the process and to evaluate the benefits of OO design. Since these claims are cognitive in nature, its seems important to assess them empirically (Détienne & Rist, 1995).Since 1990, much empirical work has been conducted on OO design both at the individual level and at the software design team level. These studies are field studies and laboratory studies. Th...

show abstract

mentioning

confidence: 97%

mentioning

confidence: 99%

mentioning

confidence: 99%

See 1 more Smart Citation

Assessing the cognitive consequences of the object-oriented approach: A survey of empirical research on object-oriented design by individuals and teams

Détienne¹

1997

Interacting with Computers

View full text Add to dashboard Cite

show abstract

“…Due to the fact that the convex hull area and the spatial density are correlated and measure the exploration-search ability of the subjects, the significant differences with these two measures show that, while experts have a directed and efficient search of the relevant constituents, novices have an extended and inefficient search. These findings can be related to the results of Lee and Pennington [18], which show that, while the experts think directly from the understanding of the problem to the identification of the relevant elements, the novices are not able to analyze the problem directly through their objects.…”

Section: B Rq2: Experts Vs Novices 1) Resultsmentioning

confidence: 77%

“…When study the cognitive activities of object-oriented experts and object-oriented novices, Lee and Pennington [18] found that "the object-oriented novices were not able to analyze the situation directly through their objects, as were the object-oriented experts".…”

Section: A Experts and Novices Comparisonmentioning

confidence: 99%

Professional status and expertise for UML class diagram comprehension: An empirical study

Soh

Sharafi

Plas³

et al. 2012

2012 20th IEEE International Conference on Program Comprehension (ICPC)

View full text Add to dashboard Cite

Abstract-Professional experience is one of the most important criteria for almost any job offer in software engineering. Professional experience refers both to professional status (practitioner vs. student) and expertise (expert vs. novice). We perform an experiment with 21 subjects including both practitioners and students, and experts and novices. We seek to understand the relation between the speed and accuracy of the subjects and their status and expertise in performing maintenance tasks on UML class diagrams. We also study the impact of the formulation of the maintenance task. We use an eye-tracking system to gather the fixations of the subjects when performing the task. We measure the subjects' comprehension using their accuracy, the time spent, the search effort, the overall effort, and the question comprehension effort. We found that (1) practitioners are more accurate than students while students spend around 35 percent less time than practitioners, (2) experts are more accurate than novices while novices spending around 33 percent less time than experts, (3) expertise is the most important factor for accuracy and speed, (4) experienced students are more accurate and spend around 37 percent less time than experienced practitioners, and (5) when the description of the task is precise, the novice students can be accurate. We conclude that it is an illusion for project managers to focus on status only when recruiting a software engineer. Our result is the starting point to consider the differences between status and expertise when studying software engineers' productivity. Thus, it can help project managers to recruit productive engineers and motivated students to acquire the experience and ability in the projects.

show abstract

The process of software maintenance: a comparison of object‐oriented and third‐generation development languages

Eierman

Dishaw

2007

J. Softw. Maint. Evol.: Res. Pract.

View full text Add to dashboard Cite

We suggest that there is a lack of empirical evidence for claims that object‐oriented software has an advantage in terms of software maintenance. We use a model of software maintenance that suggests that the maintenance task and programming language have an impact on the maintenance process and, in turn, use the maintenance process to explore the impact of the programming language on the maintenance process. A field study design, using students, examined the perceived difference in process employed by students using an object‐oriented language and those using a third‐generation language. We found a difference in the perceived process used by the two groups of students. Students using the object‐oriented language perceived that they performed more planning and diagnosis activities during the maintenance process and students using a third‐generation language perceived that they performed more knowledge building activities. Copyright © 2007 John Wiley & Sons, Ltd.

show abstract

The effects of paradigm on cognitive activities in design

Cited by 40 publications

References 28 publications

Assessing the cognitive consequences of the object-oriented approach: A survey of empirical research on object-oriented design by individuals and teams

Assessing the cognitive consequences of the object-oriented approach: A survey of empirical research on object-oriented design by individuals and teams

Professional status and expertise for UML class diagram comprehension: An empirical study

The process of software maintenance: a comparison of object‐oriented and third‐generation development languages

Contact Info

Product

Resources

About