Essentials of Systems Analysis and Design, 6e (Valacich)
Chapter 9 Designing Databases
1) One of the purposes of logical and physical database design is to choose data-storage
technologies that will efficiently, accurately, and securely process database activities.
Classification: Concept
2) The selection of data-storage technologies is made during the systems implementation and
operation phase.
Classification: Concept
3) The network model is the most common style for a logical database model.
Classification: Concept
4) Generally speaking, logical and physical database design is performed in parallel with other
systems design steps.
Classification: Concept
5) Normalization helps build a data model that is simple, not redundant, and requires minimum
maintenance.
Classification: Concept
1
6) During logic modeling, the normalized data requirements from all user interfaces are
combined into one consolidated logical database model.
Classification: Concept
7) Conceptual modeling is performed during systems design.
Classification: Concept
8) The selection of the appropriate data types of attributes from the logical database model is
made during physical database design.
Classification: Concept
9) In general, data structure refers to grouping attributes from the logical database model into
physical records.
Classification: Concept
10) A file organization is an arrangement of related records in secondary memory so that
individual and groups of records can be stored, retrieved, and updated rapidly.
Classification: Concept
11) The primary deliverable from logical database design is a conceptual model.
Classification: Concept
2
12) When using the normalized relation notation, the primary key attribute is indicated by a
dashed underline.
Classification: Concept
13) A relation corresponds to a computer file.
Classification: Concept
14) During physical database design, relations from logical database design are translated into
computer file specifications.
Classification: Concept
15) The network database model is a popular database technology for new information systems.
Classification: Concept
16) Object-oriented database models are the most frequently used database technologies for new
information systems development.
Classification: Concept
17) Each column in a relation corresponds to an entity type.
Classification: Concept
3
18) Each row of a relation corresponds to a record that contains data values for an entity.
Classification: Concept
19) One property of a relation is that entries in columns are from the same set of values.
Classification: Concept
20) Referencing a relation, the sequence of columns cannot be interchanged without changing
the meaning or use of the relation.
Classification: Concept
21) A well-structured relation contains data about two or more entities.
Classification: Concept
22) The result of normalization is that every nonprimary key attribute depends upon the whole
primary key and nothing but the primary key.
Classification: Concept
23) Normalization is based on an analysis of weak entities.
Classification: Concept
4
24) If for every valid value of A the value of B is determined by the value of A, then B is
functionally dependent on A.
Classification: Application
25) An attribute can be functionally dependent on more than one attribute.
Classification: Concept
26) A relation is said to be in second normal form if the primary key consists of a combination
key, and the nonkey attributes are partially dependent on the primary key.
Classification: Concept
27) A relation is in second normal form if every nonprimary key attribute is functionally
dependent on the whole primary key.
Classification: Concept
28) A relation is said to be in second normal form if the primary key consists of only one
attribute.
Classification: Concept
29) Transitive attributes are attributes that determine other attributes.
Classification: Concept
5
30) A relation is said to be in second normal form when there are no transitive dependencies.
Classification: Concept
31) A business rule is an integrity constraint specifying that the value of an attribute in one
relation depends on the value of the same attribute in another relation.
Classification: Concept
32) The creation of a separate relation is sometimes required to represent a relationship.
Classification: Concept
33) Referential integrity specifies that the value of an attribute of one relation depends on the
existence of the same attribute in another relation.
Classification: Concept
34) Each entity type in an ER Diagram becomes an attribute.
Classification: Concept
35) The value of a key attribute in a relation must uniquely identify every row in the relation.
Classification: Concept
6
36) A key can be redundant.
Classification: Concept
37) A binary 1 to many relationship in an ER Diagram is represented by adding the primary key
of the entity on the one side of the relationship as a foreign key to the entity on the many side.
Classification: Concept
38) For a binary one-to-one relationship between two entities, A and B, the primary key of A
becomes a foreign key in B and the primary key in B becomes a foreign key in A.
Classification: Concept
39) When two relations, A and B, have a many-to-many relationship, we create a separate
relation, C, to represent this.
Classification: Concept
40) A corporal key is one assigned by the system.
Classification: Concept
41) A recursive foreign key is a foreign key in a relation that references the primary key value of
the same relation.
Classification: Concept
7
42) When modeling a many-to-many unary relationship, the primary key of the relation
representing the relationship is always singular.
Classification: Concept
43) View integration is the last step of logical database design.
Classification: Concept
44) Two different names used for the same attribute is called a homonym.
Classification: Concept
45) Two different names used for the same attribute is called a synonym.
Classification: Concept
46) A default value is a value a field will assume unless an explicit value is entered for that field.
Classification: Concept
47) A null value is used to represent the zero digit in a relation.
Classification: Concept
8
48) Efficient use of secondary storage and data processing speed are the two goals of physical
table design.
Classification: Concept
49) Generally speaking, a physical table always corresponds to a relation.
Classification: Concept
50) Denormalization reduces the chance of errors introduced by normalizing relations.
Classification: Concept
51) Denormalization is the process of splitting or combining normalized relations into physical
tables based on EFFICIENCY of use of rows and fields.
Classification: Concept
52) A data marker is a field of data that can be used to locate a related field or row of data.
Classification: Concept
53) When using the sequential file organization, the addition of rows requires rewriting the file.
Classification: Concept
9
54) Sequential files are practical for random row retrievals.
Classification: Concept
55) Indexes should be used generously for databases intended primarily to support data
retrievals.
Classification: Concept
56) Indexes should be used generously for databases that support transaction processing and
other applications with heavy updating requirements.
Classification: Concept
57) The hashed file organization determines the address for each row by using an algorithm.
Classification: Concept
58) Sequential retrieval on the primary key is impractical with the hashed file organization.
Classification: Concept
59) A primary key is converted in a hashed file organization.
Classification: Concept
10