...
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.
From Vijay's email to us when Lyla dropped the class:Whatever you decide to do, please when you submit code or post a link on the Wiki,
add a short blurb outlining what scope reductions you make, and please confirm with me
before making your final decision on what to eliminate.
Our prototype is web-based and can be found here: CalendarShare
Platform and Software Requirements:
Browser: Google Chrome 10
Resolution: Maximized (tested at 1680x1050)
Implementation Details
Fully implemented:
- We implemented adding, editing, deleting of event
Incompletely implemented:
Not implemented:
- We have not yet implemented account management the login/account management stuff.
- Remembering your ....
...
- There are no canned responses – everything is generated dynamically and saved as long as you don't reload a page
Scope Reductions
Due to the loss of a group member, we eliminated some features of our design.
1) We removed the notion of categories.
2) We removed the idea of sharing notes, events, and deadlines.
3) We removed the ability to print the calendar within the application.