database design

DM-36 - Physical models
  • Differentiate between logical and physical models, in terms of the level of detail, constraints, and range of information included
  • Create physical model diagrams, using UML or other tools, based on logical model diagrams and software requirements
  • Create a complete design document ready for implementation
  • Recognize the constraints and opportunities of a particular choice of software for implementing a logical model
DM-35 - Logical models
  • Determine which relationships need to be stored explicitly in the database
  • Create logical models based on conceptual models and general data models using UML or other tools
  • Differentiate between conceptual and logical models, in terms of the level of detail, constraints, and range of information included
  • Evaluate the various general data models common in GIS&T for a given project, and select the most appropriate solutions
  • Distinguish between the incidental and structural relationships found in a conceptual model
  • Explain the various types of cardinality found in databases
  • Define the cardinality of relationships
DM-34 - Conceptual models
  • Define entities and relationships as used in conceptual data models
  • Create a conceptual model diagram of data needed in a geospatial application or enterprise database
  • Design application-specific conceptual models
  • Deconstruct an application use case into conceptual components
  • Explain the objectives of the conceptual modeling phase of design
  • Describe the degree to which attributes need to be modeled in the conceptual modeling phase
DM-33 - Modeling tools
  • Compare and contrast the relative merits of various textual and graphical tools for data modeling, including E-R diagrams, UML, and XML
  • Create E-R and UML diagrams of database designs
  • Create conceptual, logical, and physical data models using automated software tools

Pages