Pros | | - Each activity can be specified with a minimum number of constraints. For example, if the user doesn't specify a duration for an activity (see snapshot 2) but does specify a "do this between X and Y time" constraint, the scheduler will interpret this as "make sure there is *some* break between time X and Y.
| - The "save" button snapshots the schedule at any point with any name that the user specifies. Once saved, the user can go back to any part of the schedule making process and make changes.
- Once the user clicks "Plan!", he/she can make manual changes to the generated schedule.
|
Cons | - The interface doesn't follow a specific metaphor (such as guidebook or post-it note) because it was designed to be multi-purpose---one can plan errands or day trips with it.
- What is a constraint? Is the concept understandable to people outside of CS?
| - Common constraints (such as activity duration/location) are not specified by default. Common activities (breakfast, lunch, dinner) must be added to the schedule every time they are needed.
| - The save button is only shown on panel 11
- If an activity or constraint is deleted, there is no "undo."
- If the user decides to re-plan (take the "woke up late" scenario for example) after making manual changes to the generated schedule, the manual changes are discarded.
- If the user under-specifies constraints (to save time), he/she might be surprized by what the scheduler generates (see "Pros, Efficiency").
|