Exam 6: Developing Data Models for Business Databases

arrow
  • Select Tags
search iconSearch Question
flashcardsStudy Flashcards
  • Select Tags

When adding historical details to a relationship,typically the 1-M relationship is converted to an M-N relationship with an attribute.

(True/False)
4.8/5
(34)

A common design error is to leave relationships in a design that could be derived from other relationships.These relationships are referred to as ___________ relationships.

(Short Answer)
4.9/5
(32)

Repeating the information already contained in an ERD is an example of poor________________.

(Short Answer)
4.8/5
(30)

For relationship ________,you should look at the number (singular or plural)of nouns along with other words that indicate cardinality.

(Short Answer)
4.9/5
(30)

Figuer: Figuer:   -Assuming that we do not use the rule(s)that avoid null values in tables,the table AUTHOR obtained in converting the ERD diagram to a relational database will have the following number of attributes: -Assuming that we do not use the rule(s)that avoid null values in tables,the table AUTHOR obtained in converting the ERD diagram to a relational database will have the following number of attributes:

(Multiple Choice)
4.9/5
(43)

One common refinement to an initial ERD would be to split compound attributes into smaller attributes.

(True/False)
4.8/5
(31)

When constructing an ERD from a problem narrative:

(Multiple Choice)
4.8/5
(31)

In a narrative,you should look for _________ involving people,things,places,and events as potential entity types.

(Short Answer)
4.8/5
(37)

The basic rules for converting an ERD cannot be applied to converting self-referencing relationships or more complex identification dependencies.

(True/False)
4.8/5
(37)

________________ should include justification for design decisions involving multiple feasible choices and explanations of subtle design choices.

(Short Answer)
4.9/5
(33)

In the absence of indication of minimum cardinality,the default should be _________.

(Short Answer)
4.9/5
(39)

Figuer: Figuer:   -Assuming that we do not use the rule(s)that avoid null values in tables,the table VOLUME obtained in converting the ERD diagram to a relational database will have the following primary key: -Assuming that we do not use the rule(s)that avoid null values in tables,the table VOLUME obtained in converting the ERD diagram to a relational database will have the following primary key:

(Multiple Choice)
5.0/5
(42)

Figuer: Figuer:   -In converting the ERD diagram to a relational database,SS# will appear in the following number of tables: -In converting the ERD diagram to a relational database,SS# will appear in the following number of tables:

(Multiple Choice)
4.8/5
(40)

Figuer: Figuer:   -Assuming that we do not use the rule(s)that avoid null values in tables in converting the ERD diagram to a relational database,the number of tables will be: -Assuming that we do not use the rule(s)that avoid null values in tables in converting the ERD diagram to a relational database,the number of tables will be:

(Multiple Choice)
4.8/5
(35)

Figuer: Figuer:   -Assuming that we do not use the rule(s)that avoid null values in tables in converting the ERD diagram to a relational database,the number of attributes in the key of the table MEMBER is: -Assuming that we do not use the rule(s)that avoid null values in tables in converting the ERD diagram to a relational database,the number of attributes in the key of the table MEMBER is:

(Multiple Choice)
4.9/5
(35)
Showing 61 - 75 of 75
close modal

Filters

  • Essay(0)
  • Multiple Choice(0)
  • Short Answer(0)
  • True False(0)
  • Matching(0)