Difference between revisions of "Use Cases"

From Earth Science Information Partners (ESIP)
m (insert TIWG info)
m (minor edits)
Line 1: Line 1:
 
Back To: [[Main Page]]
 
Back To: [[Main Page]]
 
==Overview==
 
==Overview==
Construction of the Earth Information Exchange will be driven by users of the Federation products and services as described in our [[Federation Documents]]The result will follow a component-based architecture.
+
Requirements for the Earth Information Exchange will be established by users. The first stage in this process is to establish user's "wish lists" by capturing scenarios of use in plain language as described by the users themselvesIn the next stage, domain experts expand this description into a more formal Use Case description that will drive the development of the Exchange.
  
The first stage in this process is to establish a few of the user's "wish lists" by capturing scenarios of use that they envision.  We have divided these 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.   
+
We are developing two types of use cases: one addressing areas of societal need, and the other showing the interface and underlying components that might be applied to address this need.   
  
 
[[Use Case Discussion]]
 
[[Use Case Discussion]]
  
==Applications Use Cases==
+
==Earth Science Solutions Use Cases==
  
It will be the scenarios that are created by each cluster that will drive resource allocations.  This page provides a point of access for the Use Cases under development by the ESDS Technology Infusion Working Group in support of ESIP Federation application area technology activities. Use cases of known data access and/or data production activities are needed to identify web services and chaining scenarios for future implementation. And may also provide reference use cases for the development of capabilities within the Earth Information Exchange or other Federation activities including proposals developed by Federation members.
+
Scenarios that capture opportunities to apply Earth science for public benefit will drive resource allocations.  For example, this page provides a point of access for the Use Cases under development by NASA's ESDS Technology Infusion Working Group in support of ESIP Federation application area technology activities. Use cases of known data access and/or data production activities are needed to identify web services and chaining scenarios for future implementation. And may also provide reference use cases for the development of capabilities within the Earth Information Exchange or other Federation activities including proposals developed by Federation members.
 
 
 
 
The Use Case template is available to copy from at: [[Application_UseCase_Template]]
 
  
 
* Use Case 1:  [[Use_Case_Template | Air Quality Use Case Example]]
 
* Use Case 1:  [[Use_Case_Template | Air Quality Use Case Example]]
 
   
 
   
 +
Information for authors of Solutions Use Cases: [[SolutionsUseCase_Entry]]
  
==Systems Use Cases==
+
==Technology Use Cases==
 
(currently only some of the use cases have been converted to Wiki format, the remainder are Word documents)
 
(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.
 
::Detailed Visio diagrams of the System use cases.

Revision as of 13:29, March 22, 2007

Back To: Main Page

Overview

Requirements for the Earth Information Exchange will be established by users. The first stage in this process is to establish user's "wish lists" by capturing scenarios of use in plain language as described by the users themselves. In the next stage, domain experts expand this description into a more formal Use Case description that will drive the development of the Exchange.

We are developing two types of use cases: one addressing areas of societal need, and the other showing the interface and underlying components that might be applied to address this need.

Use Case Discussion

Earth Science Solutions Use Cases

Scenarios that capture opportunities to apply Earth science for public benefit will drive resource allocations. For example, this page provides a point of access for the Use Cases under development by NASA's ESDS Technology Infusion Working Group in support of ESIP Federation application area technology activities. Use cases of known data access and/or data production activities are needed to identify web services and chaining scenarios for future implementation. And may also provide reference use cases for the development of capabilities within the Earth Information Exchange or other Federation activities including proposals developed by Federation members.

Information for authors of Solutions Use Cases: SolutionsUseCase_Entry

Technology 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 02: Personalize User Experience

Use Case 03: Manage Portal

Use Case 04: Provider Management

Use Case 05: Manage Datasets/Collections Catalog

Use Case 06: Manage Inventory

Use Case 07: Manage Services

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 13: Parametric Search for Data

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]]

Use Case 26: Plugin Management