This survey has expired!
Survey expiration date reached on 11/6/2000.
Your answer will not be recorded.
Create your own free survey now!
Click here to continue.

CodeWeb Evaluation Survey

Please answer all questions that apply to you.

Your feedback will have a major impact on the development of CodeWeb and similar tools (which will be done in an open source manner in the future).

PollCat Surveys   http://www.pollcat.com


1.   Please provide your name or an alias that is unlikely to be used by others. You can use the name/alias to provide additional answers/clarifications to the survey in the future.
name/alias

2.   I have looked at the CodeWeb data to see if it might be useful in KDE development.
neverfrequently

3.   I have tried to use CodeWeb data for actual KDE development.
neverfrequently

4.   I have found the CodeWeb data to be useful during actual KDE development.
neverfrequently

5.   I plan to check out future versions of CodeWeb data to see if it is potentially useful to me in KDE development.
neverfrequently

6.   I plan to use CodeWeb data in the future for KDE development.
neverfrequently

7.   I have read the CodeWeb documentation (e.g., help page, papers, and chapters).
strongly disagreestrongly agree

8.   I understand the purpose of the CodeWeb tool.
strongly disagreestrongly agree

9.   CodeWeb achieves this goal based on my experience.
strongly disagreestrongly agree

10.   CodeWeb's browsing metaphor (as opposed to say a querying approach like that used in search engines) is suitable for understanding library usage in existing applications.
strongly disagreestrongly agree

11.   This tool can be used by library developers to see how users have used the libraries in their applications.

Alternatively, it can be used also by application developers to learn to use the libraries by seeing how others have used them in the past.

I have used the Codeweb data mostly from...
library developer perspectiveapplication developer perspective

12.   I believe that a simpler tool that shows all application classes that use a particular library class would be sufficient for understanding library usage (by browsing the application class code that uses the library class); there is no need for reuse statistics or reuse patterns (if/then rules).
strongly disagreestrongly agree

13.   I believe that a simpler tool that shows reuse statistics and reuse patterns but doesn't provide access to the source code is sufficient; I rarely found myself needing to look at the source code corresponding to the reuse statistics/patterns.
strongly disagreestrongly agree

14.   I have found the Web pages generated by CodeWeb to be easy to browse and understand.
strongly disagreestrongly agree

15.   I have found the reuse tables to be useful.

(These tables show you which library classes are used more so than others in existing applications. This feature was dropped in the most recent release so you may not have seen it.)
strongly disagreestrongly agree

16.   I have found the the "similar classes" feature to be useful.

This feature was introduced in the latest release.
strongly disagreestrongly agree

17.   I have found the "reuse opportunities" feature to be useful. (This is the table which shows you the number of applications that use specific members of a particular class.)
strongly disagreestrongly agree

18.   I have found the reuse patterns to be useful. (These are the if/then rules that show you that usage of a particular class/member implies usage of another.)
strongly disagreestrongly agree

19.   I have found the CodeWeb data to be just as good as hand-written tutorials for learning to use the KDE libraries.
strongly disagreestrongly agree

20.   I have found that the CodeWeb data complements existing tutorials (e.g., better than looking at tutorials only).
strongly disagreestrongly agree

21.   I have found that looking at code in real-life applications is just as good as looking at toy examples (e.g., in tutorials or those that come with the library).
strongly disagreestrongly agree

22.   I have found that looking at code in real-life applications is better than looking at toy examples when learning to use a library.
strongly disagreestrongly agree

23.   I have mostly used...
library viewbothapplication view

24.   What did you use CodeWeb to do? Please be as specific as possible and refer to the features of the tool that you used. For example: I browsed the reuse patterns in library view to look at typical library usage and I also used the similar classes feature in application view to find similar code that other people wrote in their applications.
answer

25.   To what extent was the CodeWeb data useful for each task described in the previous question? What insight (if any) did CodeWeb yield?
answer

26.   List the most positive aspects of CodeWeb.
answer

27.   List the most negative aspects of CodeWeb.
answer

28.   How do you think CodeWeb could be improved to make the tool more useful to you?
answer

29.   What existing features of CodeWeb (if any) should be dropped all together?
answer

30.   What is your occupation (e.g., 3rd year CS student, professional software developer, etc.)?
answer

31.   How long have you been developing software (not necessarily for KDE)?
years

32.   Any other comments?

You can also comment on any preceding questions here.

If you need clarification on any of the questions, please make a note of it here. I can then post a reply on the kde-devel mailing list (or send you email if you provide your address). You can then use the same name/alias from question 1 to update the questionnaire in the future.
answer
PollCat Surveys   http://www.pollcat.com
Reset

Thank you for completing this survey!
Click 'Done' to register your response.

You will then be shown a summary of the questionnaire answers given by people so far. Bookmark the link if you would like to see updates to this summary in the future.
PollCat