Incremental Software Reuse
Current reuse techniques disincentive their mass practice in software development organizations because of their large initial investments, the changes they required in ways of developing software, and their fragility in front of domain evolutions. We argue that the root of these problems is the poor resolution of retrieval techniques to identify candidate artifacts to utilize in new projects. We sketch an approach to reuse based on artifacts retrieval by content, which allows incremental adoption at low cost. The Incremental Reuse Method (IRM), founded on these principles, can solve the big problems of traditional reuse, allowing their application in all manner of organizations.
KeywordsClass Diagram Software Development Process Software Reuse Domain Evolution Reuse Process
Unable to display preview. Download preview PDF.
- 1.Desouza, K.C., Awazu, Y., Tiwana, A.: Four dynamics for bringing use back into software reuse. Communications of the ACM 49(1) (January 2006)Google Scholar
- 3.IEEE Std 610.12-1990. IEEE Standard Glossary of Software Engineering (1990)Google Scholar
- 4.Jacobson, I., Griss, M., Jonsson, P.: Software Reuse: Architecture, Process and Organization for Business Success. ACM Press, Addison Wesley (1997)Google Scholar
- 5.Llorens, J., Morato, J., Genova, G.: RSHP: An information representation model based on relationships. In: Damiani, E., Jain, L.C., Madravio, M. (eds.) Soft Computing in Software Engineering. Studies in Fuzziness and Soft Computing Series, vol. 159, pp. 221–253. Springer, Heidelberg (2004)Google Scholar