Difference between revisions of "Use Cases"

From Earth Science Information Partners (ESIP)
m
m
Line 3: Line 3:
 
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.   
 
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 examples of people using the Exchange to address areas societal need, and the other showing how the interface and underlying components work.  Eventually, it might be useful to construct the ESIP exchange using a collection of interrelated "reference models" as employed by the US Government following the sections of the Federal Enterprise 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.
 
+
<br><br>
[[Image:FEA Reference Models.jpg|center|px=100|]]
+
[[Image:FEA Reference Models.jpg|center|450px|]]
 
<center>Figure 1. Federal Enterprise Architecture Reference Models</center>
 
<center>Figure 1. Federal Enterprise Architecture Reference Models</center>
 
<br>
 
<br>
Line 15: Line 15:
 
:Mike Burnett presented the following diagrams:
 
:Mike Burnett presented the following diagrams:
  
::[[image:Burnett Components Diagram.PNG|center|]]
+
::[[image:Burnett Components Diagram.PNG|center|450px]]
  
  
 
==Applications Use Cases==
 
==Applications Use Cases==
  
It will be the scenarios that are created by each cluster that will drive the resource allocation.
+
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 b useful in desgning and evolving the Exchange.
  
 
==Systems Use Cases==
 
==Systems 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 diagrams of the Technical use cases.
+
::Detailed Visio diagrams of the System use cases.
 
:::[[Media:Use Case Realizations Michael Burnett.vsd|Use Case Overview]]
 
:::[[Media:Use Case Realizations Michael Burnett.vsd|Use Case Overview]]
  

Revision as of 06:47, July 22, 2006

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.

FEA Reference Models.jpg
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 diagrams:
Burnett Components Diagram.PNG


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 b useful in desgning and evolving the Exchange.

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