ACM Home Page
Please provide us with feedback. Feedback
The reuse of uses in Smalltalk programming
Full text PdfPdf (1.02 MB)
Source ACM Transactions on Computer-Human Interaction (TOCHI) archive
Volume 3 ,  Issue 3  (September 1996) table of contents
Pages: 219 - 253  
Year of Publication: 1996
ISSN:1073-0516
Authors
Mary Beth Rosson  Virginia Polytechnic Institute and State Univ., Blacksburg, VA
John M. Carroll  Virginia Polytechnic Institute and State Univ., Blacksburg, VA
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 11,   Downloads (12 Months): 57,   Citation Count: 22
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/234526.234530
What is a DOI?

ABSTRACT

Software reuse, a long-standing and refractory issue in software technology, has been specifically emphasized as an advantage of the object-oriented programming paradigm. We report an empirical study of expert Smalltalk programmers reusing user interface classes in small graphical applications. Our primary goal was to develop a qualitative characterization of expert reuse strategies that could be used to identify requirements for teaching and supporting reuse programming. A secondary interest was to demonstrate to these experts the Reuse View Matcher—a prototype reuse tool—and to collect some initial observations of this tool in use during reuse programming. We observed extensive “reuse of uses” in the programmers' work: they relied heavily on code in expample applications that provided an implicit specification for reuse of the target class. We called this implicit specification a “usage context.” The programmers searched for relevant usage contexts early. They repeatedly evaluated the contextualized information to develop solution plans, and they borrowed and adapted it when the sample context suited their immediate reuse goals. The process of code development was highly dynamic and incremental; analysis and implementation were tightly interleaved, frequently driven by testing and debugging. These results are considered in terms of the tradeoffs that inhere in the reuse of uses and the teaching and tool support that might improve the efficiency and accuracy of this approach to reuse.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
AUSUBEL, D. P. 1960. The use of advance organizers in the learning and retention of meaningful verbal material. J. Educ. Psychol. 51, 267-272.
 
2
3
 
4
BIGGERSTAFF,T.J.AND RICHTER, C. 1987. Reusability framework, assessment, and direc-tions. IEEE Softw. 4, 2 (Mar.), 41-49.
 
5
 
6
CARROLL,J.M.AND ROSSON, M. B. 1991. Deliberated evolution: Stalking the View Matcher in design space. Hum. Comput. Interact. 6, 3-4, 281-318.
 
7
8
 
9
CARROLL,J.M.,THOMAS,J.C.,AND MALHOTRA, A. 1979. A clinical-experimental analysis of design problem solving. Des. Stud. 1, 2, 84-92.
 
10
 
11
COX, B. J. 1987. Building malleable systems from software "chips." Computerworld (Mar.), 59-86.
 
12
DE~ TIENNE, F. 1991. Reasoning from a schema and from an analog in software code reuse. In Proceedings of Workshop on Empirical Studies of Programmers (ESP IV). Ablex, Norwood, N.J., 5-22.
13
 
14
DIGITALK, I. 1989. Smalltalk/V PM: Object-Oriented Programming System. Digitalk Inc., Los Angeles, Calif.
 
15
ERICSSON,K.A.AND SIMON, H. A. 1980. Verbal reports as data. Psychol. Rev. 87, 215-251.
 
16
FISCHER, G. 1987. Cognitive view of reuse and redesign. IEEE Softw. 4, 3, 60-72.
 
17
FLANAGAN, J. C. 1954. The critical incident technique. Psychol. Bull. 51, 28, 28-35.
 
18
GUINDON, R. 1990. Designing the design process: Exploiting opportunistic thoughts. Hum. Comput. Interact. 5, 1, 305-344.
19
 
20
JOHNSON,R.E.AND FOOTE, B. 1988. Designing reusable classes. J. Object-Oriented Pro-gram. 1, 2 (June/July), 22-35.
21
22
 
23
 
24
MEYER, B. 1987. Reusability: The case for object-oriented design. IEEE Softw. 4, 2 (Mar.), 50-64.
 
25
26
 
27
RAJ,R.K.AND LEVY, H. M. 1989. A compositional model of software reuse. In Proceedings of European Conference on Object-Oriented Programming (ECOOP '89). British Computer Society, London, U.K., 3-24.
28
 
29
30
31
 
32
 
33
TAENZER, D., GANTI, M., AND PODAR, S. 1989. Problems in object-oriented software reuse. In Proceedings of European Conference on Object-Oriented Programming (ECOOP '89). British Computer Society, Cambridge, U.K., 25-38.
 
34

CITED BY  22

Collaborative Colleagues:
Mary Beth Rosson: colleagues
John M. Carroll: colleagues