click below
click below
Normal Size Small Size show me how
BIA354 Exam 1
| Question | Answer |
|---|---|
| Data that describes the properties or characteristics of the data including data context (names, definitions), length (size), allowable values, and type (integer, decimal, alphanumeric) | Metadata |
| Column labels are ______ because they give context to the data in each row | Metadata |
| Statements that define or constrain some business aspect | Business rules |
| This is an example of a _____ _____: “An order can include many products but it must have at least one product.” | Business rule |
| A person, a place, an object, an event, or a concept in the user environment about which the organization wishes to maintain data | Entity |
| The set of attributes defined by one entire entity table | Entity type |
| The set of attributes in one row of an entity | Entity instance |
| Property or characteristic of an entity or relationship type | Attribute |
| Attribute that stands alone | Simple attribute |
| Attribute with meaningful component attributes | Composite attribute |
| An attribute that may take on more than one value for a given instance | Multivalued attribute |
| An attribute whose values can be calculated from related attribute values | Derived attribute |
| An attribute that must have a value for every instance | Required attribute |
| An attribute that may not have a value for every instance | Optional attribute |
| An attribute whose value is different for each entity instance | Unique attribute |
| Each entity must have at least one ______ attribute. Each ______ attribute is called a _____ _____ | Unique, unique, candidate key |
| An attribute (or combination of attributes) that uniquely identifies individual instances of an entity type | Identifier (key) |
| An association that represents an interaction among the instances of one or more entity types | Relationship |
| The number of entities that participate in a relationship | Degree of a relationship |
| A relationship in which one entity is related to another of the same entity type | Unary relationship |
| A relationship in which entities of two different entity types are related to each other | Binary relationship |
| A relationship in which entities of three different entity types are related to each other | Ternary relationship |
| The number of instances of one entity that can or must be associated with each instance of another entity | Cardinality |
| Cardinality of _____ _____: Each order MAY be transacted by zero or one employee | Optional one |
| Cardinality of _____ _____: Each product MAY be part of zero or more orders | Optional many |
| Cardinality of _____ _____: Each order MUST be placed by one and only one customer | Mandatory one |
| Cardinality of _____ _____: Each order MUST contain one or more products | Mandatory many |
| A relationship cardinality in which each entity in the relationship will have exactly one related entity | One-to-one |
| A relationship cardinality in which an entity on one side of the relationship can have many related entities, but an entity on the other side will have a maximum of one related entity | One-to-many |
| A relationship cardinality in which entities on both sides of the relationship can have many related entities on the other side | Many-to-many |
| When more than one relationship exists between the same entity types | Multiple relationships |
| The relationship between strong and weak entities | Identifying relationship |
| The entity on the one side of the relationship is almost always the _____ entity. The entity on the many side is almost always the _____ entity | Strong, weak |
| A combination of a relationship and entity | Associative entity |
| The two situations in which an associative entity should be created | 1. Many-to-many relationships 2. Ternary relationships |
| Order -|----< Order_line >----|- Product Here, one order contains _____ product(s) and one product contains _____ order(s) | Many, many |
| What are the three components of the relational database model? | 1. Data structure 2. Data integrity 3. Data manipulation |
| A named, two-dimensional table of data in a relational model | Relation |
| In a relational model, a _____ _____ is a unique identifier (simple or composite) of the relation that guarantees all rows are unique | Primary key |
| In a relational model, a _____ _____ is an identifier that enables a dependent relation (on the many side of a relationship) to refer to its parent relation (on the one side of the relationship) | Foreign key |
| A constraint stating that a primary key attribute can NOT be null | Entity integrity constraint |
| A constraint stating that any foreign key value MUST match a primary key value in the relation of the one side (if optional the foreign key can be null) | Referential integrity constraint |
| A constraint defining all allowable values for an attribute | Domain constraint |
| In a relational diagram, the arrow points toward the _____ entity. The _____ entity gets the foreign key | Strong, weak |
| Facts that are recorded and can be accessed and are not organized to convey any specific meaning | Data |
| The centralized storehouse for metadata | Data repository |
| An organized collection of logically related data | Database |
| Data that is accessed by a user for some particular purpose | Information |
| What is the purpose of a primary key in the context of an individual entity table? | Uniquely identify any single row |
| What type of entity is reliant on composite candidate keys? | Associative entity |
| What type of attribute is always required when inputting data into a database? | Candidate key |
| An associative entity has a ______ ______ and other ______. It also has an ______ meaning | Unique identifier, attributes, independent |
| Why does the weak entity inherent the primary key from the strong entity? | The weak entity is fully dependent |
| What kinds of relationships are established between supertypes and subtypes | One-to-one |
| A general, high-level entity containing attributes shared by multiple specialized subtypes | Supertype |
| Attributes that break down large supertype attributes into specific categories | Subtypes |
| Improving the logical design of a database to create well-structured relations | Data normalization |
| What are the four things that data normalization hopes to accomplish? | 1. Avoid duplication and conserve storage 2. Satisfy certain referential integrity constraints 3. Facilitate data maintenance by eliminating the insertion, update, and deletion anomalies 4. Provide a better design that enables future growth |
| A table should pertain to _____ _____ entity type | Only one |
| When the value of the determinant decides the value of another attribute | Functional dependency |
| In a relational model, a primary key is any key that is not _____ _____ on anything else | Functionally dependent |
| Determinants have the minimal number of attributes to maintain the functional dependency with all non-key attributes | Full dependency |
| When non-key attributes are functionally dependent on a subset of the primary key | Partial dependency |
| When the primary key is a determinant for another attribute which is a determinant for a third attribute | Transitive functional dependency |
| _____ databases need high normalization. _____ databases can do with low normalization | Transactional, analytical |
| To reach third normal form, there should be no _____ _____ | Transitive dependencies |
| To reach second normal form, there should be no _____ _____ | Partial dependencies |
| To reach first normal form, there should be no _____ _____ | Repeating groups |
| Data transformed from an information source into table format that has undergone no normalization yet | Unnormalized form |
| _____ normal form is generally considered to be sufficient | Third |
| What are the six steps to creating an ERD? | 1. Entities 2. Attributes 3. Identifiers 4. Relationships 5. Cardinalities 6. Associative entities |
| What are the five steps to creating a relational diagram? | 1. Map entities to relations 2. Map attributes 3. Identify primary keys 4. Identify foreign keys 5. Link foreign keys to primary keys |
| What are the five steps to normalizing a database? | 1. Remove repeating groups (1NF) 2. Identify primary keys 3. Remove partial dependencies (2NF) 4. Remove transitive dependencies (3NF) 5. Link foreign keys to primary keys |
| An attribute (or group of attributes) represented on the left side of the arrow | Determinant |
| When new rows create duplicate data or certain facts cannot be recorded | Insertion anomaly |
| When changing data in a row forces changes in other rows | Update anomaly |
| When deleted rows result in the loss of data needed for future rows | Deletion anomaly |
| What type of anomaly is the most critically important to avoid? | Deletion anomaly |