The Community for Technology Leaders
RSS Icon
Subscribe
Issue No.02 - March/April (2011 vol.28)
pp: 68-74
Gerald Kotonya , Lancaster University
Simon Lock , Lancaster University
John Mariani , Lancaster University
ABSTRACT
Many organizations implicitly rely on opportunistic reuse as a low-cost mechanism for extending existing software systems and exploring new product ideas. Such strategies are also commonly used as an informal way to introduce and promote reuse in organizations that may not have the resources to set up systematic reuse programs. Scrapheap software development is a form of opportunistic reuse that emphasizes scavenging reusable functionality from discarded software projects and systems. A study that examined a microcosm of scrapheap software development derives generalizable and transferable lessons to inform its use in different development contexts.
INDEX TERMS
Software engineering, opportunistic reuse, scrapheap development, component-based development
CITATION
Gerald Kotonya, Simon Lock, John Mariani, "Scrapheap Software Development: Lessons from an Experiment on Opportunistic Reuse", IEEE Software, vol.28, no. 2, pp. 68-74, March/April 2011, doi:10.1109/MS.2010.59
REFERENCES
1. R.N. Charette, "Why Software Fails," IEEE Spectrum, vol. 42, no. 9, 2005, pp. 42–49.
2. C. Ncube, P. Oberndorf, and A.W. Kark, "Opportunistic Software Systems Development," IEEE Software, vol. 25, no. 6, 2008, pp. 38–41.
3. G. Kotonya, S. Lock, and J. Mariani, "Scrapheap Challenge: A Study of Developing Systems from Scrap Components," Proc. 11th Int'l Symp. Component-Based Software Eng. (CBSE 08), LNCS 5282, Springer, 2008, pp. 302–309.
11 ms
(Ver 2.0)

Marketing Automation Platform Marketing Automation Tool