Code reuse in object oriented software development has been common for some time. A recent study performed by the author revealed that while software developers in small Norwegian companies regard code reuse as important and useful, they are prone to perform ad-hoc reuse. This reduces the positive effects achieved through reuse, and although most of the developers wish to perform more systematic reuse, they do not know how to do this. This thesis aims to help amend this problem by developing a set of guidelines describing the process of making a plan for reuse. To develop the guidelines, a literature study was performed, followed by three phases of writing. Between the three phases of writing, two rounds of three feedback interviews were performed to elicit information on the usability and clarity of the guidelines. Each feedback interview was performed with a developer from a small Norwegian company at the developer's workplace. After each set of interviews, the guidelines were revised and improved. The final set of guidelines presented in this report was considered by the developers to be easily understandable and useful, but further work remains to make the guidelines complete; a set of examples of how the process could be performed is essential to help the developers make the leap from the theoretical descriptions of the guidelines to making their own plan for reuse.
| Identifer | oai:union.ndltd.org:UPSALLA1/oai:DiVA.org:ntnu-9253 |
| Date | January 2005 |
| Creators | Eriksen, Lisa Wold |
| Publisher | Norges teknisk-naturvitenskapelige universitet, Institutt for datateknikk og informasjonsvitenskap, Institutt for datateknikk og informasjonsvitenskap |
| Source Sets | DiVA Archive at Upsalla University |
| Language | English |
| Detected Language | English |
| Type | Student thesis, info:eu-repo/semantics/bachelorThesis, text |
| Format | application/pdf |
| Rights | info:eu-repo/semantics/openAccess |
Page generated in 0.0021 seconds