The draft requirements will certainly not be implemented for the first release. Jesse will try to come up the subset that would be reasonable.
It wasn't clear if the original wording was expressing a requirement to provide more information than just identifying the observer requirements. Providing more detailed information will go along with the last of the high level requirements.
The high level requirements posted on the VP web page will be change to reflect this change.
These high level requirements will also be numbered in future versions of the requirements.
We discussed the issue of how to allow the user to exclude linked visits or choose subsets of visits to analyze or display. This arose partly because of conflict between requirements 00.1.1.2 and 00.2.3.5.
To exclude linked visits, the user will turn off the constraints that specify that the visits are linked.
This control would be useful if a visit has many linked visits, most of which are not a problem. In general, though, most proposals are not of this nature. Certainly, the default should be to process and display all visits in the current APT context.
However, we still need to figure a way for user's to select which visits to display. We could leave the visit selector in the control panel, but use it to control the display, not the processing. We could add a tool bar to the display panel to give some display and visit navigation control.
There was some concern that the word "Calender", particularly in the term Schedulability Windows Calender, might be confused with "flight calenders". We decided to just leave it the way it is unless someone later figures out better terminology.
To help next week's meeting move along, please send any concerns about the requirements to Jesse who will organize all input into an agenda so we can have a more focused discussion than we did today.
Chris will present a review of the requirements at an upcoming APT review. Between our schedules, the first week of September is when we can have a review ready.