https://wiki.esipfed.org/w/api.php?action=feedcontributions&user=65.105.49.70&feedformat=atomEarth Science Information Partners (ESIP) - User contributions [en]2024-03-28T12:05:55ZUser contributionsMediaWiki 1.35.14https://wiki.esipfed.org/w/index.php?title=Sensor_Web&diff=8156Sensor Web2007-04-19T21:32:24Z<p>65.105.49.70: </p>
<hr />
<div>The Sensor Web Subgroup has been established as part of the NASA Earth Science Data Systems Technology Infusion Working Group. The subgroup intends to align its activities with those of the Federation clusters and to participate in Federation meetings.<br />
<br />
==Sensor Web Meetings==<br />
<br />
===Telecon Schedule===<br />
<br />
TIWG Sensor Web telecon normally held on the 4th Tuesday at 2:00 pm Eastern<br />
<br />
===Telecon Notes===<br />
<br />
[http://www.sciencedatasystems.org/seeds/wg/infusion/sensorweb/Working%20Documents/Forms/AllItems.aspx?RootFolder=%2fseeds%2fwg%2finfusion%2fsensorweb%2fWorking%20Documents%2fTelecon%20Notes&View=%7bC0C8F832%2dD245%2d4C3B%2dB1B2%2dB9AD7BDFA6A1%7d TIWG Telecon Notes]<br />
<br />
===July ESIP Federation Meeting (July 17-20, 2007, Madison, WI)===<br />
<br />
[[Summer 2007 Session: Evaluating Sensor Webs for Earth Science Applications]]<br />
<br />
==Activities==<br />
<br />
===Candidate Activities===<br />
::Identifying common semantics for sensor web<br />
::Develop sensor web use cases<br />
::How to evaluate the effectiveness of sensor web<br />
::Approaches to cataloging and searching for sensor data<br />
::Establish and share data sets (metadata) to test and evaluate sensor webs<br />
::Software development and code sharing<br />
<br />
===Use Cases===<br />
<br />
Preamble needed to introduce role of general ESIP Use Cases to drive sensor web application<br />
development.<br />
<br />
:http://wiki.esipfed.org/index.php/Use_Cases<br />
<br />
==NASA Working Groups==<br />
*NASA Earth Science Data System Working Groups/ Technology Infusion Working Group/<br />
Sensor Web Subgroup :http://www.sciencedatasystems.org/seeds/wg/infusion/sensorweb/default.aspx</div>65.105.49.70https://wiki.esipfed.org/w/index.php?title=Sensor_Web&diff=8155Sensor Web2007-04-19T21:26:52Z<p>65.105.49.70: /* Telecon Schedule */</p>
<hr />
<div>==Sensor Web Meetings==<br />
<br />
===Telecon Schedule===<br />
<br />
TIWG Sensor Web telecon normally held on the 4th Tuesday at 2:00 pm Eastern<br />
<br />
===Telecon Notes===<br />
<br />
[http://www.sciencedatasystems.org/seeds/wg/infusion/sensorweb/Working%20Documents/Forms/AllItems.aspx?RootFolder=%2fseeds%2fwg%2finfusion%2fsensorweb%2fWorking%20Documents%2fTelecon%20Notes&View=%7bC0C8F832%2dD245%2d4C3B%2dB1B2%2dB9AD7BDFA6A1%7d TIWG Telecon Notes]<br />
<br />
===July ESIP Federation Meeting (July 17-20, 2007, Madison, WI)===<br />
<br />
[[Summer 2007 Session: Evaluating Sensor Webs for Earth Science Applications]]<br />
<br />
==Activities==<br />
<br />
===Candidate Activities===<br />
::Identifying common semantics for sensor web<br />
::Develop sensor web use cases<br />
::How to evaluate the effectiveness of sensor web<br />
::Approaches to cataloging and searching for sensor data<br />
::Establish and share data sets (metadata) to test and evaluate sensor webs<br />
::Software development and code sharing<br />
<br />
===Use Cases===<br />
<br />
Preamble needed to introduce role of general ESIP Use Cases to drive sensor web application<br />
development.<br />
<br />
:http://wiki.esipfed.org/index.php/Use_Cases<br />
<br />
==NASA Working Groups==<br />
*NASA Earth Science Data System Working Groups/ Technology Infusion Working Group/<br />
Sensor Web Subgroup :http://www.sciencedatasystems.org/seeds/wg/infusion/sensorweb/default.aspx</div>65.105.49.70https://wiki.esipfed.org/w/index.php?title=Sensor_Web&diff=8154Sensor Web2007-04-19T21:26:22Z<p>65.105.49.70: /* Telecon Notes */</p>
<hr />
<div>==Sensor Web Meetings==<br />
<br />
===Telecon Schedule===<br />
<br />
Normally help on the 4th Tuesday at 2:00 pm Eastern<br />
<br />
===Telecon Notes===<br />
<br />
[http://www.sciencedatasystems.org/seeds/wg/infusion/sensorweb/Working%20Documents/Forms/AllItems.aspx?RootFolder=%2fseeds%2fwg%2finfusion%2fsensorweb%2fWorking%20Documents%2fTelecon%20Notes&View=%7bC0C8F832%2dD245%2d4C3B%2dB1B2%2dB9AD7BDFA6A1%7d TIWG Telecon Notes]<br />
<br />
===July ESIP Federation Meeting (July 17-20, 2007, Madison, WI)===<br />
<br />
[[Summer 2007 Session: Evaluating Sensor Webs for Earth Science Applications]]<br />
<br />
==Activities==<br />
<br />
===Candidate Activities===<br />
::Identifying common semantics for sensor web<br />
::Develop sensor web use cases<br />
::How to evaluate the effectiveness of sensor web<br />
::Approaches to cataloging and searching for sensor data<br />
::Establish and share data sets (metadata) to test and evaluate sensor webs<br />
::Software development and code sharing<br />
<br />
===Use Cases===<br />
<br />
Preamble needed to introduce role of general ESIP Use Cases to drive sensor web application<br />
development.<br />
<br />
:http://wiki.esipfed.org/index.php/Use_Cases<br />
<br />
==NASA Working Groups==<br />
*NASA Earth Science Data System Working Groups/ Technology Infusion Working Group/<br />
Sensor Web Subgroup :http://www.sciencedatasystems.org/seeds/wg/infusion/sensorweb/default.aspx</div>65.105.49.70https://wiki.esipfed.org/w/index.php?title=Sensor_Web&diff=8148Sensor Web2007-04-19T19:43:05Z<p>65.105.49.70: /* Telecon Schedule */</p>
<hr />
<div>==Sensor Web Meetings==<br />
<br />
===Telecon Schedule===<br />
<br />
Normally help on the 4th Tuesday at 2:00 pm Eastern<br />
<br />
===Telecon Notes===<br />
<br />
===July ESIP Federation Meeting (July 17-20, 2007, Madison, WI)===<br />
<br />
[[Summer 2007 Session: Evaluating Sensor Webs for Earth Science Applications]]<br />
<br />
== Cluster Task Activities ==<br />
<br />
Candidate activities<br />
::Identifying common semantics for sensor web<br />
::Develop sensor web use cases<br />
::How to evaluate the effectiveness of sensor web<br />
::Approaches to cataloging and searching for sensor data<br />
::Establish and share data sets (metadata) to test and evaluate sensor webs<br />
::Software development and code sharing<br />
<br />
===Use Cases===<br />
<br />
Preamble needed to introduce role of general ESIP Use Cases to drive sensor web application<br />
development.<br />
<br />
:http://wiki.esipfed.org/index.php/Use_Cases<br />
<br />
===NASA Working Groups===<br />
*NASA Earth Science Data System Working Groups/ Technology Infusion Working Group/<br />
Sensor Web Subgroup :http://www.sciencedatasystems.org/seeds/wg/infusion/sensorweb/default.aspx</div>65.105.49.70https://wiki.esipfed.org/w/index.php?title=Sensor_Web&diff=8147Sensor Web2007-04-19T19:41:40Z<p>65.105.49.70: /* July ESIP Federation Meeting (July 17-20, 2007, Madison, WI) */</p>
<hr />
<div>==Sensor Web Meetings==<br />
<br />
===Telecon Schedule===<br />
<br />
===Telecon Notes===<br />
<br />
===July ESIP Federation Meeting (July 17-20, 2007, Madison, WI)===<br />
<br />
[[Summer 2007 Session: Evaluating Sensor Webs for Earth Science Applications]]<br />
<br />
== Cluster Task Activities ==<br />
<br />
Candidate activities<br />
::Identifying common semantics for sensor web<br />
::Develop sensor web use cases<br />
::How to evaluate the effectiveness of sensor web<br />
::Approaches to cataloging and searching for sensor data<br />
::Establish and share data sets (metadata) to test and evaluate sensor webs<br />
::Software development and code sharing<br />
<br />
===Use Cases===<br />
<br />
Preamble needed to introduce role of general ESIP Use Cases to drive sensor web application<br />
development.<br />
<br />
:http://wiki.esipfed.org/index.php/Use_Cases<br />
<br />
===NASA Working Groups===<br />
*NASA Earth Science Data System Working Groups/ Technology Infusion Working Group/<br />
Sensor Web Subgroup :http://www.sciencedatasystems.org/seeds/wg/infusion/sensorweb/default.aspx</div>65.105.49.70https://wiki.esipfed.org/w/index.php?title=Sensor_Web&diff=8146Sensor Web2007-04-19T19:40:12Z<p>65.105.49.70: </p>
<hr />
<div>==Sensor Web Meetings==<br />
<br />
===Telecon Schedule===<br />
<br />
===Telecon Notes===<br />
<br />
===July ESIP Federation Meeting (July 17-20, 2007, Madison, WI)===<br />
<br />
== Cluster Task Activities ==<br />
<br />
Candidate activities<br />
::Identifying common semantics for sensor web<br />
::Develop sensor web use cases<br />
::How to evaluate the effectiveness of sensor web<br />
::Approaches to cataloging and searching for sensor data<br />
::Establish and share data sets (metadata) to test and evaluate sensor webs<br />
::Software development and code sharing<br />
<br />
===Use Cases===<br />
<br />
Preamble needed to introduce role of general ESIP Use Cases to drive sensor web application<br />
development.<br />
<br />
:http://wiki.esipfed.org/index.php/Use_Cases<br />
<br />
===NASA Working Groups===<br />
*NASA Earth Science Data System Working Groups/ Technology Infusion Working Group/<br />
Sensor Web Subgroup :http://www.sciencedatasystems.org/seeds/wg/infusion/sensorweb/default.aspx</div>65.105.49.70https://wiki.esipfed.org/w/index.php?title=Main_Page&diff=8144Main Page2007-04-19T19:20:15Z<p>65.105.49.70: /* Federation Administration */</p>
<hr />
<div>==Societal Benefit Areas==<br />
[[Image:Silver Falls OR.JPG|left|Silver Falls, OR]]<br />
:[[Air Quality Cluster | Air Quality]]<br />
:[[Coastal Management]]<br />
:[[Disaster Management]]<br />
:[[Ecological Forecasting]]<br />
:[[Public Health]]<br />
:[[Water Management]]<br />
<br><br />
:[[Cluster tools]]<br />
<br />
<br />
==Federation Administration==<br />
<br />
*Meetings<br />
::[[July 2007 ESIP Federation Meeting, Madison, Wisconsin]]<br />
::[[January 2007 ESIP Federation Meeting, Portland, Oregon]]<br />
*Clusters<br />
::[[Web Services]]<br />
::[[Semantic Web]]<br />
::[[Sensor Web|Sensor Web (provisional)]]<br />
*Standing Committees<br />
::[[Products and Services]]<br />
::[[Interoperability and Technology|Information Technology and Interoperability]]<br />
::[[Commercial Development]]<br />
::[[Community Engagement]]<br />
::[[Education]]<br />
*Administrative Committees<br />
::[[Executive Committee]]<br />
::[[Constitution and Bylaws]]<br />
::[[Finance]]<br />
::[[Partnership]]<br />
*[[Federation Documents|Defining Documents]]<br />
<br />
==Earth Information Exchange==<br />
*[[Vision Document]]<br />
*[[Requirements]]<br />
::[[Use Cases]]<br />
::[[Informal Requirements Document]]<br />
*[[Architecture]]<br />
::[[Components]]<br />
::[[Interaction Diagrams]]<br />
::[[Validation]]<br />
*[[Planning]]<br />
*[[Portal Working Group]]</div>65.105.49.70https://wiki.esipfed.org/w/index.php?title=Application_Use_Cases&diff=7464Application Use Cases2007-03-01T22:27:08Z<p>65.105.49.70: </p>
<hr />
<div>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.<br />
<br />
The Use Case template is available to copy from at: [[Application_UseCase_Template]]<br />
<br />
An example Use Case is available at: [[Use_Case_Template | Air Quality Use Case Example]]<br />
<br />
* Use Case 1 (this entry would be replaced with a link to a separate document for a use case)<br />
* Use Case 2<br />
* ...<br />
<br />
----<br />
<br><br />
<center>(added by [[User:HowardBurrows|HowardBurrows]] 10:29, 7 February 2007 (EST))</center><br />
<br><br />
# I don't think we should use "TIWG" in page title. Maybe call it "Application Use Cases"? <br />
# Where should this appear? We started a section for Use Cases as part of the Exchange discussion (See architecture section at the bottom of the [[Main_Page|Main wiki page]]. <br />
# Here is a partial comparison of the document structure used for the previous cases with that proposed here:<br />
<br><br />
{| border="1" cellspacing="0" cellpadding="5" align="center"<br />
!New proposal<br />
!Previous example<br />
|- valign="top"<br />
|<br />
1 Use Case <Cluster>.<SubArea>.<number>.<letter>: <Short Name><br />
:1.1 Purpose<br />
:1.2 Revision Information<br />
:1.3 Use Case Identification<br />
::1.3.1 Use Case Designation<br />
::1.3.2 Use Case Name<br />
----<br />
:1.4 Use Case Definition<br />
::1.4.1 Actors<br />
:::1.4.1.1 Primary Actors<br />
:::1.4.1.2 Other Actors<br />
<br><br />
----<br />
::1.4.2 Preconditions<br />
::1.4.3 Postconditions<br />
::1.4.4 Normal Flow (Process Model)<br />
::1.4.5 Alternative Flows<br />
::1.4.6 Successful Outcomes<br />
::1.4.7 Failure Outcomes<br />
::1.4.8 Special Functional Requirements<br />
::1.4.9 Extension Points<br />
----<br />
:1.5 Diagrams<br />
::1.5.1 Use Case Diagram<br />
::1.5.2 State Diagram (optional)<br />
::1.5.3 Activity Diagram (optional)<br />
::1.5.4 Other Diagrams (optional)<br />
:1.6 Non-Functional Requirements (optional)<br />
::1.6.1 Performance<br />
::1.6.2 Reliability<br />
::1.6.3 Scalability<br />
::1.6.4 Usability<br />
::1.6.5 Security<br />
::1.6.6 Other Non-functional Requirements<br />
:1.7 Selected Technology<br />
::1.7.1 Overall Technical Approach<br />
::1.7.2 Architecture<br />
::1.7.3 Technology A<br />
:::1.7.3.1 Description<br />
:::1.7.3.2 Benefits<br />
:::1.7.3.3 Limitations<br />
::1.7.4 Technology B<br />
:::1.7.4.1 Description<br />
:::1.7.4.2 Benefits<br />
:::1.7.4.3 Limitations<br />
:1.8 References (optional)<br />
|<br />
<br><br><br><br />
1. Use Case Identification<br />
:1.1 Use Case Number<br />
:1.2 Use Case Name<br />
----<br />
2.Use Case Definition<br />
:2.1 Actors<br />
<br><br><br />
:2.2 Business Rules<br />
----<br />
:2.3 Preconditions<br />
:2.4 Normal Flow<br />
:2.5 Alternative Flows<br />
:2.6 Postconditions<br />
:2.7 Extension Points<br />
:2.8 Special Requirements<br />
<br><br><br />
----<br />
:2.9 Assumptions<br />
:2.10 Notes<br />
:2.11 Issues<br />
|-<br />
|}</div>65.105.49.70https://wiki.esipfed.org/w/index.php?title=Application_Use_Cases&diff=7463Application Use Cases2007-03-01T21:44:23Z<p>65.105.49.70: </p>
<hr />
<div>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.<br />
<br />
The Use Case template is available to copy from at: [[Application_UseCase_Template]]<br />
<br />
An example is Use Case available at: [[Use_Case_Template | Air Quality Use Case Example]]<br />
<br />
* Use Case 1 (this entry would be replaced with a link to a separate document for a use case)<br />
* Use Case 2<br />
* ...<br />
<br />
----<br />
<br><br />
<center>(added by [[User:HowardBurrows|HowardBurrows]] 10:29, 7 February 2007 (EST))</center><br />
<br><br />
# I don't think we should use "TIWG" in page title. Maybe call it "Application Use Cases"? <br />
# Where should this appear? We started a section for Use Cases as part of the Exchange discussion (See architecture section at the bottom of the [[Main_Page|Main wiki page]]. <br />
# Here is a partial comparison of the document structure used for the previous cases with that proposed here:<br />
<br><br />
{| border="1" cellspacing="0" cellpadding="5" align="center"<br />
!New proposal<br />
!Previous example<br />
|- valign="top"<br />
|<br />
1 Use Case <Cluster>.<SubArea>.<number>.<letter>: <Short Name><br />
:1.1 Purpose<br />
:1.2 Revision Information<br />
:1.3 Use Case Identification<br />
::1.3.1 Use Case Designation<br />
::1.3.2 Use Case Name<br />
----<br />
:1.4 Use Case Definition<br />
::1.4.1 Actors<br />
:::1.4.1.1 Primary Actors<br />
:::1.4.1.2 Other Actors<br />
<br><br />
----<br />
::1.4.2 Preconditions<br />
::1.4.3 Postconditions<br />
::1.4.4 Normal Flow (Process Model)<br />
::1.4.5 Alternative Flows<br />
::1.4.6 Successful Outcomes<br />
::1.4.7 Failure Outcomes<br />
::1.4.8 Special Functional Requirements<br />
::1.4.9 Extension Points<br />
----<br />
:1.5 Diagrams<br />
::1.5.1 Use Case Diagram<br />
::1.5.2 State Diagram (optional)<br />
::1.5.3 Activity Diagram (optional)<br />
::1.5.4 Other Diagrams (optional)<br />
:1.6 Non-Functional Requirements (optional)<br />
::1.6.1 Performance<br />
::1.6.2 Reliability<br />
::1.6.3 Scalability<br />
::1.6.4 Usability<br />
::1.6.5 Security<br />
::1.6.6 Other Non-functional Requirements<br />
:1.7 Selected Technology<br />
::1.7.1 Overall Technical Approach<br />
::1.7.2 Architecture<br />
::1.7.3 Technology A<br />
:::1.7.3.1 Description<br />
:::1.7.3.2 Benefits<br />
:::1.7.3.3 Limitations<br />
::1.7.4 Technology B<br />
:::1.7.4.1 Description<br />
:::1.7.4.2 Benefits<br />
:::1.7.4.3 Limitations<br />
:1.8 References (optional)<br />
|<br />
<br><br><br><br />
1. Use Case Identification<br />
:1.1 Use Case Number<br />
:1.2 Use Case Name<br />
----<br />
2.Use Case Definition<br />
:2.1 Actors<br />
<br><br><br />
:2.2 Business Rules<br />
----<br />
:2.3 Preconditions<br />
:2.4 Normal Flow<br />
:2.5 Alternative Flows<br />
:2.6 Postconditions<br />
:2.7 Extension Points<br />
:2.8 Special Requirements<br />
<br><br><br />
----<br />
:2.9 Assumptions<br />
:2.10 Notes<br />
:2.11 Issues<br />
|-<br />
|}</div>65.105.49.70https://wiki.esipfed.org/w/index.php?title=Application_Use_Cases&diff=7462Application Use Cases2007-03-01T21:22:49Z<p>65.105.49.70: </p>
<hr />
<div>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.<br />
<br />
The Use Case template is available to copy from at: [[Application_UseCase_Template]]<br />
<br />
An example is Use Case available at: [[Use_Case_Template | Air Quality Use Case]]<br />
<br />
* Use Case 1 (this entry would be replaced with a link to a separate document for a use case)<br />
* Use Case 2<br />
* ...<br />
<br />
----<br />
<br><br />
<center>(added by [[User:HowardBurrows|HowardBurrows]] 10:29, 7 February 2007 (EST))</center><br />
<br><br />
# I don't think we should use "TIWG" in page title. Maybe call it "Application Use Cases"? <br />
# Where should this appear? We started a section for Use Cases as part of the Exchange discussion (See architecture section at the bottom of the [[Main_Page|Main wiki page]]. <br />
# Here is a partial comparison of the document structure used for the previous cases with that proposed here:<br />
<br><br />
{| border="1" cellspacing="0" cellpadding="5" align="center"<br />
!New proposal<br />
!Previous example<br />
|- valign="top"<br />
|<br />
1 Use Case <Cluster>.<SubArea>.<number>.<letter>: <Short Name><br />
:1.1 Purpose<br />
:1.2 Revision Information<br />
:1.3 Use Case Identification<br />
::1.3.1 Use Case Designation<br />
::1.3.2 Use Case Name<br />
----<br />
:1.4 Use Case Definition<br />
::1.4.1 Actors<br />
:::1.4.1.1 Primary Actors<br />
:::1.4.1.2 Other Actors<br />
<br><br />
----<br />
::1.4.2 Preconditions<br />
::1.4.3 Postconditions<br />
::1.4.4 Normal Flow (Process Model)<br />
::1.4.5 Alternative Flows<br />
::1.4.6 Successful Outcomes<br />
::1.4.7 Failure Outcomes<br />
::1.4.8 Special Functional Requirements<br />
::1.4.9 Extension Points<br />
----<br />
:1.5 Diagrams<br />
::1.5.1 Use Case Diagram<br />
::1.5.2 State Diagram (optional)<br />
::1.5.3 Activity Diagram (optional)<br />
::1.5.4 Other Diagrams (optional)<br />
:1.6 Non-Functional Requirements (optional)<br />
::1.6.1 Performance<br />
::1.6.2 Reliability<br />
::1.6.3 Scalability<br />
::1.6.4 Usability<br />
::1.6.5 Security<br />
::1.6.6 Other Non-functional Requirements<br />
:1.7 Selected Technology<br />
::1.7.1 Overall Technical Approach<br />
::1.7.2 Architecture<br />
::1.7.3 Technology A<br />
:::1.7.3.1 Description<br />
:::1.7.3.2 Benefits<br />
:::1.7.3.3 Limitations<br />
::1.7.4 Technology B<br />
:::1.7.4.1 Description<br />
:::1.7.4.2 Benefits<br />
:::1.7.4.3 Limitations<br />
:1.8 References (optional)<br />
|<br />
<br><br><br><br />
1. Use Case Identification<br />
:1.1 Use Case Number<br />
:1.2 Use Case Name<br />
----<br />
2.Use Case Definition<br />
:2.1 Actors<br />
<br><br><br />
:2.2 Business Rules<br />
----<br />
:2.3 Preconditions<br />
:2.4 Normal Flow<br />
:2.5 Alternative Flows<br />
:2.6 Postconditions<br />
:2.7 Extension Points<br />
:2.8 Special Requirements<br />
<br><br><br />
----<br />
:2.9 Assumptions<br />
:2.10 Notes<br />
:2.11 Issues<br />
|-<br />
|}</div>65.105.49.70https://wiki.esipfed.org/w/index.php?title=Application_Use_Cases&diff=7461Application Use Cases2007-03-01T21:22:29Z<p>65.105.49.70: </p>
<hr />
<div>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.<br />
<br />
The Use Case template is available to copy from at: [[Application_UseCase_Template]]<br />
<br />
An example is available at: [[Use_Case_Template | Air Quality Use Case]]<br />
<br />
* Use Case 1 (this entry would be replaced with a link to a separate document for a use case)<br />
* Use Case 2<br />
* ...<br />
<br />
----<br />
<br><br />
<center>(added by [[User:HowardBurrows|HowardBurrows]] 10:29, 7 February 2007 (EST))</center><br />
<br><br />
# I don't think we should use "TIWG" in page title. Maybe call it "Application Use Cases"? <br />
# Where should this appear? We started a section for Use Cases as part of the Exchange discussion (See architecture section at the bottom of the [[Main_Page|Main wiki page]]. <br />
# Here is a partial comparison of the document structure used for the previous cases with that proposed here:<br />
<br><br />
{| border="1" cellspacing="0" cellpadding="5" align="center"<br />
!New proposal<br />
!Previous example<br />
|- valign="top"<br />
|<br />
1 Use Case <Cluster>.<SubArea>.<number>.<letter>: <Short Name><br />
:1.1 Purpose<br />
:1.2 Revision Information<br />
:1.3 Use Case Identification<br />
::1.3.1 Use Case Designation<br />
::1.3.2 Use Case Name<br />
----<br />
:1.4 Use Case Definition<br />
::1.4.1 Actors<br />
:::1.4.1.1 Primary Actors<br />
:::1.4.1.2 Other Actors<br />
<br><br />
----<br />
::1.4.2 Preconditions<br />
::1.4.3 Postconditions<br />
::1.4.4 Normal Flow (Process Model)<br />
::1.4.5 Alternative Flows<br />
::1.4.6 Successful Outcomes<br />
::1.4.7 Failure Outcomes<br />
::1.4.8 Special Functional Requirements<br />
::1.4.9 Extension Points<br />
----<br />
:1.5 Diagrams<br />
::1.5.1 Use Case Diagram<br />
::1.5.2 State Diagram (optional)<br />
::1.5.3 Activity Diagram (optional)<br />
::1.5.4 Other Diagrams (optional)<br />
:1.6 Non-Functional Requirements (optional)<br />
::1.6.1 Performance<br />
::1.6.2 Reliability<br />
::1.6.3 Scalability<br />
::1.6.4 Usability<br />
::1.6.5 Security<br />
::1.6.6 Other Non-functional Requirements<br />
:1.7 Selected Technology<br />
::1.7.1 Overall Technical Approach<br />
::1.7.2 Architecture<br />
::1.7.3 Technology A<br />
:::1.7.3.1 Description<br />
:::1.7.3.2 Benefits<br />
:::1.7.3.3 Limitations<br />
::1.7.4 Technology B<br />
:::1.7.4.1 Description<br />
:::1.7.4.2 Benefits<br />
:::1.7.4.3 Limitations<br />
:1.8 References (optional)<br />
|<br />
<br><br><br><br />
1. Use Case Identification<br />
:1.1 Use Case Number<br />
:1.2 Use Case Name<br />
----<br />
2.Use Case Definition<br />
:2.1 Actors<br />
<br><br><br />
:2.2 Business Rules<br />
----<br />
:2.3 Preconditions<br />
:2.4 Normal Flow<br />
:2.5 Alternative Flows<br />
:2.6 Postconditions<br />
:2.7 Extension Points<br />
:2.8 Special Requirements<br />
<br><br><br />
----<br />
:2.9 Assumptions<br />
:2.10 Notes<br />
:2.11 Issues<br />
|-<br />
|}</div>65.105.49.70https://wiki.esipfed.org/w/index.php?title=Application_Use_Cases&diff=7424Application Use Cases2007-02-27T20:36:13Z<p>65.105.49.70: </p>
<hr />
<div>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.<br />
<br />
The Use Case template is available to copy from at: [[Application_UseCase_Template]]<br />
<br />
* Use Case 1 (this entry would be replaced with a link to a separate document for a use case)<br />
* Use Case 2<br />
* ...<br />
<br />
----<br />
<br><br />
<center>(added by [[User:HowardBurrows|HowardBurrows]] 10:29, 7 February 2007 (EST))</center><br />
<br><br />
# I don't think we should use "TIWG" in page title. Maybe call it "Application Use Cases"? <br />
# Where should this appear? We started a section for Use Cases as part of the Exchange discussion (See architecture section at the bottom of the [[Main_Page|Main wiki page]]. <br />
# Here is a partial comparison of the document structure used for the previous cases with that proposed here:<br />
<br><br />
{| border="1" cellspacing="0" cellpadding="5" align="center"<br />
!New proposal<br />
!Previous example<br />
|- valign="top"<br />
|<br />
1 Use Case <Cluster>.<SubArea>.<number>.<letter>: <Short Name><br />
:1.1 Purpose<br />
:1.2 Revision Information<br />
:1.3 Use Case Identification<br />
::1.3.1 Use Case Designation<br />
::1.3.2 Use Case Name<br />
----<br />
:1.4 Use Case Definition<br />
::1.4.1 Actors<br />
:::1.4.1.1 Primary Actors<br />
:::1.4.1.2 Other Actors<br />
<br><br />
----<br />
::1.4.2 Preconditions<br />
::1.4.3 Postconditions<br />
::1.4.4 Normal Flow (Process Model)<br />
::1.4.5 Alternative Flows<br />
::1.4.6 Successful Outcomes<br />
::1.4.7 Failure Outcomes<br />
::1.4.8 Special Functional Requirements<br />
::1.4.9 Extension Points<br />
----<br />
:1.5 Diagrams<br />
::1.5.1 Use Case Diagram<br />
::1.5.2 State Diagram (optional)<br />
::1.5.3 Activity Diagram (optional)<br />
::1.5.4 Other Diagrams (optional)<br />
:1.6 Non-Functional Requirements (optional)<br />
::1.6.1 Performance<br />
::1.6.2 Reliability<br />
::1.6.3 Scalability<br />
::1.6.4 Usability<br />
::1.6.5 Security<br />
::1.6.6 Other Non-functional Requirements<br />
:1.7 Selected Technology<br />
::1.7.1 Overall Technical Approach<br />
::1.7.2 Architecture<br />
::1.7.3 Technology A<br />
:::1.7.3.1 Description<br />
:::1.7.3.2 Benefits<br />
:::1.7.3.3 Limitations<br />
::1.7.4 Technology B<br />
:::1.7.4.1 Description<br />
:::1.7.4.2 Benefits<br />
:::1.7.4.3 Limitations<br />
:1.8 References (optional)<br />
|<br />
<br><br><br><br />
1. Use Case Identification<br />
:1.1 Use Case Number<br />
:1.2 Use Case Name<br />
----<br />
2.Use Case Definition<br />
:2.1 Actors<br />
<br><br><br />
:2.2 Business Rules<br />
----<br />
:2.3 Preconditions<br />
:2.4 Normal Flow<br />
:2.5 Alternative Flows<br />
:2.6 Postconditions<br />
:2.7 Extension Points<br />
:2.8 Special Requirements<br />
<br><br><br />
----<br />
:2.9 Assumptions<br />
:2.10 Notes<br />
:2.11 Issues<br />
|-<br />
|}</div>65.105.49.70