Abstract

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.