Please copy this page and use it as a template for adding new VIVO use cases. For more background, see Wikipedia article on use case structure
| Element | Description (replace text below with your text) |
|---|---|
| Title (Goal) | A one-line summary with just enough detail to easily convey the primary purpose of the new feature or requirement |
| Primary Actor | Is 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 use cases may be broader than your immediate need, and may thereby attract greater buy-in from others |
| Scope | Indicate 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 |
| Level | Indicate 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 | Sometimes called a scenario, the story expresses the need motivating the use case in a way that provides context as well as desired outcome(s) – and may follow in more narrative form the pattern of this structure, as in, "As a (actor), I need to (describe the task) so that I can (benefit from the outcome)" |
Supplementary Content
Please then add additional diagrams, links, examples, narrative – whatever you think will help clarify your use case and make it more compelling to others.
