U C f G l i tUse Cases for Geospatial Interoperabilitymaps.aqua.wisc.edu/ican/ican-gl-tuesday-arctur1.pdf · – Disaster Management Scenario ... (SST), winds, land cover, many other

®

U C f G ti l U C f G ti l Use Cases for Geospatial Use Cases for Geospatial InteroperabilityInteroperability

Presented to ICAN-Great Lakes Workshop on Coastal Web Atlas

Madison WI 13-15 September 2011Madison WI, 13 15 September 2011

David Arctur, PhDDirector Interoperability Programs

© 2010 Open Geospatial Consortium, Inc.© 2010 Open Geospatial Consortium, Inc.

Director, Interoperability Programs

ObjectiveObjective

• Help participants understand how to develop a sound use case for networked Coastal Web Atlases (CWAs)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?

OGC®

© 2010 Open Geospatial Consortium, Inc. 2

Project Definition: Use Cases in ContextProject Definition: Use Cases in Context

1. Scenarios

2.Enterprise

Models O ti iModels

3. E i i

Optimize

Engineering Design

Use Cases

Specify

4.Deployment

PlanComponent Types

Information Objects

OGC®

3© 2010 Open Geospatial Consortium, Inc.

What is a Use Case?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 dataUse Case

• Analysis of use cases yields data, interface, application

• Use cases can:

Transform Data

– Capture existing work flows– Define new applications

Help understand alternative– Help understand alternativeand pathological work flows

• A set of use cases informs and helps one to construct a

OGC®

needs assessment or return-on-investment study


What is a Use Case?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 ais 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 grequirements..”

adapted from Wikipedia http://en wikipedia org/wiki/Use case Sept 2010adapted from Wikipedia, http://en.wikipedia.org/wiki/Use_case, Sept 2010

OGC®


Use Case DiagramUse Case Diagram

• Show the actor/use case relationships

S t hit tManage flood

System boundary

– System architecture– Data flows, coordination

• Develop with usersOperations & Maintenance Produce

control structures

Develop with users– During meetings, interviews– Post-it notes on whiteboard– Clean up and refine later

StaffProduce

flood maps

Geocode & ll li t

• Graphical notation is helpful, but the use case documentis the most important artifact

GIS AnalystDocument

locations of

Emergency Call Center

map call list

is the most important artifact• Some diagramming software:

– Microsoft Visio (Win)– OmniGraffle Professional (Mac)

flooding

Actorand nameUse case

OGC®

– OmniGraffle Professional (Mac)– Sparx Enterprise Architect (Win/Linux)

and nameand name


Use Case Document TemplateUse Case Document Template

• Each use case is documented according to a template with Use Case Name, IDaccording to a template with these parts – Note that Actors can be

humans systems or

Description:Actors (initiators):Actors (receivers):Pre conditions:humans, systems, or

system componentsPre-conditions:Post-conditions:

System components:

Basic flow of events:- business rules- user actions, responses

Exceptions:Alternates:

OGC®


Lessons from GEOSS: Lessons from GEOSS: Reusable Process for Deploying ScenariosReusable Process for Deploying Scenarios

• GEOSS = Global Earth Observation System of Systems– Visit earthobservations.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

F d t i f i t t t it– 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

OGC®

– Utilize Interoperability Arrangements


GEOSS Architecture Implementation Pilot GEOSS Architecture Implementation Pilot (AIP): Engineering Use Cases(AIP): Engineering Use Cases

www.ogcnetwork.net/AIpilot


AIP Engineering Use CasesAIP Engineering Use Cases

• Plus new use cases for AIP-3– Semantic mediation– Data access conditions– User management– Revision of geo-processing use case

OGC®


AIP Use CasesAIP 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 S i htt // it i 3 t k t/h /h– AIP-3 SBA Scenarios http://sites.aip3.ogcnetwork.net/home/home

– Disaster Management Scenario htt // it i 3 t k t/h /h /di thttp://sites.aip3.ogcnetwork.net/home/home/disaster-management/aip-3-disaster-management-scenario

D ht S i– Drought Scenario http://sites.aip3.ogcnetwork.net/home/home/waterquality-drought/water-products/comprehensive-drought-index-1

OGC®


AIP Engineering Use Cases (partial list)AIP Engineering Use Cases (partial list)

OGC®


BPW = Best Practice Wiki, http://wiki.ieee-earth.org/CSR = Components & Services Registry, http://geossregistries.info/GCI = GEOSS Common Infrastructure

Engineering Use Case ExampleEngineering Use Case Example

OGC®


SBA Scenario: Disaster ManagementSBA Scenario: Disaster Management

OGC®


Disaster Management Use CasesDisaster Management Use Cases

OGC®


SBA Scenario: DroughtSBA 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 sectorsy , p g y– Sea surface temperatures (SST), winds, land cover, many other factors

• Scenario objectives– Monitor & forecast drought indicatorsMonitor & forecast drought indicators– Assess water and drought conditions and impacts– Plan for mitigation– Carry out response strategyCarry out response strategy– Consider and address multi-disciplinary and cross-border institutional

communications and coordination

OGC®

16

Source: GEOSS AIP-3 CFP

© 2010 Open Geospatial Consortium, Inc.

Drought Scenarios & Use CasesDrought Scenarios & Use Cases

OGC®


Use Case ExamplesUse Case Examples

• Water supply restriction decisions based on flow monitoring and forecast modelsand forecast models

• Stakeholder access to drought-related water supply information

• Water quality and cholera prediction models• Drought prediction and alert

D ht d d ti it i• Drought and crop production monitoring• Incorporate semantic mediation to support client access to

several distributed registries needed for droughtseveral distributed registries needed for drought investigation

OGC®



Drought Scenario: Services and Drought Scenario: Services and ComponentsComponents

• Sensor Observation Services• Processing service (population) for modeling chains• Processing service (population) for modeling chains• Visualization tools• Data provenance registriesData provenance registries• Community catalog and registered services• Moisture and weather observations (OGC Web Coverage

Service; CF/netCDF)• OPeNDAP service

C di ti d l• Crop prediction models

OGC®



Use Case: Drought DeterminationUse Case: Drought Determination

• Title: Research staff tasked to forecast seasonal & annual precipitation, temperature, soil moisture, droughtprecipitation, 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

OGC®



Use Case: Semantic MediationUse 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 d fi iti– WMO definitions

• Use case steps (notional)– User enters a term of interest into mediation client

M di i li l l i i i i– Mediation client access several ontologies in remote registries– Client displays subset of ontologies and allows for creation of links between

termsLinked ontologies used to find datasets of interest– Linked ontologies used to find datasets of interest

OGC®



Interoperability Issues with DataInteroperability 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 systemsDifferent 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 , p p yworkflow, or in the usage pattern for relevant web services

• Attempting to integrate data sets with different temporal scales or timeseries types

OGC®

– ??


Interoperability Issues with CataloguesInteroperability 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 againstcatalogue 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.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

OGC®


Dr. David Arctur [email protected]@opengeospatial.org

Open Geospatial Consortiumhttp://www.opengeospatial.org

Thanks!QuThanks!QuQQestionsestions??

OGC®


Documents

U C f G l i tUse Cases for Geospatial Interoperabilitymaps.aqua.wisc.edu/ican/ican-gl-tuesday-arctur1.pdf · – Disaster Management Scenario ... (SST), winds, land cover, many other