Multivalued attributes are typically represented by creating additional columns

Multivalued attributes are typically represented by

This preview shows page 1 - 2 out of 2 pages.

Multivalued attributes are typically represented by creating additional columns in the same table. Checking for integrity constraint is an optional step during logical database design. False Identifying relationship types is part of the physical design. False Conceptual database design is the process of constructing a model of the data independent of all physical considerations. True Attributes whose values are based on values of other attributes are known as derived attributes. Validating relations (tables) using normalization is part of logical database design. True Homonyms are entities having the same name but are in fact different. True A potential problem that can be identified during the conceptual design is the omission of certainattributes, entities, or relationships. True Deriving relations (tables) is part of the conceptual design. False Simple/Composite and Single/Multi-values nature of attributes mean the same thing. False Deriving relations (tables) is part of the physical design. True
Image of page 1
A critical success factor in database design is to work interactively with the users as much as possible. True For Mandatory/nondisjoint (mandatory/and), we will always need only one tablet irrespective of the number of subclasses. True The primary key of a weak entity should not be derived from its corresponding strong entity. The way we decided to do one to one relationship is somewhere different from how it is prescribed in the book. True
Image of page 2

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture