Versions Compared

Old Version 39

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

Saved on

compared with

New Version 40

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

Saved on

Key

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

...

  1. You want to visit Florence.
  2. You want to wake up at 8am and go to bed at 10pm.
  3. You want to do the following activities throughout the day: eat breakfast/lunch/dinner, visit the dome, and go to the opera.
  4. Now, you want to visit tourist places in Florence *and want to do as little walking as possible.*  You want to visit the dome (at the piazza del duomo) at some point in the day for two hours; it doesn't matter when you go.  The dome opens at 10am and closes at 5pm.  You also want to go to the Medici chapel for a special opera showing that starts at exactly 3pm and lasts for 2 hours.

Reflection

TODO: Andrew


- There is a fundamental problem in that in order to tell what a medium can do, we need to do a nontrivial amount of implementation with it that does not really belong in front part of a development cycle. 

It seemed that the process of  

We concentrated very heavily on constraints in the beginning, where that involved more complexity than users were prepared to deal with, so we simplified that interface. We did not get a chance to prototype the exploration and picking of activities, which was more of a problem with users. This would not really have been predictable. 

That we spent a lot of time on an issue and the users didn't have problems with it may simply reflect that we succeeded in