Scrapheap Software Development: Lessons from an Experiment on Opportunistic Reuse

In this paper a set of 10 guidelines for opportunistic software reuse is discussed. These guidelines are based on observations of nine systems developed entirely with scraps of functionality scavenged from abandoned projects.

[1]  Capers Jones,et al.  Why software fails , 1996 .

[2]  David Lorge Parnas,et al.  On the Design and Development of Program Families , 2001, IEEE Transactions on Software Engineering.

[3]  William B. Frakes,et al.  Software reuse research: status and future , 2005, IEEE Transactions on Software Engineering.

[4]  Sajjan G. Shiva,et al.  Software Reuse: Research and Practice , 2007, Fourth International Conference on Information Technology (ITNG'07).

[5]  Maurizio Morisio,et al.  Success and Failure Factors in Software Reuse , 2002, IEEE Trans. Software Eng..

[6]  L. Wood,et al.  From the Authors , 2003, European Respiratory Journal.

[7]  Arun Sen,et al.  The Role of Opportunism in the Software Design Reuse Process , 1997, IEEE Trans. Software Eng..

[8]  NcubeCornelius,et al.  Opportunistic Software Systems Development , 2008 .

[9]  Cornelius Ncube,et al.  Opportunistic Software Systems Development: Making Systems from What's Available , 2008, IEEE Software.

[10]  Slinger Jansen,et al.  Pragmatic and Opportunistic Reuse in Innovative Start-up Companies , 2008, IEEE Software.

[11]  R.N. Charette,et al.  Why software fails [software failure] , 2005, IEEE Spectrum.

[12]  James M. Neighbors,et al.  The Draco Approach to Constructing Software from Reusable Components , 1984, IEEE Transactions on Software Engineering.