1 / 26

UML ( cont. )

UML ( cont. ). Diagrammatic notation = “visual language”... For constructing a data model Drawings, relationships constructed in Visio Tools to input a drawing to ArcGIS input data to the data model . UML Notation Zeiler pp. 97-99. a class is shown as a box

aiden
Download Presentation

UML ( cont. )

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. UML ( cont. ) • Diagrammatic notation = “visual language”... • For constructing a data model • Drawings, relationships constructed in Visio • Tools to input a drawing to ArcGIS • input data to the data model

  2. UML NotationZeilerpp. 97-99 • a class is shown as a box • top part contains the name of the class • lower part contains the attributes • lines connect boxes and indicate relationships • methods/rules associated with the class

  3. Graphic courtesy of Maidment et al., ArcHydro team

  4. Objects and Features • Object (abstract class, real world) • in ArcGIS an object is non-spatial • it is NOT a point, line, or area • it has no geographic location • it has no shape attribute in its table • Drainage network, ship, vehicle, … customer, lake, house, etc. • Feature (feature class, spatial context) • an object that has geographic location • a point, line, area, TIN, raster

  5. UML Notation ( cont. ) • Abstract class • specify subclasses underneath • Mammals w/human or dog feature classes • Numbers w/integer or float feature classes • Extremely generic • Feature Class • Specify subtypes underneath

  6. Graphic courtesy of Maidment et al., ArcHydro team

  7. GridPoints has GridLocation Marine Data Model • Model Mesh Points

  8. Relationships • Links between classes, shown as lines • One to one • One to many • Many to many

  9. Relationships (cont.) • 1:1 - solid line • one record in Class A linked to one record in Class B • “is married to” • the class of state capitals linked to the class of states • 1:n - solid line with * at one end • one record in Class A linked to any number of records in Class B • "owns" • the class of states linked to the class of area codes

  10. Relationships (cont.) • m:n - solid line with * at both ends • any number of records in Class A linked to any number of records in Class B • "has visited” • "was never married to" • the class of mountain lions linked to the class of wilderness areas

  11. Graphic courtesy of Maidment et al., ArcHydro team

  12. Type Inheritance • White triangle • Class B inherits the properties (attributes, methods) of Class A • the class street inherits from the class transportation network • Solid diamond • the parts and the whole depend on each other

  13. Graphic courtesy of Maidment et al., ArcHydro team

  14. Measurement InstantaneousPoints MeasuringDevice MeasuredType MeasuredData InstantaneousPoint (ex: CTD) Michael Blongewicz X TimeStamp Y Measurement MeasuringDevice Z

  15. Marine Data Model Gdb Geodatabase Feature Class Feature Dataset Table Relationship Class

  16. Steps in Data Modeling (1) Conceptualize the user's view of data • what are the basic features needed to solve the problem? (2) Select the geographic representation • points, lines, areas, rasters, TINs (3) Define objects and relationships • draw a UML diagram, specify relationships, “behaviors” (4) Match to geodatabase elements • Refine relationships, “behaviors” (5) Organize geodatabase structure, add data

  17. Data Model Levels Reality Human-oriented Conceptual Model Increasing Abstraction Logical Model Computer-oriented Physical Model

  18. Modeling Process Conceptual Model Lists, flow diagrams, etc Real World Objects and relationships Logical Model Diagram in CASE Tool Physical Model Database Schema (Object state) Graphic courtesy of ESRI

  19. Steps in Data Modeling (1) Conceptualize the user's view of data • what are the basic features needed to solve the problem? (2) Select the geographic representation • points, lines, areas, rasters, TINs (3) Define objects and relationships • draw a UML diagram, specify relationships, “behaviors” (4) Match to geodatabase elements • Refine relationships, “behaviors” (5) Organize geodatabase structure, add data • e.g., Alyssa Aaby’s talk yesterday, and subsequent marine GAP analysis

  20. Resulting Analysis - ArcHydro From Arctur and Zeiler, Case Studies in GIS Data Modeling, ESRI Press, in prep.

  21. Data Model Exercise • Part 1 - Required - due Apr. 28, 6:00 p.m. • Part 2 - Extra credit - turn in before end of term • Exercise and data on web and on server

  22. Marine Data Model

More Related