Terrestrial_usecases

This is version 15. It is not the current version, and thus it cannot be edited.
[Back to current version]   [Restore this version]

Terrestrial usecases

The following are the Usecases the terrestrial working group discussed during the July 2007 REAP Requirements Workshop. The group also conducted some informal ranking of these. First, usescases were given a 1-3 importance ranking, with 1 being most important. Second, of those cases ranked 1, group members voted for a few they felt were most important or should be implemented first.

Use Case Name: Detached Execution

Use Case Name: Smart Reruns

Use Case Name: Optional archiving of intermediate derived datasets.

Use Case Name: Archive a complete end to end run ("publication ready archive")

Use Case Name: Database actor option: Snapshot

Use Case Name: Actor specific annotations (gui linked)

Use Case Name: Actor for Data-Merge for specific product

Use Case Name: Integrate database actors

Use Case Name: Event Notification Monitoring system

Use Case Name: Search through workflow for a certain type of actor

Use Case Name: Different workflow view

Use Case Name: Manage a group of model runs

Use Case Name: Workflows need to accommodate sub-workflows that operate at different frequencies

Use Case Name: Tutorial or Wizard for wrapping external programs

Use Case Name: Easily create and share workflows and actors

Use Case Name: Improve component search.

Use Case Name: facilitate peer review process

Use Case Name: Use Kepler as a teaching tool

Use Case Name: Ecological Actors

Use Case Name: FakeData Generator Actor(s)

Use Case Name: 3d plots

Use Case Name: Iterator wrapper actor

Use Case Name: Markov Chain Monte Carlo (mcmc)

Use Case Name: Breakpoints

Use Case Name: Debugging

Use Case Name: Improved error messages.

Use Case Name: Disable actors