Difference between revisions of "Form:Use Case Definition"
Jump to navigation
Jump to search
Megankatsumi (talk | contribs) |
Megankatsumi (talk | contribs) |
||
| Line 12: | Line 12: | ||
{| class="formtable" | {| class="formtable" | ||
! Summary: | ! Summary: | ||
| − | | {{{field|Summary|input type=textarea|mandatory|maxlength=280|placeholder= | + | | {{{field|Summary|input type=textarea|mandatory|maxlength=280|placeholder=Short description (max 280 characters). |
| − | The summary should identify the goal and one or more value proposition(s) in the form | + | The summary should identify the goal and one or more value proposition(s) in the form: «Verb» «direct object».}}} |
|- | |- | ||
! Description: | ! Description: | ||
| − | | {{{field| Description |input type=textarea|mandatory|placeholder= | + | | {{{field| Description |input type=textarea|mandatory|placeholder=A more extended description of the use case. It should provide sufficient context to provide insight into the data that needs to be exchanged and processed.}}} |
|- | |- | ||
! Actors: | ! Actors: | ||
| Line 22: | Line 22: | ||
|- | |- | ||
! Basic Flow of Events: | ! Basic Flow of Events: | ||
| − | | {{{field|Basic Flow of Events|input type=textarea|mandatory|placeholder= | + | | {{{field|Basic Flow of Events|input type=textarea|mandatory|placeholder=The sequence of events that occur during the normal flow of this use case with any notes.}}} |
|- | |- | ||
! Flow Exceptions: | ! Flow Exceptions: | ||
| − | | {{{field|Flow Exceptions|input type=textarea|placeholder= | + | | {{{field|Flow Exceptions|input type=textarea|placeholder=If applicable, highlighted alternative flow(s) of events that reveal the need for additional data to be exchanged among the actors of the use case.}}} |
|- | |- | ||
! Information Requirements: | ! Information Requirements: | ||
| − | | {{{field|Information Requirements|input type=textarea|placeholder= | + | | {{{field|Information Requirements|input type=textarea|placeholder=This is a very high-level description, for example, "origin location, destination location, and travel preferences". Details can be hashed out later and shown in the diagrams; this can be updated later to provide correspondence linkages to the defined data concepts in the Information View. While not technically required to define a use case, this field should be populated prior to beginning work on the data definitions.}}} |
|- | |- | ||
! Scenario Licensing: | ! Scenario Licensing: | ||
| Line 40: | Line 40: | ||
{{{for template|Supplementary Figures|label=Supplementary Figure(s)|multiple}}} | {{{for template|Supplementary Figures|label=Supplementary Figure(s)|multiple}}} | ||
| + | Include any figures needed to assist the user in better understanding the scenario. Any figures should be explained and referenced by either the description or the flow of events. | ||
{| class="formtable" | {| class="formtable" | ||
| − | ! Figure(s): | + | ! Figure(s): |
| {{{field|Figure|uploadable}}} | | {{{field|Figure|uploadable}}} | ||
| | | | ||
Revision as of 18:42, 12 April 2021
This is the "Use Case Definition" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page.