“Coastal Erosion” A Use Case for Coastal Atlases

David HartUniversity of WisconsinWisconsin Sea Grant

Marcia BermanMarcia BermanVirginia Institute of Marine ScienceCenter for Coastal Resources Management

T H d dTanya HadadOregon Coastal Zone Management Program

September, 2010 1

What is a Use Case?

• Outline

• Background

St t i Ai• Strategic Aims

• Members

• Products

• ICAN Future

• Use cases describe system behavior from an actor's point of view as scenario-driven threads through the functional requirements;

• Conclusion

• Each use case focuses on describing how to achieve a goal or a task

• Use cases provide a general sense of the information requirements for applications.

2September, 2010

Developing the Coastal Erosion Use Case

• Defined a set of “actors” or users with an interest in coastal erosion;

D fi d t f ifi t k i ti th t h• Defined a set of specific tasks via questions that each user needed to address;

• Defined the necessary data that each user required to answer• Defined the necessary data that each user required to answer those questions.;

• “Coastal Erosion” was the use case topic around which theCoastal Erosion was the use case topic around which the ICAN prototype was initiated to demonstrate ontology development and interoperability across CWAs.

3September, 2010

3.1. Coastal Atlas Users and the Importance of Interoperability Use Casesp p y

September, 2010 4

Structure of the Coastal Erosion Use Case

ROLE/CLIENTQUESTIONSQUESTIONSDATASETS

5September, 2010

Structure of the Coastal Erosion Use Case

EXAMPLE:EXAMPLE:

ROLE/CLIENT: Coastal Managerg

QUESTION(S): What are the erosion rates along a geographically defined shoreline (coastal) reach?

DATASETS: Historic Shoreline Positions

6September, 2010

Structure of the Coastal Erosion Use Case

ANOTHER EXAMPLE:ANOTHER EXAMPLE:

ROLE/CLIENT: Emergency Responderg y p

QUESTION(S): Where are the best evacuation routes during major coastal storm events?

DATASETS: topography, transportation networks

7September, 2010

Roles/Clients in the Coastal Erosion Use Casein the Coastal Erosion Use Case

• Coastal Manager• Private Property Ownersp y• Emergency Responders• Scientist

L l S t Ad i i t t• Local System Administrator

8September, 2010

Datasets

Coastal access and recreationCoastal armoringC d l d i h ib iCadastral datasets with assessor attributionGeologyLand use and zoningCurrent shoreline positionHi t i h li itiHistoric shoreline positionsPermit tracking systems and a dynamic link to cadastral dataAerial imageryStreamsB hBeachesBluff and dune fieldsRegulatory jurisdictionsCommunity developG h l filGeomorphology profilesErosion Risk study results – Risk Zones or LinesTopographyWave climate dataSh ll t b th t

9September, 2010

Shallow water bathymetryTransportation networksPublic utilitiesPublic lands

Adaptation of the Coastal Erosion Use Case for a Networked CWACase for a Networked CWA

• Virginia X

• Maryland Maryland

10September, 2010

Virginia’s Strengths

• Conservation Planning• Aquaculture• WildlifeWildlife

D t t t t l iData to support a coastal erosion use case is not available

September, 2010 11

Maryland’s Strengths

• Coastal hazard planning• Habitat assessment

September, 2010 12

What are the erosion rates along a geographically defined shoreline (coastal)

h?reach?

September, 2010 13

Where/When/How has the shoreline been defended? (i.e., armored, hardened, protected)defended? (i.e., armored, hardened, protected)

September, 2010 14

How big is an incoming storm / erosion-causing event?

September, 2010 16

What is the best method to protect my shoreline?