Database Systems, unit: Database Design and ER Diagrams. Core concepts, terminology, and worked-example cues a college student meets for this unit, building on prior units without repeating them. Front: a term, concept, or short problem cue. Back: the definition, explanation, or answer.
18 cards · basic cards · AI-written, checked twice. Edit anything.
- What is database design?
- The process of structuring a database to efficiently store and organize data
- What is an ER (Entity-Relationship) diagram?
- A visual model showing entities, their attributes, and relationships
- What is an entity, in ER modeling?
- A distinct object or concept represented by a table, such as a customer or product
- What is an attribute, in ER modeling?
- A property or characteristic of an entity
- What is a relationship, in ER modeling?
- An association between two or more entities
- What is cardinality, in ER modeling?
- The numerical relationship between rows of two related entities, such as one-to-many
- What is a weak entity?
- An entity that cannot be uniquely identified without the primary key of another entity
- What is an identifying relationship?
- A relationship linking a weak entity to its owning strong entity
- What is a strong entity?
- An entity that has its own unique primary key and does not depend on another entity
- What is a derived attribute?
- An attribute whose value can be calculated from other attributes, such as age from birth date
- What is a multivalued attribute?
- An attribute that can hold more than one value for a single entity
- What is the process of converting an ER diagram into relational tables called?
- Mapping (or translating the ER model to a relational schema)
- How is a one-to-many relationship typically implemented in tables?
- By placing a foreign key on the 'many' side referencing the 'one' side
- How is a many-to-many relationship typically implemented in tables?
- By creating a junction table with foreign keys to both related tables
- What is conceptual database design?
- Designing a high-level, technology-independent model of the data requirements
FlashKeepers