The Modeling Data in the Organization and the Enhanced ER Model
🇬🇧
In English
In English
Practice Known Questions
Stay up to date with your due questions
Complete 5 questions to enable practice
Exams
Exam: Test your skills
Test your skills in exam mode
Learn New Questions
Popular in this course
Learn with flashcards
Manual Mode [BETA]
Select your own question and answer types
Other available modes
Complete the sentence
Listening & SpellingSpelling: Type what you hear
multiple choiceMultiple choice mode
SpeakingAnswer with voice
Speaking & ListeningPractice pronunciation
TypingTyping only mode
The Modeling Data in the Organization and the Enhanced ER Model - Leaderboard
The Modeling Data in the Organization and the Enhanced ER Model - Details
Levels:
Questions:
57 questions
| 🇬🇧 | 🇬🇧 |
| This is a detailed, logical representation of the data for an organization or for a business area. | Entity-relationship model |
| This is the graphical representation of an entity-relationship model or ER model. | Entity-relationship diagram |
| These are properties of an entity. | Attributes |
| This is 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 |
| This is a meaningful association between (or among) entity types. | Relationship type |
| This is an association between (or among) entity instances where each [BLANK] associates exactly one entity instance from each participating relationship type. | Relationship instance |
| These are crucial to data modeling and providing names and definitions for entity types, attributes, and relationships. | Business rules |
| These are intended to assert business structure or to control or influence the behavior of the business. | Business rules |
| This is a high level model that represents the requirements and complexities of a complex database. | Enhanced entity-relationship model |
| What are the two concepts of EER model? | Generalization Specialization |
| This is the process of defining a more general entity type from a set of more specialized entity types. | Generalization |
| This is the process of defining one or more subtypes of the supertype and forming supertype/subtype relationships. | Specialization |
| These constraints allow you to capture some of the important business rules that apply to these relationships. | Specifying constraints |
| These are the two most important type of constraints that are described. | Completeness constaints Disjointness constraints |
| This is a type of constraint that addresses whether an instance of a supertype must also be a member of at least one subtype. | Completeness constraints |
| These are the two possible rules of the completeness constraints. | Total specialization rule Partial specialization rule |
| This rule specifies that each entity instance of a supertype must be a member of some subtype in the relationship. | Total specialization rule |
| This rule specifies that an entity instance of a supertype is allowed not to belong to any subtype. | Partial specialization rule |
| These constraints addresses whether an instance of a supertype may simultaneously be a member of two (or more) subtypes. | Disjointness constraints |
| These are the two possible rules of the disjointness constraints. | Disjoint rule Overlap rule |
| What are the three types of data models? | Conceptual data model Logical data model Physical data model |
| What are the five data model building blocks? | Entities Attributes Relationship Constraint Business rules |
| What are the two different types of an entity? | Strong entity Weak entity |
| What are the five types of attributes? | Simple attributes Composite attributes Derived attributes Single-value attributes Multi-value attributes |
| What are the three degrees of a relationship? | Unary (degree 1) Binary (degree 2) Ternary (degree 3) |
| This is a high-level view of the entire data environment of an organization. | Conceptual data model |
| This describes the data in a more detailed and structured way than the conceptual model. | Logical data model |
| This describes an association among entities. | Relationship |
| This has a primary key. This is dependent on strong entities. Its existence is not dependent on any other entity. | Strong entity |
| These cannot be further subdivided into components. | Simple attributes |
| These can be split into components, and are made of more than one simple attribute. | Composite attributes |
| These are the attributes that do not exist in the physical database, but their values are derived from other attributes present in the database. | Derived attributes |
| These takes up only a single value for each entity instance. | Single-value attributes |
| These may contain more than one value. | Multi-value attributes |
| This is a relationship between instances of a single entity type. | Unary relationship |
| This is a relationship between the instances of two entity types and is the most common type of relationship encountered in data modeling. | Binary relationship |
| This is a simultaneous relationship among the instances of three entity types. | Ternary relationship |