1. ® © 2010 Open Geospatial Consortium, Inc. Use Cases for Geospatial Interoperability Presented to ICAN-Great Lakes Workshop on Coastal Web Atlas Madison WI, 13-15 September 2011 David Arctur, PhD Director, Interoperability Programs

2. OGC ® Objective Help participants understand how to develop a sound use case for networked Coastal Web Atlases (CWAs) –What is a use case? –How do they differ from a needs assessment or a return-on- investment study? –How would a use case address interoperability? –What are some use cases that could directly be applied for CWAs? © 2010 Open Geospatial Consortium, Inc.2

3. OGC ® 4. Deployment Plan 4. Deployment Plan 1. Scenarios 2. Enterprise Models 2. Enterprise Models 3. Engineering Design 3. Engineering Design Use Cases Component Types Information Objects Optimize Specify Project Definition: Use Cases in Context 3© 2010 Open Geospatial Consortium, Inc.

4. OGC ® What is a Use Case? A description of a task you want the system to perform – Read a sensor, populate a database, notify others Basis of all analysis and design – Start simple; expand with detail later Analysis of use cases yields data, interface, application Use cases can: – Capture existing work flows – Define new applications – Help understand alternative and pathological work flows A set of use cases informs and helps one to construct a needs assessment or return-on-investment study Transform Data Use Case 4© 2010 Open Geospatial Consortium, Inc.

5. OGC ® What is a Use Case? “A use case in software engineering and systems engineering is a description of a system’s behavior as it responds to a request that originates from outside of that system. In other words, a use case describes "who" can do "what" with the system in question. The use case technique is used to capture a system's behavioral requirements by detailing scenario-driven threads through the functional requirements..” adapted from Wikipedia, http://en.wikipedia.org/wiki/Use_case, Sept 2010 5© 2010 Open Geospatial Consortium, Inc.

6. OGC ® Use Case Diagram Show the actor/use case relationships – System architecture – Data flows, coordination Develop with users –During meetings, interviews –Post-it notes on whiteboard –Clean up and refine later Graphical notation is helpful, but the use case document is the most important artifact Some diagramming software: –Microsoft Visio (Win) –OmniGraffle Professional (Mac) –Sparx Enterprise Architect (Win/Linux) Operations & Maintenance Staff GIS Analyst Produce flood maps Manage flood control structures Document locations of flooding Emergency Call Center System boundary Actor and name Use case and name Geocode & map call list 6© 2010 Open Geospatial Consortium, Inc.

7. OGC ® Use Case Document Template Each use case is documented according to a template with these parts  –Note that Actors can be humans, systems, or system components Use Case Name, ID Description: Actors (initiators): Actors (receivers): Pre-conditions: Post-conditions: System components: Basic flow of events: - business rules - user actions, responses Exceptions: Alternates: 7© 2010 Open Geospatial Consortium, Inc.

8. OGC ® Lessons from GEOSS: Reusable Process for Deploying Scenarios GEOSS = Global Earth Observation System of Systems –Visit earthobservations.orgearthobservations.org –Scenarios are chosen to address various Societal Benefit Areas (SBAs): Disasters, Health, Energy, Climate, Water, Weather, Ecosystems, Agriculture, Biodiversity Engineering Use Cases support SBA Scenarios Scenarios: end user view of the value of GEOSS –Focused on topics of interest to a community –Occur in a geographic Area of Interest (AOI) –Steps in a scenario are Use Cases Use Cases: reusable service oriented architecture –Use cases for discovery, data access, etc –Utilize Interoperability Arrangements 8© 2010 Open Geospatial Consortium, Inc.

9. 9 GEOSS Architecture Implementation Pilot (AIP): Engineering Use Cases www.ogcnetwork.net/AIpilot

10. OGC ® AIP Engineering Use Cases 10© 2010 Open Geospatial Consortium, Inc. Plus new use cases for AIP-3 –Semantic mediation –Data access conditions –User management –Revision of geo-processing use case

11. OGC ® AIP Use Cases AIP engineering use cases are posted here: –http://sites.aip3.ogcnetwork.net/home/home/engineering-use-caseshttp://sites.aip3.ogcnetwork.net/home/home/engineering-use-cases Examples of societal benefit area (SBA) scenarios: –AIP-3 SBA Scenarios http://sites.aip3.ogcnetwork.net/home/homehttp://sites.aip3.ogcnetwork.net/home/home –Disaster Management Scenario http://sites.aip3.ogcnetwork.net/home/home/disaster- management/aip-3-disaster-management-scenario http://sites.aip3.ogcnetwork.net/home/home/disaster- management/aip-3-disaster-management-scenario –Drought Scenario http://sites.aip3.ogcnetwork.net/home/home/waterquality- drought/water-products/comprehensive-drought-index-1 http://sites.aip3.ogcnetwork.net/home/home/waterquality- drought/water-products/comprehensive-drought-index-1 © 2010 Open Geospatial Consortium, Inc.11

