Reuse dimensions

ABSTRACT

In recent years, there have been much publications on reuse. In order to bet an overview of the whole field and also a good impression of the state of the reuse art, we studied reuse literature of the last few years. As basis for comparison, we classified literature according to four (more or less orthogonal) dimensions, based on the actions and knowledge of the reuser, i.e. the software engineer. The dimensions are: actions to be taken to get an existing reusable item; knowledge to be applied to find an existing reusable item; actions to be taken to build the complete system needed; knowledge to be applied to get the complete system needed.The survey shows that research on reuse from the viewpoint of needed system, receives far less attention than research from the viewpoint of reusable artifacts. We expect reuse to live up to its promise if this topic is addressed was well.

REFERENCES

• 1: W.W. Agresti, editor. New Paradigms for Software Development. IEEE Computer Society Press, 1986.
• 2: A Nikitas Alexandridis, Adaptable software and hardware: Problems and solutions, Computer, v.19 n.2, p.29-39, Feb. 1986 [doi>10.1109/MC.1986.1663147]
• 3: Alejandro Alonso , Juan A. de la Puente, Reusable real-time executive in Ada design issues, ACM SIGAda Ada Letters, v.XIII n.2, p.44-53, March/April 1993 [doi>10.1145/152827.152830]
• 4: G Arango , I Baxter , P Freeman , C Pidgeon, Maintenance and porting of software by design recovery, The Institute of Electrical and Electronics Engineers, Inc on Conference on software maintenance--1985, p.42-49, January 1986, Washington, D.C, United States
• 5: Guillermo Arango, Eric Schoen, and Robert Pet tengill. Design as Evolution and Reuse. In Prieto-Diaz and Frakes {102}, pages 9-18.
• 6: S.P. Arnold and S.L. Stepoway. The REUSE system: Cataloging and retrieval of reusable software. In Michael {92}, pages 376-379.
• 7: C. Ausnit, C. Braun, E. Sterling, J. Goodenough, and R. Simpson. Ada Reusability Guidelines. Technical Report Report no 3285-2-208/2, SofTech Inc., Waltham, MA, April 1985.
• 8: S.C. Bailin and S. Henderson. Towards a Case-Based Software Engineering Environment. In et al. {49}.
• 9: D.R. Barstow. A Perspective on Automatic Programming. Ai Magazine, pages 5-27, Spring 1984.
• 10: David R. Barstow, Domain-specific automatic programming, IEEE Transactions on Software Engineering, v.11 n.11, p.1321-1336, Nov. 1985 [doi>10.1109/TSE.1985.231881]
• 11: Don Batory and Sean O'Malley. Genvoca: Reuse In Layered Domains. In Ruben Prieto-Diaz, Wilhelm Sch~ifer, Joachim Cramer, and Stefan Wolf, editors, Procveedings of the First International Workshop on Software Reusability, Dortmund, Germany, July 3-5, 1991, number MEMO Nr. 57, pages 108-113. 1991.
• 12: Don Batory , Vivek Singhal , Jeff Thomas , Sankar Dasari , Bart Geraci , Marty Sirkin, The GenVoca Model of Software-System Generators, IEEE Software, v.11 n.5, p.89-94, September 1994 [doi>10.1109/52.311067]
• 13: Ira D. Baxter, Design maintenance systems, Communications of the ACM, v.35 n.4, p.73-89, April 1992 [doi>10.1145/129852.129859]
• 14: E.V. Berard. Software Reusability Cannot Be Considered in a Vacuum. In Michael {92}, pages 390-393.
• 15: T Biggerstaff and C. Richter. Reusability Framework, Assessment, and Directions. iEEE Software, 4(2):41- 49, 1987.
• 16: Ted J. Biggerstaff. Hypermedia as a Tool to Aid Large Scale Reuse. In Workshop on Software Reuse, Rocky Mountain Institute of Software Engineering, Boulder, CO, October 1987.
• 17: Ted J. Biggerstaff. Design Recovery for Maintenance and Reuse. Technical Report STP-378-88, Microelectronics and Computer Technology Corporation (MCC), November 1988.
• 18: Ted J. Biggerstaff, Design Recovery for Maintenance and Reuse, Computer, v.22 n.7, p.36-49, July 1989 [doi>10.1109/2.30731]
• 19: T.j. Biggerstaff and A.J. Perlis. Foreword on Reusability. IEEE Transactions on Software Engineering, 10(5):474--476, September 1984.
• 20: Ted J. Biggerstaff , Alan J. Perlis, Software reusability: vol. 1, concepts and models, ACM Press, New York, NY, 1989
• 21: H.G. Birch. The Relation of Previous Experience to Insightful Problem-Solving. Journal of Comparative Psychology, 38:367-383, 1945.
• 22: H.G. Birch and H.S. Rabinowitz. The Negative Effect of Previous Experience on Productive Thinking. In Wason and Johnson-Laird {122}, chapter 3.
• 23: M.F. Bott. Software Reuse -- An Overview. In IEE Colloquium on Reusable Software Components (Digest No. 68), page 28. IEE, London England, 1987.
• 24: M.F. Bott, A. Elliot, and R.J. Gautier. Ada Reuse Guidelines. Technical Report ECLIPSE/REUSE/DST/ADA-GUIDE/RP, Software Sciences Ltd., 1986.
• 25: C.L. Braun, J.B. Goodenough, and R.S. Eanes. Ada Reusability Guidelines. Technical Report TR 3285-2- 208/2, SoftTech Inc., April 1985.
• 26: P.T Breuer and K. Lano. REDO at Oxford. In Dusink and Hall {45}, pages 39--49.
• 27: B.A. Burton, R.W. Aragon, S.A. Bailey, K.D. Koehler, and L.A. Mayes. The Reusable Software Library. IEEE Software, 4(4):25-33, 1987.
• 28: B.A. Burton and M.D. Broido. Development of an Ada Package Library. In NASA'86 {93}.
• 29: S. Castano and V. De Antonellis. A Constructive Approach to Reuse of Conceptual Components. In Prieto-Diaz and Frakes { 102}, pages 19-28.
• 30: P.S. Chen, R. Hennicker, and M. Jarke. On the Retrieval of Reusable Software Components. In Prieto- Diaz and Frakes {102}, pages 99-108.
• 31: T.T Cheng, E.D. Lock, and N.S. Prywes. Use of Very High Level Languages and Program Generation by Management Professionals. IEEE Transactions on Software Engineering, 10(5):552-563, September 1984.
• 32: J. Clapp. Software Reusability: A Management View. In COMPSAC'84 {35}, pages 479-480.
• 33: J. Craig Cleaveland, Building Application Generators, IEEE Software, v.5 n.4, p.25-33, July 1988 [doi>10.1109/52.17799]
• 34: The Small Computer (R)Evolution, Proceedings of COMPCON Fall 84, Sept 1984, Silver Spring, VA, USA, 1984. IEEE Computer Society Press.
• 35: Proceedings of COMPSAC 84, Silver Spring, MD, USA, November 1984. IEEE Computer Society Press.
• 36: Joachim Cramer, Heike Htinnekens, Wilhelm Sch~ifer, and Stefan Wolf. The MERLIN Approach to the Reuse of Software Components. In Dusink and Hall {45}, pages 57-75.
• 37: A. Cross. Design intelligence: The Use of Codes and Language Systems. Design Studies, 7(1): 14-19, 1986.
• 38: M. D'Alessandro, EL. Iachini, and A. Martelli. The Generic Reusable Component: An Approach to Reuse Hierarchical OO Designs. In Prieto-Diaz and Frakes {102}, pages 39-46.
• 39: T. Davis. The Reuse Capability Model: A Basis for Improving an Organization's Reuse Capability. In Prieto-Diaz and Frakes {102}, pages 126-133.
• 40: Prem Devanbu , Ron Brachman , Peter G. Selfridge, LaSSIE: a knowledge-based software information system, Communications of the ACM, v.34 n.5, p.34-49, May 1991 [doi>10.1145/103167.103172]
• 41: E.M. Dusink. A Design Method to Make Re-Use Happen, chapter 8, pages 87-96. In Dusink and Hall {45}, 1991.
• 42: E.M. Dusink. Reuse is not done in a Vacuum. In et al. {49}.
• 43: E.M. Dusink and L. Latour. Controlling Functional Fixedness: the Essence of Successful Reuse. In N Wognum, editor, Ecai94, Workshop Proceedings Design for Reuse, 1994.
• 44: E. M. Dusink , J. van Katwijk, Reflections on reusable software and software components, Proceedings of the Ada-Europe International Conference on Ada-components: libraries and tools, p.113-126, November 1987, Stockholm, Sweden
• 45: Liesbeth Dusink and Patrick Hall, editors. Software Re-Use, Utrecht 1989, Workshops in Computing. Springer Verlag, 1991.
• 46: James Baldo Jr. (ed.). Reuse in Practice Workshop Summary. Technical Report IDA Document D-754, Institute for Defense Analyses, April 1990.
• 47: j. Edwards. Schemas to code. Technical report, Associative Design Technology, Westborough, MA, 1990.
• 48: D. W. Embley , S. N. Woodfield, A knowledge structure for reusing abstract data types, Proceedings of the 9th international conference on Software Engineering, p.360-368, March 1987, Monterey, California, United States
• 49: Larry Latour et al., editor. WISR'92, 5th Annual Workshop on Software Reuse, Palo Alto California, October 26-29 1992, 1992.
• 50: Danielle Fafchamps, Organizational Factors and Reuse, IEEE Software, v.11 n.5, p.31-41, September 1994 [doi>10.1109/52.311049]
• 51: P. Di Felice, Reusability of Mathematical Software: A Contribution, IEEE Transactions on Software Engineering, v.19 n.8, p.835-843, August 1993 [doi>10.1109/32.238586]
• 52: G. Fischer. Cognitive View of Reuse and Redesign. IEEE Software, 4(4):60-72, 1987.
• 53: Gerhard Fischer, Andras C. Lemke, Raymond McCall, and Anders 1. Morch. Making Argumentation Serve Design. to appear in HCI Journal, April 1991.
• 54: W.B. Frakes and B.A. Nejmeh. An information system for software reuse. In Proceedings of the l Oth Minnowbrook Workshop on Software Reuse (Syracuse, N.Y., July 28-31 1987). Syracuse University, 1987.
• 55: W. B. Frakes , T. P. Pole, An Empirical Study of Representation Methods for Reusable Software Components, IEEE Transactions on Software Engineering, v.20 n.8, p.617-630, August 1994 [doi>10.1109/32.310671]
• 56: W.L. Frank. What limits to software gains. Computerworld, pages 65-70, May 1981.
• 57: P. Freeman, Tutorial, software reusability, IEEE Computer Society Press, Los Alamitos, CA, 1987
• 58: M.G. Fugini and S. Faustle. Retrieval of Reusable Components in a Development Information System. In Prieto-Diaz and Frakes { 102}, pages 89-98.
• 59: J.A. Goguen. LIL- A Library Interconnect Language. In Report on Programming Libraries Workshop, pages 12-51, Menlo Park, Calif., October 1983. SRI international.
• 60: J.A. Goguen. Parameterized Programming. IEEE Transactions on Software Engineering, 10(5):528- 543, September 1984.
• 61: M. Griss. A Multi-Disciplinary Software Reuse Program. In et al. {49}.
• 62: F.-J. Grosch and G. Snelting. Polymorphic Components for Monomorphic Languages. In Prieto-Diaz and Frakes {102}, pages 47-55.
• 63: V Grover , E Guerrieri, Expressing module interconnections in Ada, Proc. of the Ada-Europe international conference on Ada: managing the transition, p.273-280, July 1986, Edinburgh, Scotland
• 64: Galen Gruman. Early Reuse Practice lives up to its Promise. IEEE Software, 5:87,88,90,91, November 1988.
• 65: Pat Hall, Cornelia Boldyreff, and Jian Zhang. PRAC- TITIONER: Pragmatic Support for the Re-use of Concepts in Existing Software. In Dusink and Hall {45}, pages 97-108.
• 66: Pat Hall and Ray Weedon. Object Oriented Module Interconnection Languages. In Prieto-Diaz and Frakes {102}, pages 29-38.
• 67: Scott Henninger, Using Iterative Refinement to Find Reusable Software, IEEE Software, v.11 n.5, p.48-59, September 1994 [doi>10.1109/52.311059]
• 68: J.B. Horowitz and E. Munson. An Expansive View of Reusable Software. IEEE Transactions on Software Engineering, 10(5):477-487, September 1984.
• 69: T Hulkkonen , V M Kehä, Software component library, Proc. of the Ada-Europe international conference on Ada: managing the transition, p.175-182, July 1986, Edinburgh, Scotland
• 70: T.C. Jones. Reusability in Programming: A Survey of the State of the Art. IEEE Transactions on Software Engineering, 10(5):487-493, 1984.
• 71: C. Jones, Tutorial programming productivity: issues for the eighties, 2nd ed., IEEE Computer Society Press, Los Alamitos, CA, 1986
• 72: Rebecca Joos, Software Reuse at Motorola, IEEE Software, v.11 n.5, p.42-47, September 1994 [doi>10.1109/52.311058]
• 73: K.C. Kang and L.S. Levy. Software Reuse: What's Behind the Buzzword. Technical Report CMU/SEI- 89-TR-27,ESD-89-TR-36, Software Engineering Institute, Carnegie Mellon University, May 1989.
• 74: B.W. Kernighan. The UNIX System and Software Reusability. IEEE Transactions on Software Engineering, 10(5):513-518, September 1984.
• 75: Charles W. Krueger, Software reuse, ACM Computing Surveys (CSUR), v.24 n.2, p.131-183, June 1992 [doi>10.1145/130844.130856]
• 76: B.S. Ku. SRSGEN- A Software Reuse Tool for Large Scale Applications. In Prieto-Diaz and Frakes {102}, pages 109-115.
• 77: J. Laski and W. Szermer. Regression Analysis of Reusable Program Components. In Prieto-Diaz and Frakes { 102}, pages 134-141.
• 78: Larry Latour. Experiments in Hypermedia Support for the "Understanding for Reuse" Problem. in Larry Latour, editor, WISR'93, 6th Annual Workshop on Software Reuse, Owego New York, November 2-4 1993, 1993.
• 79: Larry Latour, Steve Philbrick, and Chandu Bhavsar, editors. 1991.
• 80: Hsian-Chou Liao , Feng-Jian Wang, Software reuse based on a large object-oriented library, ACM SIGSOFT Software Engineering Notes, v.18 n.1, p.74-80, Jan. 1993 [doi>10.1145/157397.157409]
• 81: Mitchell D. Lubars, Affording higher reliability through software reusability, ACM SIGSOFT Software Engineering Notes, v.11 n.5, p.39-42, Oct. 1986 [doi>10.1145/382298.382367]
• 82: Mitchell D. Lubars, Code reusability in the large versus code reusability in the small, ACM SIGSOFT Software Engineering Notes, v.11 n.1, p.21-28, Jan. 1986 [doi>10.1145/382300.382307]
• 83: Yoëlle S. Maarek , Daniel M. Berry , Gail E. Kaiser, An Information Retrieval Approach for Automatically Constructing Software Libraries, IEEE Transactions on Software Engineering, v.17 n.8, p.800-813, August 1991 [doi>10.1109/32.83915]
• 84: C. MacAnAirchinnigh. Reusable Generic Packages: Design Guidelines Based on Structural Isomorphism. In Proceedings 3rd Annual National Conference on Ada Technology; Hyatt Regency Houston, Houston, Texas, March 1985, pages 132-144. US Army Communications-Electronics Command Fort Monmouth, NJ, US Army, Center for Tactical Computer Systems, 1985.
• 85: M. MacAnAirchinnigh. Conceptual Model of an Ada Software Factory. Technical report, Ada-Europe Environment Working Group. Internal report, 1987.
• 86: Nell Maiden and Alistar Sutcliffe. The Abuse of Reuse: Why Cognitive Aspects of Software Re-usability are Important, chapter 10, pages 109-113. In Dusink and Hall {45}, 1991.
• 87: Johan Margono , Edward V. Berard, A modified Booch's taxonomy for Ada generic data-structure components and their implementation, Proceedings of the Ada-Europe International Conference on Ada-components: libraries and tools, p.61-74, November 1987, Stockholm, Sweden
• 88: William Mark , Sherman Tyler , James McGuire , Jon Schlossberg, Commitment-Based Software Development, IEEE Transactions on Software Engineering, v.18 n.10, p.870-885, October 1992 [doi>10.1109/32.163604]
• 89: Y. Matsumoto. Organizational Effort for Reusing Existing Softwares. In COMPCON'84 {34}.
• 90: M.D. Mcllroy. Mass-Produced Software Components. In J.M. Buxton, P. Naur, and B. Randell, editors, Software Engineering Concepts and Techniques; 1968 NATO Conference on Software Engineering, pages 88-98. Petrocelli/Charter, Belgium, 1976.
• 91: Bertrand Meyer. Reusability: The Case for Object- Oriented Design. IEEE Software, 4(2):50-64, March 1987.
• 92: G.A. (chair) Michael, editor. Intellectual Leverage; Spring Joint Computer Conference 87; 32nd International Conference, San Francisco, Feb 23-271987, Digest ofPapers. IEEE Computer Society Press Washington DC, 1987.
• 93: Proceedings 1st Conference on Ada Programming Applications for the NASA Space Station, Houston, June 1986, 1986.
• 94: N.S. Nise and C. Griffin. Considerations for the Design of Ada Reusable Packages. In NASA' 86 {93}.
• 95: James O'Connor , Catharine Mansour , Jerri Turner-Harris , Grady H. Campbell, Jr., Reuse in Command-and-Control Systems, IEEE Software, v.11 n.5, p.70-79, September 1994 [doi>10.1109/52.311065]
• 96: H. Partsch , R. Steinbrüggen, Program Transformation Systems, ACM Computing Surveys (CSUR), v.15 n.3, p.199-236, Sept. 1983 [doi>10.1145/356914.356917]
• 97: Andy Podgurski , Lynn Pierce, Retrieving reusable software by sampling behavior, ACM Transactions on Software Engineering and Methodology (TOSEM), v.2 n.3, p.286-303, July 1993 [doi>10.1145/152388.152392]
• 98: Jeffrey S. Poulin, Integrated support for software reuse in Computer-Aided Software Engineering (CASE), ACM SIGSOFT Software Engineering Notes, v.18 n.4, p.75-82, Oct. 1993 [doi>10.1145/163626.163637]
• 99: R. Prieto-Diaz. A Software Classification Scheme. Technical Report 85-19, Department of Information and Computer Science, University of California, Irvine, 1985.
• 100: R. Prieto-Diaz, Implementing faceted classification for software reuse ( experience report), Proceedings of the 12th international conference on Software engineering, p.300-304, March 26-30, 1990, Nice, France
• 101: R. Prieto-Diaz and P. Freeman. Classifying Software for Reusability. IEEE Software, 4(1):6-16, 1987.
• 102: Ruben Prieto-Diaz and William B. Frakes, editors. Advances in Software Reuse: Selected Papers from the Second International Workshop on Software Reusability, March 24-26, 1993, Lucca, Italy. IEEE Computer Society Press, 1993.
• 103: C. V. Ramamoorthy , Vijay Garg , Atul Prakash, Support for Reusability in Genesis, IEEE Transactions on Software Engineering, v.14 n.8, p.1145-1154, August 1988 [doi>10.1109/32.7625]
• 104: George E. Raymond , David M. Hollis, Software reuse economics model: Version 1.0, Proceedings of the eighth annual Washington Ada symposium & summer SIGAda meeting on Ada: software: foundation for competitveness, p.141-155, June 17-21, 1991, McLean, Virginia, United States [doi>10.1145/134494.134508]
• 105: Charles Rich , Richard C. Waters, Automatic Programming: Myths and Prospects, Computer, v.21 n.8, p.40-51, August 1988 [doi>10.1109/2.75]
• 106: Neil W. Rickert, Preconditions for widespread reuse of code, ACM SIGSOFT Software Engineering Notes, v.11 n.2, p.21, April 1986 [doi>10.1145/382248.382814]
• 107: A.J. Rockmore. Knowledge-Based Software Turns Specifications into Efficient Programs. Electron. Des.(USA), 33(17):105-12, July 1985.
• 108: P. Saugstadt and K. Raaheim. Problem-Solving, Past Experience and Availability of Functions. in Wason and Johnson-Laird {122}, chapter 5.
• 109: M.E. Sime, A.T. Arblaster, and T.R.G. Green. Structuring the programmer's task. In Bill Curtis, editor, Tutorial: Human Factors in Software Development (second edition), pages 453--464. IEEE Computer Society Press/North-Holland, 1986.
• 110: K. Soloway and E. Ehrlich. Empirical Studies of Programming Knowledge. IEEE Transactions on Software Engineering, 10(5):595-609, September 1984.
• 111: L.S. SCrumgfird, G. Sindre, and F. Stokke. Experiences from Application of a Faceted Classification Scheme. In Prieto-Diaz and Frakes { 102}, pages 116- 124.
• 112: R. St.-Dennis. A Guidebook for Writing Reusable Source Code in Ada. Technical Report CSC-86- 3:8213, Computer Science Center, Honeywell Inc., 1000 Boone Avenue North, Golden Valley, Minnesota 55427, 1986.
• 113: T.A. Standish. An Essay on Software Reuse. IEEE Transactions on Software Engineering, 10(5):494- 497, September 1984.
• 114: Werner Staringer, Constructing Applications from Reusable Components, IEEE Software, v.11 n.5, p.61-68, September 1994 [doi>10.1109/52.311062]
• 115: Proceedings of the Ada-Europe International Conference on Ada-components: libraries and tools, November 1987
• 116: W. M. Thomas , A. Delis , V. R. Basili, An evaluation of Ada source code reuse, Proceedings of the 11th Ada-Europe international conference on Ada: moving towards 2000, p.80-91, January 1992, Zandvoort, The Netherlands
• 117: W. Tracz. Software Reuse: Motivators and Inhibitors. In Michael {92}, pages 358-363.
• 118: Will Tracz, Software reuse: emerging technology, IEEE Computer Society Press, Los Alamitos, CA, 1988
• 119: W. Tracz. LILEANNA: A Parameterized Programming Language. In Prieto-Diaz and Frakes {102}, pages 66-78.
• 120: F. Ververs, J. van Katwijk, and L. Dusink. Directions in Reusing Software. Technical Report TR 88-58, Faculty of Mathematics and Informatics, TU Delft, The Netherlands, 1988.
• 121: Proc. of the Ada-Europe international conference on Ada: managing the transition, July 1986
• 122: P.C. Wason and P.N. Johnson-Laird, editors. Thinking and Reasoning, Selected Readings. Penguin Modern Psychology. Penguin Books, 1968.
• 123: W. Wong, A management overview of software reuse, U.S. Department of Commerce, 1986
• 124: S.N. Woodfield, D.W. Embley, and D.T Scott. Can Programmers Reuse Software? IEEE Software, 4(4):52-59, July 1987.
• 125: R.T Yeh, N. Roussopoulos, and B. Chu. Management of reusable software. In COMPCON'84 {34}, pages 311-320.

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.m Miscellaneous
          Subjects: Reusable software**

General Terms:
Theory