R. Holibaugh
ABSTRACT
The Software Engineering Institute (SEI) is interested in identifying the costs and benefits of software reuse to the mission critical computer resource (MCCR) community. In fulfilling this role, we were faced with the need to investigate reuse without making a large investment. This paper examines where to start a reuse activity by describing our initial view of reuse, our decisions on where to begin, what lessons we learned, and finally, our current view.
The reuse life cycle described in our final view gives more insight on how and where to implement reuse. It defines the phases of a reuse life cycle that begin with business planning and shows their relationships. For each phase of the reuse life cycle, we give the goals, the outputs, and an approach for achieving the goals. Each organization that is interested in obtaining the benefits of reuse must evaluate reuse in terms of business goals and objectives. Once this evaluation has been made, the life cycle described in the paper provides one approach to achieving the benefits of reuse.
- 1.Basili, V., Selby, R., and Hutchens, D. "Experimentation in Software Engineering". IEEE Transactions on Software Engineering SE-12, 7 (July 1986), 733-743. Google Scholar
Digital Library
- 2.Biggersta~f, T, Reuse in Practice Workshop. Slides.Google Scholar
- 3.Brooks, F., et al. Report of the Defense Science Board Task Force on Military Software. Department of Defense, 1987.Google Scholar
- 4.Lanergan, R. and Grasso, C. "Software Engineering with Reusable Designs and Code". IEEE Transactions on Software Engineering SE-IO, 5 (September 1984), 498-501.Google ScholarDigital Library
- 5.McKay, C. A Model for Life Cycle Reusability in lnformarion and Software Engineering. Sixth Symposium on Empirical Foundations of Information and Software Sciences, Atlanta, Georgia, October 1988.Google Scholar
- 6.McNamara, D. Japanese Software Factories. Software Factory Forum, Pittsburgh, Pennsylvania, February 1986.Google Scholar
- 7.McNichoU, D. Common Ada Missile Packages. Tech. Rept. AFATL.-TR-85-93, Air Force Armament Laboratory, Eglin AFB, Florida, May 1986.Google Scholar
- 8.McNicholl, D., et al. Common Ada Missile Program--Phase 2. Tech. Rept. AFATL-TR-88-62, Air Force Armament Laboratory, Eglin AFB, Florida, November 1988.Google Scholar
- 9.Peterson, A., Kang, K., Holibaugh, R., and Cohen, S. Real- Time Scheduling with Reusable Requirements Templates and Statemate. Tech. Rept. SEI Technical Report in Preparation, Software Engineering Institute, Pittsburgh, Pennsylvania, 1989.Google Scholar
- 10.Sha, L. and Goodenough, J. Real-Time Scheduling Theory and Ada. Teeh. Rept. CMU/SEI-88-TR-33, DTIC ADA#205048, Software Engineering Institute, Pittsburgh, Pennsylvania, May 1988.Google Scholar
- 11.Shaw, M. Purpose and Varieties of Software Reuse. Slides.Google Scholar
Index Terms
- Reuse: where to begin and why
Recommendations
Software reuse
Software reuse is the process of creating software systems from existing software rather than building software systems from scratch. This simple yet powerful vision was introduced in 1968. Software reuse has, however, failed to become a standard ...
Viewpoint-centred reuse: bridging the gap between reusability and the needs of the reuser
The "Reuse without Reusers" SyndromeThe problems of low productivity, late delivery and poor software quality are, unfortunately, characteristic of the software industry (Horowitz and Munson 1989). Increasingly, software developers are looking towards ...
Reuse: the two concurrent life cycles paradigm
TRI-Ada '90: Proceedings of the conference on TRI-ADA '90Since its introduction, Ada has held out the promise of significant productivity gains resulting from the ability to reuse design and code components more effectively. However, these gains will not occur simply because of the powerful features of the ...
Comments