Client: David Stotts
Contractor: Bian Wu, Yuquan Jiang, Xiaosi Li, Zhu He
A powerful yet user-friendly meeting scheduling software system is needed for groups with limited meeting resources(individual people, rooms, equipment, etc.), such as Computer Science Department of UNC-CH. Currently, Microsoft Meeting Maker is used to perform such scheduling task. The limitation of Meeting maker is that a user can only use it within certain LAN. A user have to use a PC, intalled with Meeting Maker software, that connects to the server with resource information.
The goal of this project is to build a webbased meeting scheduler that can be used anywhere with web brower access(e.g, Dr.Scotts can travel to California, yet still use internet explorer to schedule a meeting with someone in our department.). Also this software has to be powerful enough to detect resource conflicts, propose possible solutions, and optimize resource allocation.
Our webbased meeting scheduler should be able to perform three major tasks:
Managing an individual schedule. If a person is needed for some meeting or appointment for certain time, check on his availablity and proposes solutions if conflicts happens Managing hardware resourses(rooms, equipment) so that no two meetings use the same one at the same time. Organizing larger meeting. Find a good time that all members have avvailable time and no hardware resource conflicts with other meetings
The party of Yuquan Jiang, Zhe Hu, Bian Wu, Xiaosi Li shall hereafter be collectively referred to as the contractor. The contractor hereby agrees to provide the client with functional software that meets the specifications defined under the heading "Primary Requirements". The contractor further agrees that this software shall be delivered to the client no later than May 8, 2000.
The contractor further agrees to provide the client with detailed documentation regarding the design, deployment and use of all software developed. This documentation will be delivered in both with the hard copy and soft copy to the client no later than May 8, 2000.
1. Web-based client-server architecture.
2. The client should be implemented as java applet.
3. Java servlet or application should be applied in server side implementation.
4. Implement the following functionalities:
Reserve room according to user requirement specified in the following terms: Time, Location, Size. Propose possible alternate when conflict occurs. If no alternate presents, arrange negotiation among conflicting parties with Email.
Meeting Time Scheduler
Schedule a time slot for meeting particants. Confirm success by sending email to all participants. If fail, arrange negotiation among all involved parties.
Schedule both time and room.
1. Certain security measure should be employed to protect clients
from unauthorized access.
2. Handle emergency situation when people change their schedule unexpectedly.
1. Provide a PC to serve as a server
2. Provide Microsoft Access database system and JDBC driver for that
3. Provide Visual Cafe as the software development evironment
1. Current scheduling algorithm is not optimized and the scheduler may not always produce the best solution for all conditions.