Use Cases

Back To: Main Page

Overview

Construction of the Earth Information Exchange will be driven by the "business" of the Federation as described in our Federation Documents. The result will follow a component-based architecture.

We have divided the use cases into two sections, one showing use of the Exchange to address areas of societal need, and the other showing the interface and underlying components. Eventually, it might be useful to construct a collection of interrelated "reference models" as employed by the US Government following the sections of the Federal Enterprise Architecture.

Figure 1. Federal Enterprise Architecture Reference Models

The most important aspects of our development strategy are shown on the left and right of Figure 1.

Diagram

Mike Burnett presented the following diagram:

Applications Use Cases

It will be the scenarios that are created by each cluster that will drive the resource allocation. See the individual cluster pages at the top of the Main Page.

(These are just now coming under development in a way that will be useful in desgning and evolving the Exchange.)

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

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

for

Earth Information Exchange

Version X.N.a (can be labeled draft if X=0) Prepared by <Author(s) with responsibility> <Affiliation> <Date/Time created> Revision History Modified by <Modifier Name/Affil>, <Date/time>, <Brief Description>

1.Use Case Identification

1.1.Use Case Designation

<Cluster>.<SubArea>.<number>

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

2.1.Actors

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.2.Preconditions

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

2.3.Postconditions

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

• EIE09.0.1)The user selects the 'dataset discovery' tool collection from the user interface
• EIE09.0.2)The user performs a 'simple' search using a simple interface that searches commonly queries dataset attribute fields for matching text/terms.
• EIE09.0.3)The results of the search are presented to the user with appropriate action controls associated with the datasets.
• EIE09.0.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

• EIE09.1.1)The user selects the 'dataset discovery' tool collection from the user interface
• EIE09.1.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.7.Failure Outcomes

• 1.Search fails to return any datasets. The system should return a message indicating the failure to find any matching datasets and offer to perform another search, perhaps providing a pointer to search tips.
• 2.The search string provided is illegal (i.e. It contains illegal characters or elements, or is blank). The system should return a warning and notification that the requested search was not performed. A pointer to valid search string syntax should also be provided. Log the event.

2.8.Security/Policy Considerations

None

2.9.Special Requirements

None

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

6.References

None

Systems Use Cases

(currently only some of the use cases have been converted to Wiki format, the remainder are Word documents)

Detailed Visio diagrams of the System use cases.

Use Case Overview

Note: Download the Visio Viewer 2003 from Microsoft and view these diagrams in Explorer (if you don't have MS Visio).

Use Case 01: User Management

Use Case 03: Manage Portal

Use Case 04: Provider Management

Use Case 05: Manage Datasets/Collections Catalog

• Use Case --: Publish Service
• Use Case --: Activate Service
• Use Case --: Delete Service

Use Case 08: Manage Groups/Communities

Use Case 09: Dataset Discovery

Use Case 10: Service Discovery

Use Case 11: Spatial Search for Data

Use Case 12: Temporal Search for Data [[1]]

Use Case 14: Free Text Searching [[2]]

Use Case 15: Preview Dataset (metadata driven)

Use Case 16: Preview Granule (metadata driven)

Use Case 17: Online Access to Granules [[3]]

Use Case 18: Direct Access to Data [[4]]

Use Case 19: Present "Hot" Products [[5]]

Use Case 20: Manage Experts

Use Case 21: Collaborate with Other Users

Use Case 22: Subscribe to Data Availability [[6]]

Use Case 23: Notify Subscriber [[7]]

Use Case 24: Track Usage

Use Case 25: Access Visualization Tool [[8]]