Cognitive activities of abstraction in object orientation

Or‐Bach, Rachel; Lavy, Ilana

doi:10.1145/1024338.1024378

Cited by 69 publications

(47 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The students had difficulties in exhibiting high levels of assimilation concerning a proper design for a hierarchy of exceptions. These results are in line with previous research regarding the object-oriented design capabilities of novice programmers (Lavy et al, 2009;Or-Bach & Lavy, 2004;Sim & Wright, 2001). …”

Section: Discussionsupporting

confidence: 92%

See 1 more Smart Citation

Students’ Strategies for Exception Handling

Rashkovits

Lavy

2011

JITE:Research

Self Cite

View full text Add to dashboard Cite

Executive SummaryThis study discusses and presents various strategies employed by novice programmers concerning exception handling. The main contributions of this paper are as follows: we provide an analysis tool to measure the level of assimilation of exception handling mechanism; we present and analyse strategies to handle exceptions; we present and analyse solutions provided by novice programmers; we classify and analyse the participants' reflections concerning their solutions. Modern programming languages, such as Java, provide the programmer an elaborated object oriented exception mechanism; enable him to handle exceptions in a more convenient way. The aim of this study was to discover the strategies novice programmers are using to handle exceptions and whether they utilise the advantage of the modern exception handling mechanism. For that matter the participants (college students) had to provide a written solution to a given problem with a special focus on exception handling. In addition each of them was interviewed. The analysis of the solutions provided was carried out according to a set of software quality criteria (clarity, modularity and extensibility) adapted to exception handling characteristics. These criteria were used to explain the advantages and disadvantages of the solutions from a software engineering perspective. The solutions provided were also analysed according to a classification of levels of assimilation concerning the structure of exceptions, based on the SOLO taxonomy. The first level of assimilation refers to solutions in which no exception mechanism was used, and the errors were handled in the old fashion way (local handling or return of an error code). The fifth and last level refers to solutions that used adequate hierarchy of exception classes allowing easy extension according to future requirements and enabling the handling of multiple exception altogether or handle each separately. In between these levels there are strategies that used exception mechanisms without the exhausting of its advantages. The results obtained reveal that only few participants (7 out of 56) provided a solution that was classified to one of the two highest assimilation levels, while many (23 out of 56) did not use exception mechanism at all. The rest of the students (25 out of 56) used the exception mechanism poorly (i.e., used only Exception class or did not use hierarchy of exceptions). The participants had difficulties in utilising the advanced exception handling mechanisms and in exhibiting a high level of abstraction with regard to the proper design of a hierarchy of exceptions. The students' statements collected during the interviews were classified into the following categories: misconceptions concerning code quality; misconceptions concerning exception handling; difficulties in understanding the exception handling mechanism; the perceived importance of exception handling; and a lack of programming experience. During the interviews the students provided explanations concerning the reasons they wer...

show abstract

Section: Discussionsupporting

confidence: 92%

“…In addition, to be able to construct an adequate class hierarchy, the student must demonstrate a high level of abstraction. Previous research has shown that few students are able to do this (Lavy, Rashkovits, & Kouris, 2009;Or-Bach & Lavy, 2004). …”

Section: Machineoperationexception)mentioning

confidence: 99%

Students’ Strategies for Exception Handling

Rashkovits

Lavy

2011

JITE:Research

Self Cite

View full text Add to dashboard Cite

show abstract

“…The students had difficulty exhibiting high levels of understanding concerning the following: use of multiple exceptions; flow of control in the context of exceptions; handling exceptions further up the calling chain; catching and handling hierarchically related exceptions; and overriding methods that throw exceptions. These results are consistent with previous research regarding the object-oriented design capabilities of novice programmers (Lavy, Rashkovits, & Kouris, 2009;Or-Bach & Lavy, 2004;Sim & Wright, 2001). …”

Section: Discussionsupporting

confidence: 92%

“…The concepts of class hierarchy and method override are part of the object-oriented paradigm which necessitates a certain level of abstraction and hence is difficult to comprehend (Or-Bach & Lavy, 2004;Sim & Wright, 2001). Also the fact that when an exception is thrown the control is passed to the nearest catch clause up the calling chain requires a profound understanding of the fundamentals of computing (memory stack, flow of control, etc.)…”

Section: Perceptions Concerning the Complexity Of The Exception Mechamentioning

confidence: 99%

Students’ Understanding of Advanced Properties of Java Exceptions

Rashkovits

Lavy

2012

JITE:IIP

Self Cite

View full text Add to dashboard Cite

Executive SummaryThis study examines how Information Systems Engineering School students on the verge of their graduation understand the mechanism of exception handling. The main contributions of this paper are as follows: we construct a questionnaire aimed at examining students' level of understanding concerning exceptions; we classify and analyse the students' responses to the questionnaire in order to determine their level of understanding of the mechanism; and we discuss the students' reflections concerning exceptions. The students were required to demonstrate their understanding of various aspects of Java exception handling: exception throwing and catching, fluency of code in the presence of exceptions, multiple catch clauses, common and different reactions to the various exceptions, passing an exception up the calling chain, proper use of the exception hierarchy, re-throwing an exception, and overriding a method which throws exceptions. The results obtained reveal that almost all the participants understood the basics of throwing and catching an exception, but only a few demonstrated the highest level of understanding of the exception mechanism. As the level of understanding required to address the questionnaire problems increased, the number of study participants who were able to answer correctly decreased substantially. In fact, most of the study participants were not familiar with all the possibilities encompassed by the exception mechanism and so were not able to use them properly. The students' reflections were classified into the following categories: perceptions concerning the benefits of using exceptions; perceptions concerning the complexity of the exception mechanism; and issues concerning the development environment. According to the results obtained we recommend several modifications to the curriculum with the aim of improving the students' ability to properly utilize the advanced properties of exceptions to produce higher quality software.

show abstract

“…Many graduating students turn out to be unable to create a proper software design [14,25]. Students struggle with the application of concepts such as abstraction and polymorphism [28] and information hiding [16]. These findings suggest that a form of scaffolding of students' learning is in order, so the question arises what kind of scaffolding is appropriate.…”

Section: Introductionmentioning

confidence: 99%

Analyzing students' software redesign strategies

Stuurman

Passier

Barendsen

2016

Proceedings of the 16th Koli Calling International Conference on Computing Education Research

View full text Add to dashboard Cite

The design of software is known to be difficult for novice computer scientists. In this paper, we focus on software redesign and on the refactoring necessary to implement a redesign. Redesigning an application aims to improve nonfunctional aspects such as extensibility, without changing the functionality. Redesign is a complex task, involving knowledge and skills from software design in general and the use of design patterns in particular. This study is part of an educational design research project aiming at developing scaffolding for students' software redesign activities in the form of procedural guidance. We investigated students' strategies and usage of concepts during a software redesign assignment using students' reports and team colllaboration recordings as data sources, thus focusing on the process instead of on the design results, in contrast with existing studies. We identified several difficulties that can serve as starting points for procedural guidance. For instance, students seem to avoid using a structured analysis method. Our findings indicate that students' activities were mainly directed towards the code rather than the design problem.

show abstract

Cognitive activities of abstraction in object orientation

Cited by 69 publications

References 10 publications

Students’ Strategies for Exception Handling

Students’ Strategies for Exception Handling

Students’ Understanding of Advanced Properties of Java Exceptions

Analyzing students' software redesign strategies

Contact Info

Product

Resources

About