...
Instructions for accessing and starting up our computer prototype
- Specify the platform and software requirements for your prototype.
- Give brief, step-by-step instructions for starting up your prototype. For web sites, a hyperlink to the site is sufficient.
- Describe which parts of the prototype are shallow (incompletely implemented or canned), so that your evaluators know what should work and what shouldn't.
- If your prototype must be downloaded, like a JAR or SWF file, put it in a place where it can be downloaded over the Web, and include a link to it in your wiki. All Athena users have a Public directory which is accessible by the URL http://web.mit.edu.ezproxy.canberra.edu.au/_username_/Public/.
- Your prototype must remain frozen (no changes) and accessible at this location for two weeks after the due date.
- Your prototype should be downloadable as a single file. Package multiple files into a ZIP archive for easy downloading.
...
Our prototype is web-based and can be found here: CalendarShare
Platform and Software Requirements:
Browser: Google Chrome 10
Resolution: 1280 x 800
Implementation Details
Fully implemented:
- Creating, editing, and deleting of events
- Creating, editing, and deleting of deadlines
- Creating, editing, and deleting notes
- Accurate calendar navigation with correct month layout and ability to select a particular day
- Event creation/editing forms that restrict user input to a valid range.
- There are no canned responses – everything is generated dynamically and saved as long as you don't navigate to a different month
Not implemented:
- We have not yet implemented an account management interface. Therefore, all users will see "Hello, Guest" in the corner along with "Log Out" text that is static.
- We have not yet implemented a visual representation for the backward propagation of deadlines. For example, if a user asks to be reminded about a deadline 7 days before it occurs, we would like to have a colored line on each of the 7 days before the deadline. This will be present once we have a backend.
- Persistency of calendar data. All events and deadlines that are created in a single month will be present in the application. When a user navigates to a different month, events and deadlines disappear. This will be fixed with a backend. Notes are persistent until a user refreshes the webpage. When a user refreshes the page, all data is lost. This will be fixed when we create a backend to store the user's calendar data with his/her account information.
Scope Reductions
Due to the loss of a group member, we eliminated the following some features of our design:.
1) CategoriesWe removed the notion of categories.
2) SharingWe removed the idea of sharing notes, events, and deadlines.
3) Printing
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
We have not implemented the login/account management stuff
We implemented adding, editing, deleting of event
There are no canned responses – everything is generated dynamically and saved as long as you don't reload a pageWe removed the ability to print the calendar within the application.