...
Also, as use cases are added in the categories listed below, please comment on or "like" ones as you see fit.
...
| 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 (A paragraph or two describing what happens) | 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)" |
Note to
...
VIVO Members
VIVO SponsorsMembers: Please add any additional use cases you might have on our Sponsor VIVO Member Use Cases page under the title of your organization, or feel free to comment on any of the use cases compiled below.
VIVO Use Case Template
- VIVO Use Case Template – please copy and fill in the table, adding any additional information such as screenshots, links, or examples that you find relevant
Categorized Use Cases
| Children Display |
|---|