Differences

This shows you the differences between two versions of the page.

--- theproject [2010/11/29 19:24] – roumani
+++ theproject [2010/12/07 21:27] (current) – roumani
@@ Line 14: / Line 14: @@
 The system must support of the following use cases:
-  * User to login. Authenticates is done via htaccess
+  * User to login. Authentication done via htaccess
-  * User to view the current bookings of a selected resource
+  * User to view the current bookings of a selected resource and time
-  * User to book a reource, if available, at a specified time. Bookings can be done on the hour or on the half-hour for a duration that is a multiple of 30 min. You can assume that bookings do not span the midnight boundary.
+  * User to book a resource, if available, at a specified time. Bookings can be done on the hour or on the half-hour for a duration that is a multiple of 30 min. You can assume that bookings do not span the midnight boundary.
-  * User to make an iterated booking of a selected resource. In  such a booking, the user specifies the start and end dates, the start time, the duration, and the frequency. The frequency can be a given set of dates or selected from predefined classes, such as "Second Friday of Each Month" and "Every Monday".
+  * User to make a repeated booking of a selected resource. In  such a booking, the user specifies the start and end dates, the start time, the duration, and the frequency. The frequency can be a given set of dates or selected from predefined classes, such as "Second Friday of Each Month" and "Every Monday".
   * The "admin" user to add, edit, or delete a resource. Each resource has an ID, a location, and a description.
   * The "admin" user to delete bookings made by others. In that case, an email is auto-sent to them with a reason for the deletion.
 ===== Deliverables =====
@@ Line 34: / Line 33: @@
 ''http://red.cse.yorku.ca:4413''
-Use the manager's facility (password the same as your own tomcat). Your app will auto deploy. If it does not run properly then the likely cause is a hard-coded path. You can fix the problem and re-upload as many times as needed (before the deadline) but make sure you stop or undeploy your webapp before re-uploading. Please do not undeploy someone's else webapp!
+Use the Tomcat Manager facility (name/password the same as your own tomcat) to upload your war file. Your webapp will auto deploy. If it does not run properly then the likely cause is a hard-coded path. You can fix the problem and re-upload as many times as needed (before the deadline) but make sure you stop or undeploy your webapp before re-uploading. Please do not undeploy someone's else webapp!
 The report is meant to describe your execution of the project to someone who is familiar with the project, e.g. a fellow student who is also executing the same project and writing a similar report. Hence, the report should focus on your own experience and efforts, i.e. what you actually did, rather than on general description. It is expected to be very brief, to the point, and made up of //at most// ten pages of typed text and diagrams (excluding printouts and source listing).