Some strategies of reuse in an object-oriented programming environment

Lange, B. M.; Moher, Tom

doi:10.1145/67450.67465

Cited by 21 publications

(25 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…It appeared that one particular element might be considered as a model at one moment and as a plugin component at another time. Our findings are consistent with results of previous studies on software design (Lange & Moher, 1989) or software enhancement by reusing supplied classes (Rosson & Carroll, 1993), and illustrate that models can also come from the current or other analogical problem domains.…”

Section: Interaction(s) Between Design and Reusesupporting

confidence: 91%

“…Second, it examines reuse in the context of object-oriented programming which is assumed by its advocates to facilitate reuse. Few studies (Détienne, 1991;Lange & Moher, 1989) have analysed reuse in that context. 1 This research is partially sponsored by the European Esprit III SCALE 6334 project (System Composition and Large Grain Component Reuse Support) Our study focuses on the three following aspects of reuse : the interaction between design and reuse processes, the mental processes involved in reuse, and the mental representations constructed throughout the reuse activity.…”

Section: Framework and Goalsmentioning

confidence: 99%

See 1 more Smart Citation

An Empirical Study of Software Reuse by Experts in Object-Oriented Design

Burkhardt

Détienne

1995

IFIP Advances in Information and Communication Technology

View full text Add to dashboard Cite

: This paper presents an empirical study of the software reuse activity by expert designers in the context of object-oriented design. Our study focuses on the three following aspects of reuse : (1) the interaction between some design processes, e.g. constructing a problem representation, searching for and evaluating solutions, and reuse processes, i.e. retrieving and using previous solutions, (2) the mental processes involved in reuse, e.g. example-based retrieval or bottom-up versus top-down expanding of the solution, and (3) the mental representations constructed throughout the reuse activity, e.g. dynamic versus static representations. Some implications of these results for the specification of software reuse support environments are discussed.

show abstract

Section: Interaction(s) Between Design and Reusesupporting

confidence: 91%

Section: Framework and Goalsmentioning

confidence: 99%

An Empirical Study of Software Reuse by Experts in Object-Oriented Design

Burkhardt

Détienne

1995

IFIP Advances in Information and Communication Technology

View full text Add to dashboard Cite

show abstract

“…Expert OO designers utilise reuse through built-in-classes whereas the novices do not spontaneously take advantage of built-in classes (Lee & Pennington, 1994). Second, contrary to the claims about how OO languages might facilitate reuse, Lange and Moher (1989) and Détienne (1991) found that reuse efforts did not centre on reuse by specialising the inheritance hierarchy but rather on literal copying and modification of code. Third, reuse involves some particular expertise different from expertise in the programming domain and expertise in the problem (task) domain.…”

Section: Reuse Activitymentioning

confidence: 98%

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

“…So, when developers encounter problems that have already been solved in the past, rather then re-inventing the wheel, or spending time componentizing the already available solution (which is sometimes not preferable [8]) they perform reuse tasks [2]. Reusing source code that was not designed in a reusable fashion is known by different synonyms: copyand-paste reuse [10], code scavenging [9] and, more recently, pragmatic-reuse [5]. Pragmatic reuse treats the system in a white-box fashion and involves extracting functionality from an existing system and reusing it within another system.…”

Section: Introductionmentioning

confidence: 99%

Reusing Web Application User-Interface Controls

Maras

Štula

Carlson

2011

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. Highly interactive web applications that offer user experience and responsiveness of desktop applications are becoming increasingly popular. They are often composed out of visually distinctive userinterface (UI) elements that encapsulate a certain behavior -the so called UI controls. Similar controls are often used in a large number of web pages, and facilitating their reuse could offer considerable benefits. Unfortunately, because of a very short time-to-market, and a fast pace of technology development, preparing controls for reuse is usually not a primary concern. In this paper we present a semi-automatic method, and the accompanying tool, for extracting and reusing web controls. The developer selects the control and performs a series of interactions that represent the behavior he/she wishes to reuse. In the background, the execution is analyzed and all code and resources necessary for the standalone functioning of the control are extracted. Optionally, the user can immediately reuse the extracted control by automatically embedding it in an already existing page.

show abstract

Some strategies of reuse in an object-oriented programming environment

Cited by 21 publications

References 3 publications

An Empirical Study of Software Reuse by Experts in Object-Oriented Design

An Empirical Study of Software Reuse by Experts in Object-Oriented Design

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

Reusing Web Application User-Interface Controls

Contact Info

Product

Resources

About