Data Analysis (and User Interaction) GEOG 463 5/7/04

Data Analysis Report Introduction / Review Analysis Plan –Data flow/process diagrams for each objective (User interface design) –Event trace for each interactive element

System Design Use an object-oriented (UML) approach Three components to the design (conceptual model) –Object model (database) –Functional model (data processing) –Dynamic model (user interface) Object model specifies what it happens to Functional model specifies what happens Dynamic model specifies when it happens Potentially need all three for systems requirement

Functional Model Describes the computations within a system Shows how objects (data) are transformed to satisfy objectives – create information Communicates how outputs are derived from inputs Specifies the meaning of the operations in the object model and the actions in the dynamic model Depicted using data flow or data process diagrams

Data Processing to Create a Seismic Landslide Map

Data Process Diagram of Seismic Landslide Analysis

Data Flow Diagram of Community Recovery from Earthquakes

Dynamic Model for Interactive Systems Concerned with changes (states) of objects (interactive elements) and their relationships over time Concerned with control -- the sequence of events or operations that occur as the result of some stimuli Described using event trace diagrams and state diagrams

User Interface for Community Recovery Decision Support System

Event Trace Diagram for Recovery Decision Support System

State Diagram for Recovery Decision Support System

Unified Modeling Language Resources Software to use in the department –Microsoft Visio or other drawing tools –ESRI’s “Building Geodatabases with Visio” IBM Rational Rose literature on design w/ UML –Introduction to UML –Entity-relationship modeling with UML UML tutorials on the web