Versions Compared

Old Version 38

changes.mady.by.user Unknown User (d_chang@mit.edu)

Saved on

compared with

New Version 39

changes.mady.by.user Andrew M Farrell

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

 

Learnability

Efficiency

Safety

Pros

  • Visual interface, Selecting destinations on map
  • 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.

 

Cons

  • 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
  • No way to undo a change
  • Currently no way to save multiple itineraries

Design 3: 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.

<insert object model>

We first allow the user to explore the city in space and time and choose those events that interest him. He can search for events 

Design 2: Schedule-specific constraint solver

...