|WDC - Web Data Collector||
Web module to collect activity requirements. This module combines various data into one application, viz unit / staff / location, to provide greater ease of data entry. However it has a major drawback in that it cannot run at the same time as the main Enterprise application, thereby restricting ongoing work. Consequently it was used in the first year of the project but is not used in subsequent years.
|WRB||Web Room Booking - web module for booking rooms directly. This module allows University staff to make their own ad-hoc bookings. General release for a particular year to UTAS staff only occurs when the academic timetable for that year has been scheduled, in order to avoid room clashes, as teaching activities have priority over ad-hoc bookings.|
|SyllabusPlus Enterprise Timetabler ET||
Net based application deployed via a website for managing SyllabusPlus data and generating the Timetable. It comprises the following components:
|Enterprise Data Reference Data Manager EDRDM||
This manages the data, parameters, constraints and definitions which control the processing and scheduling within Syllabus Plus. The major components are:
|Scientia Web Server SWS||Web module to display the generated timetable to end users.|
Inbound feed of staff data so that lecturers can be allocated to teaching activities. The data here is incomplete, as casual staff are not available in the system - these staff members have to be entered manually into S+ as and when they are known.
|Handbook Course and Unit||
Inbound feed of unit offering information from which teaching activities can be generated. A unit offering comprises:
|SAS Course and Unit||Inbound feed of program structure information as to which unit offerings are required to meet specific course requirements so that those unit offerings can be timetabled clash free.|
Inbound feed of location information. This information includes:
|Student Timetable||Outbound feed of activity bookings so that they can be displayed on the Student Timetable. This feed actually populates tables in the TARA database, which in turn feeds the Student Timetable. It is done this way in order to use the pre-existing functionality in TARA.|
|MyMedia Service Bookings||Outbound feed of bookings that use Lectopia capabilities - uses the same feed and mechanism as the Student Timetable.|
|Tutorial Allocation System||Uses same source table as the Student Timetable.|