Podcast
Questions and Answers
Which characteristic defines a good business rule?
Which characteristic defines a good business rule?
Which of the following best describes the term 'Entity Type'?
Which of the following best describes the term 'Entity Type'?
What does a timestamp model help in data handling?
What does a timestamp model help in data handling?
Which type of relationship involves links between three different entity types?
Which type of relationship involves links between three different entity types?
Signup and view all the answers
What is a defining characteristic of a good data name?
What is a defining characteristic of a good data name?
Signup and view all the answers
Which of the following statements about appropriate entities in a database is accurate?
Which of the following statements about appropriate entities in a database is accurate?
Signup and view all the answers
Which classification of attributes refers to those that may or may not have a value?
Which classification of attributes refers to those that may or may not have a value?
Signup and view all the answers
Which statement is true regarding identifiers in a database?
Which statement is true regarding identifiers in a database?
Signup and view all the answers
What is the best definition of a candidate identifier?
What is the best definition of a candidate identifier?
Signup and view all the answers
What characterizes a multivalued attribute in the context of a database system?
What characterizes a multivalued attribute in the context of a database system?
Signup and view all the answers
Study Notes
Business Rules
- Define or constrain aspects of a business.
- Assert business structure and control business behavior.
- Expressed in terms relevant to end users.
- Automated through Database Management Systems software.
Good Business Rules
- Declarative: Focus on "what" rather than "how".
- Precise: Clearly defined and agreed-upon meaning.
- Atomic: Each rule should be a single, independent statement.
- Consistent: Internal and external consistency in rules.
- Expressible: Structured using natural language.
- Distinct: Avoid redundancy in rules.
- Business-oriented: Understood by business people.
Good Data Names
- Related to business characteristics, not technical aspects.
- Meaningful and self-documenting for easy understanding.
- Unique to avoid confusion.
- Readable for easy interpretation.
- Composed of words from an approved list for consistency.
- Repeatable for uniformity.
Data Definitions
- Explanations of terms or facts.
- Terms represent words or phrases with specific meanings.
- Facts denote an association between two or more terms.
- Guidelines for creating good definitions:
- Gather definitions during systems requirement analysis.
- Accompany definitions with diagrams for visual representation.
- Iteratively refine definitions through collaboration.
- Achieve consensus on definitions.
E-R Model Constructs
- Entities:
- Entity instance: A specific person, place, object, event, or concept (often corresponds to a row in a table).
- Entity type: A collection of entities (often corresponds to a table).
- Relationships:
- Relationship instance: Links between entities (corresponds to primary key-foreign key equivalencies in related tables).
- Relationship type: Categories of relationships linking entity types.
- Attribute: A property or characteristic of an entity or relationship type (often corresponds to a field in a table).
Entity Rules
-
Should be:
- An object with many instances in the database.
- An object composed of multiple attributes.
- An object being modeled.
-
Should not be:
- A user of the database system.
- An output of the database system (e.g., a report).
Attribute Classifications
- Required vs. Optional: Whether an attribute must be present for each entity instance.
- Simple vs. Composite: Whether an attribute is a single value or broken down into components.
- Single-Valued vs. Multivalued: Whether an attribute can hold one value or multiple values for each instance.
- Stored vs. Derived: Whether an attribute is physically stored or calculated from other attributes.
- Identifier Attributes (Keys): Attributes that uniquely identify individual instances of an entity type.
Identifier Characteristics
- Unchanging in value.
- Not null.
- No intelligent identifiers (e.g., containing locations or people that might change).
- Substitute simple keys for complex composite keys.
Relationship Types and Instances
- Relationship type: Modeled as lines between entity types. Represents the category of association.
- Relationship instance: Instances of the relationship type linking specific entity instances.
- Relationships can have attributes that describe features of the association between entities.
- Two entities can have multiple relationship types between them.
- Associative Entity: Combines elements of relationships and entities, representing an association with attributes.
Degree of Relationships
- Unary: A relationship between instances of the same entity type.
- Binary: A relationship between two different entity types.
- Ternary: A relationship between three different entity types.
Cardinality of Relationships
- One-to-One: Each entity on both sides has exactly one related entity.
- One-to-Many: One entity can have multiple related entities on the other side, but each entity on the other side can only have one related entity.
- Many-to-Many: Both entities can have multiple related entities on the other side.
Cardinality Constraints
- Define the number of instances of one entity that can or must be associated with each instance of another entity.
-
Minimum Cardinality:
- Zero: Optional relationship.
- One or more: Mandatory relationship.
- Maximum Cardinality: The maximum number of instances allowed in the relationship.
Strong vs. Weak Entities
- Strong entity: Exists independently. Has its own unique identifier.
- Weak entity: Dependent on a strong entity (identifying owner). Cannot exist without the strong entity. Does not have a unique identifier (only a partial identifier).
- Identifying Relationship: Links strong entities to weak entities.
Associative Entities
- Combine characteristics of relationships and entities.
- Have attributes.
- Used when:
- All relationships for the associative entity are many-to-many.
- The entity has meaning independent of the other entities.
- The associative entity has a unique identifier and other attributes.
- The associative entity participates in relationships beyond the original associated entities.
- Ternary relationships need to be modeled.
Studying That Suits You
Use AI to generate personalized quizzes and flashcards to suit your learning preferences.