09-09-2017, 02:36 PM
A university schedule is a temporary arrangement of a set of classes and classrooms in which all the restrictions given are satisfied. It has been known that the time schedule belongs to the class of problems called NP hard. This project introduces a practical algorithm of timing capable of effectively taking care of the strong and weak restrictions used in an automated timing system.
Rich Internet Applications (RIAs) are web applications that have the features and functionality of traditional desktop applications. RIAs typically transfer the processing required for the user interface to the web client, but maintain most of the data (ie maintaining program state, data, etc.) on the application server.
We have used Google Web Toolkit, which is the RIA framework, with the same purpose. Our project reduces the overhead on the client UI component rendering server and makes room for the processing time of the scheduler algorithm.
Our Timetabling algorithm is the main component of our project that produces the HTML-based weekly time sheet as the output. Our project takes several user inputs such as the teacher list, course list, semester list, site list, day list and Timeslot as well as various rules, facts and restrictions using the forms based on the web , which are stored in the XML based knowledge base.
This knowledge base serves as input to our Time Generator Algorithm that resides on the server machine. Both the GWT Client Side UI user code and our algorithm are written in JAVA, which makes our project platform stand alone. Other benefits of choosing these frameworks are explained in the back of the report with practically acceptable results.
The algorithm we have constructed fully utilizes our knowledge of theory topics, including programming methodology, data structure and algorithm design and analysis. The previous efforts that we have dedicated to learning these topics at that time helped us during the design and construction of our entire project, especially in our timing algorithm. After the completion of the testing of our schedule generator algorithm, we moved towards the front end design.
Our main goal was to build the Rich Internet Application (RIA). Why we chose RIA architecture is explained in detail in the next section along with our survey for various RIA architectures. Once the survey is complete, we chose Google's Web Toolkit (GWT) for RIA creation. This decision is made during our Requirement and Analysis phase and the GWT details are explained in that section
Rich internet applications (RIAs) are web applications that have the features and functionality of traditional desktop applications. RIAs typically transfer the processing required for the user interface to the web client, but maintain most of the data (ie maintaining program state, data, etc.) on the application server.
Rich Internet Applications (RIAs) are web applications that have the features and functionality of traditional desktop applications. RIAs typically transfer the processing required for the user interface to the web client, but maintain most of the data (ie maintaining program state, data, etc.) on the application server.
We have used Google Web Toolkit, which is the RIA framework, with the same purpose. Our project reduces the overhead on the client UI component rendering server and makes room for the processing time of the scheduler algorithm.
Our Timetabling algorithm is the main component of our project that produces the HTML-based weekly time sheet as the output. Our project takes several user inputs such as the teacher list, course list, semester list, site list, day list and Timeslot as well as various rules, facts and restrictions using the forms based on the web , which are stored in the XML based knowledge base.
This knowledge base serves as input to our Time Generator Algorithm that resides on the server machine. Both the GWT Client Side UI user code and our algorithm are written in JAVA, which makes our project platform stand alone. Other benefits of choosing these frameworks are explained in the back of the report with practically acceptable results.
The algorithm we have constructed fully utilizes our knowledge of theory topics, including programming methodology, data structure and algorithm design and analysis. The previous efforts that we have dedicated to learning these topics at that time helped us during the design and construction of our entire project, especially in our timing algorithm. After the completion of the testing of our schedule generator algorithm, we moved towards the front end design.
Our main goal was to build the Rich Internet Application (RIA). Why we chose RIA architecture is explained in detail in the next section along with our survey for various RIA architectures. Once the survey is complete, we chose Google's Web Toolkit (GWT) for RIA creation. This decision is made during our Requirement and Analysis phase and the GWT details are explained in that section
Rich internet applications (RIAs) are web applications that have the features and functionality of traditional desktop applications. RIAs typically transfer the processing required for the user interface to the web client, but maintain most of the data (ie maintaining program state, data, etc.) on the application server.