Application UseCase Template

From Earth Science Information Partners (ESIP)
Revision as of 15:36, January 9, 2007 by Pfox (talk | contribs)

0.Use Case <Cluster>.<SubArea>.<number>.<letter>: <Short Name>[edit | edit source]

Use Case AQ.Smoke.1.a: Smoke plume event detection and related dataset discovery
<Cluster>={AQ, DM, EC, EF, PH, WM}
<number>={1, 2, 3, ...}
<letter>={a, b, c, ...}

0.1.Purpose[edit | edit source]

Earth Information Exchange

0.2.Revision Information[edit | edit source]

Version X.N.a (can be labeled draft if X=0)

Prepared by <Author(s) with responsibility>


<Date/Time created>

Revision History

Modified by <Modifier Name/Affil>, <Date/time>, <Brief Description>

1.Use Case Identification[edit | edit source]

1.1.Use Case Designation[edit | edit source]


1.2.Use Case Name[edit | edit source]

<Insert short name and long name>

2.Use Case Definition[edit | edit source]

First paragraph is short description, second paragraph, etc. may contain
further details.

Through this use case, the system User locates and identifies datasets (collections of related grandules) for use or processing. This process results in the User having access to a subset of the datasets in the portal that meet the requirements of the User. Individual datasets, and their constituent granules, may then be identified for further action or processing (e.g. Visualization, analysis, download).

2.1.Actors[edit | edit source]

Always identify primary actors, may be more than one. Also identify other actor
including any other systems or services which are important.

2.1.1.Primary Actors[edit | edit source]

The actor that initiates this use case is the portal User. Providers may also initiate this use case as a precursor to use case EIE05, Manage Collections/datasets.

2.1.2.Other Actors[edit | edit source]

2.2.Preconditions[edit | edit source]

  • 1.Collection metadata have been entered into the system
  • 2.Collection metadata have been validated
  • 3.Collection metadata have been published

2.3.Postconditions[edit | edit source]

  • 1.Datasets or granules have been identified within the system for further action
  • 2.Appropriate action (i.e. Map, download, process) controls have been provided to the user to initiate that action.
  • 3.Controls are provided to the user to refine the criteria used to 'discover' the dataset.

2.4.Normal Flow (Process Model)[edit | edit source]

  • 1)The user selects the 'dataset discovery' tool collection from the user interface
  • 2)The user performs a 'simple' search using a simple interface that searches commonly queries dataset attribute fields for matching text/terms.
  • 3)The results of the search are presented to the user with appropriate action controls associated with the datasets.
  • 4)The user selects one of the action controls to 'use' the identified dataset(s) in a specified action (i.e. Visualization, download, processing)

2.5.Alternative Flows[edit | edit source]

  • 1)The user selects the 'dataset discovery' tool collection from the user interface
  • 2)The user selects a control that provides access to an advanced search tool that supports spatial, temporal, and parametric search methods. Flow then extends to EIE11-EIE14.

2.6.Successful Outcomes[edit | edit source]

  • 1.Operation succeeds and user obtains QQQ.

2.7.Failure Outcomes[edit | edit source]

  • 1.Operation fails to return any XXX. Should instead YYYY.
  • 2.Illegal input of AAA, Should instead ZZZZ

2.8.Special Functional Requirements[edit | edit source]


2.9.Extension Points[edit | edit source]

  • <Cluster>.<SubArea>.<number>.<letter+1> something added or a variant.

E.g. AQ.Smoke.1.b something added or a variant

  • <Cluster>.<SubArea>.<number>.<letter+2> something added or a variant
  • <Cluster>.<SubArea>.<number>.<letter+3> something added or a variant

3.Diagrams[edit | edit source]

3.1.Use Case Diagram[edit | edit source]

3.2.State Diagram[edit | edit source]

3.3.Activity Diagram[edit | edit source]

3.4.Other Diagrams[edit | edit source]

4.Non-Functional Requirements[edit | edit source]

4.1.Performance[edit | edit source]

4.2.Reliability[edit | edit source]

4.3.Scalability[edit | edit source]

4.4.Usability[edit | edit source]

4.5.Security[edit | edit source]

4.6.Other Non-functional Requirements[edit | edit source]

5.Selected Technology[edit | edit source]

5.1.Overall Technical Approach[edit | edit source]

5.2.Architecture[edit | edit source]

5.3.Technology A[edit | edit source]

5.3.1.Description[edit | edit source]

5.3.2.Benefits[edit | edit source]

5.3.3.Limitations[edit | edit source]

5.4.Technology B[edit | edit source]

5.4.1.Description[edit | edit source]

5.4.2.Benefits[edit | edit source]

5.4.3.Limitations[edit | edit source]

6.References[edit | edit source]