Software Reuse Risks
Laboratory 6
Revision 1
Trinity Software
CS 340 Group 3
February 27, 2000
Software Reuse Risks Laboratory 6
We all agree that everyone contributed fairly to this document and we all agree to its contents.
J.D. Jordan ______
Jermaine McDonald ______
David Click ______
Damian Slonneger ______
Contents
Elimination of Risks 0
Introduction of Risks 0
02/27/00 Trinity Software ii
Software Reuse Risks Laboratory 6
Elimination of Risks
The use of software reuse can help reduce, or even eliminate, problems that could arise in this project. The most obvious elimination code reuse presents is the need to code a particular piece of the software. Because we can use pre-coded software that accomplishes what we desire, more time could be spent on pieces of the software that must be coded from scratch. The reused code might be extremely hard to code, or at least very difficult to get working correctly. In this regard, reuse would help cut down on mistakes and other problems fresh code might introduce. The reused code could also be much cleaner and work much better than code we might write ourselves. Thus the program would run more efficiently and effectively with this reused code. The reuse of good code helps cut down on time spent coding and allows that time to be used more wisely.
Introduction of Risks
Software reuse could also introduce problems into our robot code. First, the code being reused might not integrate very easily into our code. This would cause us to have to tweak the reused code and might take more time than desired to incorporate it correctly. The code could also be buggy, meaning that it just doesn’t work well or efficiently. In this case, the code would need to be rewritten or reworked and again take up more time than preferred. Finally, the reused software just might not work at all. Again this would mean the code would need to be rewritten. In the end, if code reuse introduces problems, time will be a major factor in making the code work.
02/27/00 Trinity Software 3