Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
56 Cards in this Set
- Front
- Back
A detailed model that captures the overall structure of data in an organization
|
Conceptual Data Modeling
|
|
Independent of any database management system (DBMS) or other implementation considerations
|
Conceptual Data Modeling
|
|
Primary deliverable is an __________ or ______________
|
entity-relationship (E-R) diagram or class diagram
|
|
Data model is derived from an intimate understanding of the business.
|
Top-down
|
|
Data model is derived by reviewing specifications and business documents.
|
Bottom-up
|
|
What are subjects/objects of the business?
|
Data entities and descriptions
|
|
What unique characteristics distinguish between subjects/objects of the same type?
|
Primary keys
|
|
What characteristics describe each subject/object
|
Attributes and secondary keys
|
|
How do you use the data?
|
Security controls and user access privileges
|
|
A detailed, logical representation of the entities, associations and data elements for an organization or business
|
Entity-Relationship (E-R) Diagram
|
|
Notation of E-R Diagram uses three main constructs
|
Data entities
Relationships Attributes |
|
Square
|
Entity
|
|
Triangle
|
Relationship
|
|
Circle
|
Attribute
|
|
Person, place, object, event or concept about which data is to be maintained
|
Entity
|
|
Association between the instances of one or more entity types
|
Relationship
|
|
named property or characteristic of an entity
|
Attribute
|
|
collection of entities with common characteristics
|
Entity type
|
|
single entity
|
Entity instance
|
|
Attribute (or combination of attributes) that uniquely identifies each instance of an entity type
|
Candidate key
|
|
Canidate Key
Identifier |
Identifier Attributes
|
|
A candidate key that has been selected as the unique identifying characteristic for an entity type
|
Identifier
|
|
Oval with Line
|
Identifier Attribute
|
|
Multivalued Attributes Represented on E-R Diagram in two ways:
|
double-lined ellipse
weak entity |
|
number of entity types that participate in a relationship
|
Degree
|
|
between two instances of one entity type
|
Unary
|
|
between the instances of two entity types
|
Binary
|
|
among the instances of three entity types
|
Ternary
|
|
The number of instances of entity B that can or must be associated with each instance of entity A
|
Cardinality
|
|
The minimum number of instances of entity B that may be associated with each instance of entity A
|
Minimum Cardinality
|
|
The maximum number of instances of entity B that may be associated with each instance of entity A
|
Maximum Cardinality
|
|
Specifies whether an instance must exist or can be absent in the relationship
|
Mandatory vs. Optional Cardinalities
|
|
An entity type that associates the instances of one or more entity types and contains attributes that are peculiar to the relationship between those entity instances
|
Associative Entities
|
|
An associative entity is:
|
An entity
A relationship |
|
________________ is the preferred way of illustrating a relationship with attributes
|
associative entity
|
|
A relationship that itself is related to other entities via another relationship must be represented as an _______________________ .
|
associative entity
|
|
a subrouping of the entities in an entity type that shares common attributes or relationships distinct from other subtypes
|
Subtype
|
|
a generic entity type that has a relationship with one or more subtype
|
Supertype
|
|
an entity instance of the supertype must be an instance of one of the subtypes
|
Total specialization
|
|
an entity instance of the supertype may or may not be an instance of one of the subtypes
|
Partial specialization
|
|
an entity instance of the supertype can be an instance of only one subtype
|
Disjoint
|
|
an entity instance of the supertype may be an instance of multiple subtypes
|
Overlap
|
|
Specifications that preserve the integrity of the logical data model
|
Business Rules
|
|
Four types of Business Rules:
|
Entity integrity
Referential integrity constraints Domains Triggering operations |
|
unique, non-null identifiers
|
Entity integrity
|
|
rules governing relationships
|
Referential integrity constraints:
|
|
valid values for attributes
|
Domains
|
|
other business rules regarding attribute values
|
Triggering operations
|
|
The set of all data types and ranges of values that an attribute can assume
|
Domains
|
|
Advantages of Domains
|
Verify that the values for an attribute are valid
Ensure that various data manipulation operations are logical Help conserve effort in describing attribute characteristics |
|
An assertion or rule that governs the validity of data manipulation operations such as insert, update and delete
|
Triggering Operations
|
|
statement of the business rule to be enforced by the trigger
|
User rule
|
|
data manipulation operation that initiates the operation
|
Event
|
|
name of entity being accessed or modified
|
Event Name
|
|
condition that causes the operation to be triggered
|
Condition
|
|
action taken when the operation is triggered
|
Action
|