1.2. System Personnel

The personnel involved in the Scheduler Tool Project can be categorized as follows:

a. end users
i. Scheduling Administrator
ii. Teachers
iii. Students
b. facilities administration
c. system developers
d. system server administration
e. third-party observers and participants

End users are participants who engage in the schedule data collection and generation process. The scheduling administrator uses the Scheduling Tool to generate a final schedule for the department/university; if a particular user's preferences or feedback hinders schedule generation or does not comply with the department/university's schedule fairness policies, the Scheduling Administrator may alter such data as department/university policies allow. Teachers provide a set of preferences which the Scheduler Tool uses in its generation of personal and department/university-wide schedules and its calculation of a fairness value by which to examine the appropriateness of such schedules. Students do not receive a personal schedule, but nevertheless provide feedback for the generation of department/university-wide schedules and calculation of corresponding fairness values.

Primary system developers include those listed in the project-governance and work-breakdown sections found in this document. These personnel are responsible for the creation and maintenance of the actual Scheduler Tool and its processes.

Facilities administration consists of those who provide data on the facilities/rooms available in the schedule generation process. Their data is added to the Scheduler tool by the Scheduling Administrator.

System server administration consists of those who store and protect data created by the the Scheduler Tool on system servers, such as saved preferences, saved schedules, and user management files.

Third-party observers and participants include those who are indirectly affected by the use of the scheduling tool, investors, outside comment and suggestion generators, and those with legal interest in the Scheduler Tool and its processes.




Prev: problem | Next: setting | Up: intro | Top: index