Views Controlled Vocabularies use case submissions

JavaScript isn't enabled in your browser, so this file can't be opened. Enable and reload.

The goal of collecting use cases is to identify requirements for the vocabularies based on the needs of communities of potential users. Submitter scenarios describe how the submitters would like to use the controlled vocabularies, then specific requirements are extracted from the stories. Please note that submitted use cases will be made public. For examples, see https://github.com/tdwg/ac/blob/master/views/use-case-examples.md

Name of use case (a short descriptive label for the use case) *

Submitter (The name of the person submitting the use case) *

Submitter's institution (Affiliation of the submitter)

Goal (Brief summary of what is to be achieved) *

Anticipated users (Descriptive labels for actors in the scenario; can be human or software agents) *

Scenario (Story describing an example instance of the use case. Actors are imaginary instances of the types of anticipated users. In the story, describe what the actors do as they interact with the controlled vocabularies.) *

Requirements (If possible, summarize the necessary conditions placed upon the controlled vocabularies in order to achieve the goal. The requirements should be based on the given scenario.)

Submit

Clear form

Never submit passwords through Google Forms.

This content is neither created nor endorsed by Google. Report Abuse - Terms of Service - Privacy Policy

Forms