The personnel invlolved in the Grader Tool project are organized into the following groups:

a. end users
i. instructors, ii. teaching assistants iii. students iv. system administrators b. customers
c. system developer
d. domain experts
f. outside parties

Instructors, teaching assistants, students, and system administrators are the end users for the grader. Instructors create, edit, and post grade books. Teaching assistants enter scores, but are very limited in their ability to edit other information. Students fetch posted grades, review thier grades and predict needed scores. System adminstrators do not use the program directly but control the files for students and gradebooks.

The primary customer is Professor Fisher. He is customer representative for his faculty and staff colleagues in the Computer Science department at the California Polytechnic State University, San Luis Obispo. In this representative capacity, Professor Fisher will consult with other potential customers to gather requirements from them, and integrate their requirements with his own.

The primary system developer is team jSting. Their development activities are all those of the software development process, from requirements analysis through product implementation and deployment. They will also conduct the ongoing process activities of testing, configuration, documentation, and project management.

The domain experts are team jSting, Professor Fisher, and other faculty and students. Team jSting are experts in the student perspective of this project. Professor Fisher is an expert in the professor of this project.

The Grader is available as public domain software for use by outside parties. The project directory is located at http://users.csc.calpoly.edu/~tcasella/grader/.