All viewing, adding, editing, and deleting commands must execute instantaneously, except for the time it takes to execute a schedule generation. This must be on the order of minutes.

The time to execute all administrative commands must be instantaneous, except for any delays due to network transmission of data from the central host.

In general, the performance of Scheduler commands that must access data across a network is subject to potential network delays. The Scheduler must transmit data as fast as is possible on any given network, but delays due to external network circumstances are beyond the control of the Scheduler.

There are no specific requirements for the allowable size of a schedule in terms of the number of scheduled items. The only restrictions are that rooms do not have more than one class per time block and that teachers are not scheduled for more than one class per time block.

The maximum expected sizes of the Scheduler databases are the following:

• User Database -- tens of records
• Teacher Database -- tens of records
• Class database -- hundreds of records
• Rooms database -- hundreds of records
• Attribute database -- hundreds to thousands of records

While there may be tens of registered users, the expected number of users connected to the Scheduler at any given time is on the order of ones, which should not cause any network or other performance delay.