12. OGC ® AIP Engineering Use Cases (partial list) © 2010 Open Geospatial Consortium, Inc.12 BPW = Best Practice Wiki, http://wiki.ieee-earth.org/http://wiki.ieee-earth.org/ CSR = Components & Services Registry, http://geossregistries.info/http://geossregistries.info/ GCI = GEOSS Common Infrastructure

13. OGC ® Engineering Use Case Example © 2010 Open Geospatial Consortium, Inc.13

14. OGC ® SBA Scenario: Disaster Management © 2010 Open Geospatial Consortium, Inc.14

15. OGC ® Disaster Management Use Cases © 2010 Open Geospatial Consortium, Inc.15

16. OGC ® SBA Scenario: Drought Drought: an increasingly damaging phenomena –Growing population & agricultural stresses on surface & groundwater –Reduced snow and glacier reservoirs Complex phenomena –Defined across many time scales, impacting many economic sectors –Sea surface temperatures (SST), winds, land cover, many other factors Scenario objectives –Monitor & forecast drought indicators –Assess water and drought conditions and impacts –Plan for mitigation –Carry out response strategy –Consider and address multi-disciplinary and cross-border institutional communications and coordination 16 Source: GEOSS AIP-3 CFP © 2010 Open Geospatial Consortium, Inc.

17. OGC ® Drought Scenarios & Use Cases © 2010 Open Geospatial Consortium, Inc.17 Watch this space!

18. OGC ® Use Case Examples Water supply restriction decisions based on flow monitoring and forecast models Stakeholder access to drought-related water supply information Water quality and cholera prediction models Drought prediction and alert Drought and crop production monitoring Incorporate semantic mediation to support client access to several distributed registries needed for drought investigation © 2010 Open Geospatial Consortium, Inc.18 Source: GEOSS AIP-3 CFP

19. OGC ® Drought Scenario: Services and Components Sensor Observation Services Processing service (population) for modeling chains Visualization tools Data provenance registries Community catalog and registered services Moisture and weather observations (OGC Web Coverage Service; CF/netCDF) OPeNDAP service Crop prediction models © 2010 Open Geospatial Consortium, Inc.19 Source: GEOSS AIP-3 CFP

20. OGC ® Use Case: Drought Determination Title: Research staff tasked to forecast seasonal & annual precipitation, temperature, soil moisture, drought Use case steps (notional) –Research staff requests data from GEOSS and other portals –Research results show region will have severe drought –Assess physical and economic risks and impacts of drought, identify needed actions –Deliver services, assistance, mitigation (track results) –Notify related stakeholders regarding data and results 20© 2010 Open Geospatial Consortium, Inc. Source: GEOSS AIP-3 CFP

21. OGC ® Use Case: Semantic Mediation Title: Client access to several distributed registries to support user investigation of various ontologies, e.g., –User Requirements Registry –CEOS Database –DIAS Definitions –WMO definitions Use case steps (notional) –User enters a term of interest into mediation client –Mediation client access several ontologies in remote registries –Client displays subset of ontologies and allows for creation of links between terms –Linked ontologies used to find datasets of interest 21© 2010 Open Geospatial Consortium, Inc. Source: GEOSS AIP-3 CFP

22. OGC ® Interoperability Issues with Data Vocabularies, ontologies –Build in semantic mediation Differences in source and destination database schemas –Try to achieve a common community information model for as much of the schemas as possible Differences in data exchange encodings and metadata –Use data exchange standards, and community-agreed metadata Different or unknown coordinate reference systems –Be sure to identify and record with metadata the correct coordinate reference system, or its identifier in a standard registry (EPSG) –If needed, incorporate a coordinate transformation process into your workflow, or in the usage pattern for relevant web services Attempting to integrate data sets with different temporal scales or timeseries types –?? © 2010 Open Geospatial Consortium, Inc.22

23. OGC ® Interoperability Issues with Catalogues Spotty / uneven collection of metadata –Establish a template with agreed metadata fields and content examples, and enforce it through the catalog registration client Catalogues are not created or started properly –Incorporate the OGC TEAM Engine (test harness) into your OGC CSW catalogue publishing workflow, so that catalog instances are validated against industry standards before being allowed to stand up You’re using the standards in your data and services as adopted by the relevant Standards Organization, but it doesn’t meet your needs. –Be sure you’re using the standards as intended by the SDO and data provider. If appropriate, submit a Change Request for the features wanted, to the relevant standards organization © 2010 Open Geospatial Consortium, Inc.23

24. OGC ® Thanks!Qu estions? © 2010 Open Geospatial Consortium, Inc.24 Dr. David Arctur darctur@opengeospatial.org Open Geospatial Consortium http://www.opengeospatial.org