Application UseCase Template

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

0.Use Case <Cluster>.<SubArea>.<number>.<letter>: <Short Name>

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, ...}


Earth Information Exchange

0.2.Revision Information

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

1.1.Use Case Designation


1.2.Use Case Name

<Insert short name and long name>

2.Use Case Definition

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).


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

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


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


  • 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)

  • 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

  • 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

  • 1.Operation succeeds and user obtains QQQ.

2.7.Failure Outcomes

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

2.8.Special Functional Requirements


2.9.Extension Points

  • <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.1.Use Case Diagram

3.2.State Diagram

3.3.Activity Diagram

3.4.Other Diagrams

4.Non-Functional Requirements






4.6.Other Non-functional Requirements

5.Selected Technology

5.1.Overall Technical Approach


5.3.Technology A




5.4.Technology B