Visit Planner Design Review Notes (October 30^th, 2001)

• Consider how to make all data returned from Spike available to the user.
• Display description information that Spike returns associated with both the visit and constraint scheduling windows.
• Change the SchedulingUnit interface to be called VpVisit. This means changing all the APT data model classes that Gary had implement SchedulingUnit.
• I should check out the design details in the DG for displaying Spike output. There is a TCL UML tool which can help with this.
• We talked about the RPS2 behavior of displaying only those constraints which affect schedulability. But, we're not going to worry about doing that in the Visit Planner since there isn't the same concern for real estate since the various tools are displayed separately.