You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

VIVO Use Cases Wanted!

The VIVO community is encouraged to add use cases in the format detailed below by creating a new sub-page from this wiki page. In order to ensure that the community's needs are reflected in the software, this input is critical.
Also, please review the existing use cases here and comment on or "like" ones as you see fit.

Use case structure (from Wikipedia):

Title (Goal)A one-line summary with just enough detail to easily convey the primary purpose of the new feature or requirement
Primary ActorIs this a use case for end users? the local VIVO site administrator? a developer? a data service consumer? Be specific but bear in mind that some tasks are shared needs
ScopeIndicate to the best of your knowledge whether this is a major or minor feature and whether it applies in your local context, for any VIVO installation, for aggregations of VIVO data, for the VIVO-ISF ontology, and/or for the technical platform underlying VIVO, called Vitro
LevelIndicate whether this use case is at a very high level (overall system), a feature overview summary, a feature description, an individual user task, or a subfunction
Story (A paragraph or two describing what happens)Sometimes called a scenario, the user story expresses the need embodied in the use case in a way that provides context and motivation as well as desired out comes – and can follow in more narrative form the pattern of the overall use case, as in "As a (actor), I need to (describe the task) so that I can (benefit from the outcome)

Note to Sponsors

VIVO Sponsors: Please add any additional use cases you might have on our Sponsor Use Cases page under the title of your organization, or feel free to comment on any of the use cases compiled below.

 Categorized Use Cases

  • No labels