...
| Learnability | Efficiency | Safety |
|---|
Pros | - A visual interface, that allows users to select destinations on the map
- Direct manipulation of path on the map and direct manipulation of the scheduled events increase learnability
| - Suggested itinerary and suggested locations allow quick generation of itineraries
- Direct manipulation of the schedule allows uses to quick get the schedule to look the way they want
- Pre-populated constraints (ie hours of operation, visit duration) for each destination so the user doesn't need to look it up or input it
- This design can schedule multiple days at once so that destinations can be optimally clustered such that destinations that were located close to each other can be visited on the same day.
| - Destinations and constraints can be changed or deleted after they are created
|
Cons | - It is not obvious that the user can directly manipulate the generated schedule.
- What is a constraint? Is the concept understandable to people outside of CS?
| - Need to check off all the locations visited in order to reschedule
- Can not manually add locations that are not in the database
| - No way to undo a change
- Currently no way to save multiple itineraries
|
Design 2: Explore, select, and budget
After Kevin chooses where and when they are starting and ending the day (probably at wherever they are sleeping, possibly at a transport node), we then consider the problem to be one of choosing which "events" he wants to experience. An event has a location, a set of timespaces when it can occur, a minimum and maximum duration, and a location. "violin concerto" concert for example, will be located at the theater, could occur only from 7pm until 9pm and have both a minimum and maximum duration of 2 hours. "Visit to Uffizi" however, could occur from 9am until 6pm and have a minimum duration of 1 hour and a maximum duration of 3 hours.
...