...
Design 2: Schedule-specific constraint solver
The big idea behind the second design is to pose the scheduling problem as a set of activities with constraints that behave like tags. This design isn't designed to look like a guide book, or a post-it note. Instead, it lets the user specify activities (in no particular order). Each activity can be tagged with an arbitrary number of constraints. The "Plan!" button takes all of the activities and schedules them to meet the constraints. By "Schedule" we mean that the activities are ordered and given specific start and end times. Routes on a map are also drawn up between each pair of time-adjacent activities.
We call this a "Schedule-specific constraint solver" because the interface lets the user pick from a list of schedule-specific constraints such as:
| Learnability | Efficiency | Safety |
|---|---|---|---|
Pros |
| ||
Cons |
|