![[spacer]](/schemes/blue/line.gif){kind=small}
|
HW 13 by Sarah Kim-Warren 1. what do you consider the main message of the paper? Codebroker is designed, implemented, and evaluated to support software reuse. Generally, software reuse is not very practical with multiple users with much different background knowledge. Codebroker focuses on task-at-hand and an individual developer's background. 2. how is this work applicable to your own 2.1. work? My current job does not require coding or developing software, so this may not applicable for my work. But we have the knowledge repository where everyone stores information to share. 2.2. interests? Yes, definitely. The article and concepts are very interesting for future coding projects or jobs because this can be very practical. 3. do you have ideas how the work in the paper could or should be further developed? Not that I can think of at this time. 4. have you used any reuse libraries 4.1. if not: why not? Not really. I only created an additional (or re-written) libraries since the classes that I took didn't require much of coding. 4.2. if yes: which ones? did the libraries have any particular strengths and weaknesses? n/a 5. How does Codebroker infer the "task-at-hand"? Codebroker works with the comments and signature when a developer writes some code. It retrieves useful parts from the repository based on them. A user may do additional query based on the previous results that were most useful. 6. what are the trade-offs between 6.1. to let the systems infer the task-at-hand I think the systems infer the task-at-hand can be turn into the "help-clip wizard" in the Microsoft Word. It may not know what the user wants to do, but it may annoyingly prompt the user with non-useful info. 6.2. versus that the users specifies the task at hand? If a user knows what to specify for the task at hand, this would be very useful because the user will get the results back as he or she queried. |
