June 18^th, 2001 APT Visit Planner Meeting at 3:00pm in N310

Jesse, Ron, Andy, Chris, Karla, Rusty

Here are the definitions we've come up with to include with the requirements
• Observer Requirements:
  The requirements which observers place on observations to meet science goals.
• Observatory Restrictions:
  The restrictions which an observatory places on observations as a matter of policy or physical limitations
• Observation Constraint:
  An Observer Requirement or Observatory Restriction that constrains the circumstances under which a visit may be scheduled.
• Scheduling Constraint:
  Any Observation Constraint or combination of Observation Constraints that affects when a visit can or cannot schedule.
• Scheduling Windows:
  The periods of time that a visit can or cannot schedule due to scheduling constraints.
• Total Scheduling Windows:
  A set of scheduling windows that accounts for all scheduling constraints.
• Partial Scheduling Windows:
  A set of scheduling windows that takes into account a subset of scheduling constraints..
• Schedulable/Unschedulable Window:
  A period of time over which a visit can or cannot schedule.

I'm listing here various points mentioned in the meeting, then show the uses cases we actually thought out.

• It was brought out that APT should make the proposal preparation process more flexible so that user's can make their own way from tool to tool.
• There should be a concept that there is a minimal set of observation constraints to be able to compute schedulability windows as well as knowledge of the complete set of observation constraints which can affect scheduling.
• Do we want the Visit Planner to be a phase 1 tool?
• We should consider how does one build a proposal if starting with the Visit Planner.
• Should the Visit Planner be able to run standalone as the VTT does? Probably not since it is used specifically for proposal preparation and planning.
• Should the Visit Planner be able to support exploratory kinds of activities?
• We should use "use cases" to flush out the capabilities that we want the Visit Planner to have.
• The questions we would like to consider for each use case are:
  • Who Is Using the Visit Planner?
  • When Is the Visit Planner Being Used?
  • What are the inputs?
  • What are the outputs?
  • What actions will the user take on the input/output data?
• We came up with three use cases to start with today:
  • Most basic case:
    • Who: PI, PC
    • When: Late in Phase 2 Writing Process
    • Input: Full Phase 2 Proposal
    • Output: Satisfactory Result, Bar Graph, Diagnostics, Advice
    • What Action: Nothing, the user is done.

  • Same as previous case, but change Output and What Actions
    • Output: Unsatisfactory Result
    • What Actions:
      • Analyze output and input data.
      • Modify input data.
      • Iterate.

  • This time, PC only
    • Who: PC Only
    • What Actions: Analyze and contact PI to change proposal.

• Given a full phase 2 proposal as input, there's probably not much else that can be changed to make other useful use cases.
• Here is a list of other types of input to consider for making other use cases:
  • Input is nothing, ie, starting from scratch for a phase 1 proposal.
  • Input is nothing for a phase 2 proposal.
  • A partially completed phase 2 proposal.
  • A partially completed phase 1 proposal.
  • A full phase 1 proposal with a partialy completed phase 2 proposal.
  • [How about a full phase 1 proposal (analogous to the cases above for phase 2)]
• Here's an image of our uses cases on the white board
  http://ra.stsci.edu/apst/apt/apt-visit-planner/meetings/meeting-2001-06-18-use-cases.jpg

http://ra.stsci.edu/apst/apt/apt-visit-planner/

• Terms for anything that affects when a visit can schedule.
  • Observer Requirements (ObsvrReqs): The requirements which observers place on observations to meet science goals.
  • Observatory Restrictions (ObsryRns): The restrictions which an observatory places on observations as a matter of policy or physical limitations
  • Observation Constraint (ObsnCsnt): An Observer Requirement or Observatory Restriction that constrains the circumstances under which a visit may be scheduled.
  • Scheduling Constraint (SchedCnst): Any Observation Constraint or combination of Observations Constraints that affects when a vist can or cannot schedule.

• The timelines displayed in the DG that show when a visit can schedule or not schedule.
  • Suitability or Scheduling Windows: The periods of of time that a vist can or cannot schedule due to scheduling constraints.
  • Total Scheduling Windows: A set of scheduling windows that accounts for all scheduling constraints.
  • Specific Scheduling Windows: A set of scheduling windows that takes into account only a specific subset of scheduling constraints. [Was "Specific Scheduling Timeline."]

    [[Actually "specific" is a somewhat unspecific word. How about "Scheduling Constraint Timeline" or "Specific Constraint Timeline" for timelines that encompass a single constraint and "Partial Scheduling Timeline" for timelines built from a subset of constraints.]]

• Points on the DG timelines that show when a visit can or cannot schedule, ie, where there are black bars.
  • Scheduling Window: A period of time over which a visit can or cannot schedule. [Was "Scheduling Violation" and "Scheduling Success"]

  [[I'm wondering if the Spike terminology might be better. How about "suitable location" (Suitable time? Suitable point?) for a point where a visit can schedule and "unsuitable location (or time or point)" for a point where the visit cannot.

  Violation to me connotes that the observer has made some type of error, whereas success to me connotes a situation where the visit has actually been scheduled as opposed to a particular point on the timeline.]]

Ron's Cases

http://ra.stsci.edu/apst/apt/apt-visit-planner/requirements/use_cases/downescases.txt

Andy's Cases

http://ra.stsci.edu/apst/apt/apt-visit-planner/requirements/use_cases/gerbscases.txt

Chris's Cases

http://ra.stsci.edu/apst/apt/apt-visit-planner/requirements/use_cases/odeascases.txt

Karla's Cases

http://ra.stsci.edu/apst/apt/apt-visit-planner/requirements/use_cases/petersonscases.txt

Rusty's Cases

http://ra.stsci.edu/apst/apt/apt-visit-planner/requirements/use_cases/whitmanscases.html

Leslie's Cases

http://ra.stsci.edu/apst/apt/apt-visit-planner/requirements/use_cases/zimmermanscases.txt

http://ra.stsci.edu/apst/apt/apt-visit-planner/