![[spacer]](/schemes/blue/line.gif){kind=small}
Assignment 13SCOTT ZWEIG3/14/04 Questions in Relationship to Software Reuse and CodeBroker source: Ye, Y., & Fischer, G. (2002) "Supporting Reuse by Delivering Task-Relevant and Personalized Information." In Proceedings of 2002 International Conference on Software Engineering (ICSE'02), Orlando, FL, pp. 513-523. Available at: http://www.cs.colorado.edu/~gerhard/papers/icse2002.pdf. due: Monday, March 15, 2004 Briefly discuss the following issues:
The main message of this article is the idea for creating a system that would allow software developers to refer to an archive of previously written lines of code while they are designing new code. This so called "repository" of information will act kind of like training wheels, helping the designers by giving them meaningful suggestions and bits of code that might be relevant to their new design. Even though this is a very useful idea, it will be extremely difficult to develop this type of system.
Sometimes when I am writing a paper I will look back on and refer to an old paper that I might have written a year or two earlier. Even if the topics are not in the same ballpark, it is still sometimes helpful to read something old and look at it from a fresh, new angle.
If and when I am designing a website or a flash movie I will often look back to an older piece and (sometimes) I will reuse an action or a color scheme or something that I thought worked well in the past. When something is good and it works, stick with it.
Obviously the archive idea is a great one, although it might even be better applied to some other context (i.e. cooking, or teaching).
Like I mentioned before, I never throw anything away. And so my most frequent use of the archival system is probably with my old papers. (I have saved term papers, research papers and opinion papers and all the rest since high school).
|
