Software Requirements
A standard web browser preferably Google Chrome.
Links
Shallow Features
Feature |
Description |
---|---|
Populating map with venues |
Currently a static map for specific route, Boston to New York. The venues are not populating |
Calendar with venu availability |
Static and canned for the specific scenario |
Venue descriptions |
Pop up for names on the map that highlights the schedule, but no description is available |
Band schedule |
Not implemented |
3 Comments
Tanya M Kortz
Here is my evaluation . Please let me know if you have any questions!
Unknown User (zingales@mit.edu)
Giuseppe's evaluation.
Edward Oscar Benson
You're off to a long start but have some ground to make up for GR5 since GR4 doesn't fully implement the UI for the tasks you're trying to accomplish. The key elements of the UI are all there; their functioning needs to be polished so that they behave well according to the heuristics we've talked about in class. Nice coordination between the table and the map. You mentioned that you're doing a lot of canvas work for development -- you may find it easier to just use plain HTML and CSS. With the exception of the map (consider the GMap API?) everything on your page can probably be done much more easily with regular HTML, plus a bit of CSS and JS.
Comments below about bugs; I think we hit on all these in the meeting:
"Wiki presentation
: Very easy to use; clear instructions
Fidelity: Missing key functionality. Doesn't support completing tasks in the scenario (choosing time of concert, displaying full schedule)
Usability: * Need titles segmenting the two areas of the left-hand bar: the top controls control the route and the bottom controls filter the venues * No validation on dates (end date can come before start) * Alignment problems with map and table - they should be flush. You can probably use up a lot more horizontal space (expand with size of browser) here. * There seem to be some mode problems with yellow shading of the $$ buttons -- they get stuck yellow after selection. * Need to find a way to make dayticker schedule fit on the page. Since it is mostly empty, why not just list the time slots available? (make sure to disable slots already scheduled) * Also, to book, the button just needs to be named ""Book"" or ""Book Concert"" or something -- not ""click"" since click is the implied semantics of a button. Redundant text above also not needed.
"