Appendix 7: Web Tools Used at UCSC 

The Web Services Committee has a Tools Subgroup comprised of Aaron Melgares, David Rosen, and  

Phillip Stark. There was some concern and reluctance that the purpose of the group was to 

recommend standard campus tools that would be enforced (Microsoft IIS web server instead of 

Apache, for example) but the group quickly refocused on reusable, customizable tools used to develop 

dynamic web sites. In April 2002, the Tools Subgroup asked Computing Coordinators and web 

application developers to provide information about tools they use to develop web applications for 

dynamic web sites. They asked these questions regarding CGI and middleware tools, as well as 

database platforms: 

Coordinator and Campus Web Application Developers Survey 

CGI/Middleware tools 

What tools do you use to develop web applications? (some examples: FileMaker, PHP, Perl, 

Cold Fusion): 

Database platform 

What is the back end data storage for your applications? (some examples: mySQL, FileMaker 

Pro, MS Access, Oracle): 

What operating systems do you use for middleware/database servers? For each web 

application you ve developed please provide the following info. If you have multiple 

applications, sharing just a sample of those you think others on campus might care about 

would be fine. 

Name of system: 

Purpose: 

Audience/who are users? 

Level of traffic/use: 

Number of hours to develop: 

Resources and staff that were required for development: 

Who is the primary contact for supporting this system? 

Could you share this system?  If so, what level of support would you be willing to provide? 

(some examples: I can t/won t share; they can download it but I can t provide any assistance; 

I can answer a few questions here and there; I ll help if/when I have time; I m willing to talk 

to people about what I did) 

The survey elicited responses from 11 web developers who support a variety of web tools. The tools 

inventory will be posted to the web in a searchable format in Summer, 2002. 

_________________________________________________________________________________

Web Services Committee 

Page 26 

May 28, 2002