As outlined in the Functional Overviews found in Section 2, the DTScheduler is comprised of web-based, paned-window layout. Should users wish to see more than one window, the tool allows for multiple browser windows to be open at once. Each view provide a means to access a central server accessible through the Internet. This is required to allow teachers to update their preferences into the central repository for actual schedule creation.
Since the tool is accessible through the Internet, security and privileges had to be taken into consideration. Traffic between the browsers and server should be secure and login processed through the User Rights functionality of the tool.
Implementation of the views and model should be straight forward. The many of the views will directly match that of the underlying models (especially for Resources.) Some views in scheduling will require temporary, derived objects to be created. However, the main Schedule object will contain all persistent data about the schedule (including locked scheduled items.)
The controller logic (especially for Schedule Generation) will require some thought to ensure the "complete and fair" requirements are met in a timely manner. Due to the amount of processing required for the preference weighting, this task is not expected to be instantaneous.
Due to the web-based nature of this project, it would make sense for the developer to use a web-browser friendly and secure language with support to connect to a central server.