Page 118

Structuring System Requirements: Conceptual Data Modeling

Chapter 6 Structuring System Requirements: Conceptual Data Modeling

True-False Questions
1. The characteristics of data captured during data modeling are crucial in the design of databases, programs, computer screens, and printed reports. Answer: True 2. Difficulty: Easy Reference: p. 199

Processes, rather than data, are the most complex aspects of many modern information systems. Answer: False Difficulty: Med Reference: p. 199

3.

The purpose of the conceptual data model is to show as many rules about the meaning and interrelationships among data as possible. Answer: True Difficulty: Med Reference: p. 200

4.

The names of data stores on primitive-level data flow diagrams often correspond to the names of data entities in entity-relationship diagrams. Answer: True Difficulty: Med Reference: p. 200

5.

During systems design, a conceptual model with attributes is prepared. Answer: False Difficulty: Med Reference: p. 201

6.

An enterprise-wide data model is prepared during systems implementation and operation. Answer: False Difficulty: Med Reference: p. 201

7.

A logical data model is prepared during systems analysis. Answer: False Difficulty: Med Reference: p. 201

8.

The primary deliverable for the conceptual data modeling step within the analysis phase is an entity-relationship diagram. Answer: True Difficulty: Med Reference: p. 202

9.

A deliverable from conceptual data modeling is a set of entries about data objects to be stored in the project dictionary or repository. Answer: True Difficulty: Easy Reference: p. 204

Page 119

Structuring System Requirements: Conceptual Data Modeling

10.

When constructing a data model, the analyst needs to know how, when, and where data are processed. Answer: False Difficulty: Med Reference: p. 205

11.

The top-down approach to data modeling derives a data model from an intimate understanding of the nature of the business. Answer: True Difficulty: Med Reference: p. 205

12.

An analyst would ask What must we know about each object in order to run a business? in order to determine relationships, their cardinality, and degrees. Answer: False Difficulty: Hard Reference: p. 205

13.

In order to determine attributes and secondary keys, an analyst might ask What characteristics describe each object? Answer: True Difficulty: Hard Reference: p. 205

14.

In order to determine security controls and understand who really knows the meaning of data, an analyst might ask What natural activities or transactions of the business involve handling data about several objects of the same or different type? Answer: False Difficulty: Hard Reference: p. 205

15.

In order to determine the integrity rules, minimum and maximum cardinality, and time dimensions of data, an analyst might ask Are values for data characteristics limited in any way? Answer: True Difficulty: Hard Reference: p. 205

16.

The bottom-up approach to data modeling derives a data model by reviewing specific business documents. Answer: True Difficulty: Med Reference: p. 206

17.

An entity is a person, place, object, event, or concept in the user environment about which the organization wishes to maintain data. Answer: True Difficulty: Med Reference: p. 207

18.

A circle represents a relationship on an entity-relationship diagram. Answer: False Difficulty: Med Reference: p. 207

19.

An ellipse represents an entity on an entity-relationship diagram. Answer: False Difficulty: Med Reference: p. 207

20.

Book, supplier, and state are examples of entity types. Answer: True Difficulty: Med Reference: p. 207

Chapter 6

Essentials of Systems Analysis and Design, Second Edition

Page 120

21.

Since a name represents a set of entities, it is plural on an entity-relationship diagram. Answer: False Difficulty: Med Reference: p. 207

22.

Use a verb or verb phrase to name an entity. Answer: False Difficulty: Easy Reference: p. 207

23.

Social security number, last name, and first name are examples of entity types. Answer: False Difficulty: Med Reference: p. 208

24.

A true data entity will have many possible instances, each with a distinguishing characteristic, as well as one or more other descriptive pieces of data. Answer: True Difficulty: Med Reference: p. 208

25.

An entity instance is a single occurrence of an entity type. Answer: True Difficulty: Med Reference: p. 208

26.

Employee identification number, name, address, and skill are examples of attributes. Answer: True Difficulty: Med Reference: p. 208

27.

An order number is a good example of a candidate key. Answer: True Difficulty: Med Reference: p. 209

28.

A faculty identification number could be used as an identifier. Answer: True Difficulty: Easy Reference: p. 209

29.

A primary key should be null. Answer: False Difficulty: Med Reference: p. 209

30.

An identifier is a candidate key that has been selected as the unique, identifying characteristic for an entity type. Answer: True Difficulty: Med Reference: p. 209

31.

When selecting an identifier, one should choose a candidate key that will not change its value over the life of each instance of the entity type. Answer: True Difficulty: Med Reference: p. 209

32.

Analysts should use intelligent keys as identifiers. Answer: False Difficulty: Med Reference: p. 209

33.

Analysts should consider substituting single-attribute surrogate keys for large composite keys. Answer: True Difficulty: Med Reference: p. 209

Page 121

Structuring System Requirements: Conceptual Data Modeling

34.

Referencing an employee entity, an employees skills are an example of a multivalued attribute. Answer: True Difficulty: Med Reference: p. 210

35.

One way to handle repeating data within an entity is to separate the repeating data into another entity, called a weak entity. Answer: True Difficulty: Med Reference: p. 210

36.

A multivalued attribute is an attribute that may take on more than one value for each entity instance. Answer: True Difficulty: Med Reference: p. 210

37.

A repeating group is a set of two or more multivalued attributes that are logically related. Answer: True Difficulty: Med Reference: p. 210

38.

A join is an association between the instances of one or more entity types that is of interest to the organization. Answer: False Difficulty: Med Reference: p. 211

39.

Relationships are labeled with verb phrases. Answer: True Difficulty: Easy Reference: p. 211

40.

The goal of conceptual data modeling is to capture as much of the meaning of data as possible. Answer: True Difficulty: Med Reference: p. 212

41.

A ternary relationship is a relationship between instances of one entity type. Answer: False Difficulty: Med Reference: p. 213

42.

A unary relationship is the most common type of relationship encountered in data modeling. Answer: False Difficulty: Med Reference: p. 213

43.

A ternary relationship is the equivalent of three binary relationships. Answer: False Difficulty: Med Reference: p. 213

44.

Cardinality is the number of instances of entity B that can (or must) be associated with each instance of entity A. Answer: True Difficulty: Med Reference: p. 213

45.

The minimum cardinality of a relationship is the minimum number of instances of entity B that may be associated with each instance of entity A. Answer: True Difficulty: Med Reference: p. 214

Chapter 6

Essentials of Systems Analysis and Design, Second Edition

Page 122

46.

A plural relationship is a relationship that the data modeler chooses to model as entity type. Answer: False Difficulty: Med Reference: p. 215

47.

A relationship must be turned into an associative entity when the associative entity has other relationships with entities besides the relationship that caused its creation. Answer: True Difficulty: Hard Reference: p. 215

48.

When performing requirements structuring steps, you should match all entities with the data stores appearing on a data flow diagram. Answer: True Difficulty: Med Reference: p. 218

49.

Ideally, each data store on a primitive data flow diagram will be an individual entity. Answer: True Difficulty: Med Reference: p. 218

50.

Conceptual data modeling for an Internet-based electronic commerce application differs significantly from the process followed when analyzing the data needs for other types of applications. Answer: False Difficulty: Med Reference: p. 219

Multiple Choice Questions

51. Some systems developers believe that a data model is the most important part of the statement of information system requirements because: a. the characteristics of data captured during data modeling are crucial in the design of databases, programs, computer screens, and printed reports. b. data rather than processes are the most complex aspects of many modern information systems and thus require a central role in structuring system requirements. c. the characteristics about data are reasonably permanent. d. structural information about data is essential to generate programs automatically. e. of all of the above. Answer: e 52. Difficulty: Med Reference: pp. 199-200

Which of the following is a true statement? a. Data characteristics are dynamic. b. A data model explains the transient form of an organization. c. An information system design based on a data orientation, rather than a process or logic orientation, should have a longer useful life. d. Data flow paths are permanent. e. A data model graphically represents the processes that capture, manipulate, store, and distribute data between a system and its environment and among components within a system. Answer: c Difficulty: Hard Reference: p. 200

Page 123

Structuring System Requirements: Conceptual Data Modeling

53.

Conceptual data modeling is typically done in parallel with other requirements analysis and structuring steps during: a. b. c. d. e. systems planning and selection. systems design. systems analysis. systems implementation and operation. systems evaluation. Difficulty: Med Reference: p. 200

Answer: c 54.

Process, logic, and data model descriptions of a system must be consistent and complete since: a. b. c. d. e. they each describe different but complementary views of the same information system. they are prepared during the analysis phase. they are constructed in parallel by separate analyst teams. a data model indicates when the data are processed. a data model shows how the data are processed. Difficulty: Med Reference: p. 200

Answer: a 55.

The most common format used for data modeling is: a. b. c. d. e. state-transition diagramming. entity-relationship diagramming. process modeling. logic modeling. a flowchart. Difficulty: Med Reference: p. 200

Answer: b 56. During systems analysis: a. b. c. d. e.

a conceptual data model (E-R with attributes) is prepared. a logical model (relational) is prepared. physical files and database designs are prepared. an enterprise-wide data model is prepared. database and file definitions are prepared. Difficulty: Med Reference: p. 201

Answer: a 57.

During systems planning and selection: a. b. c. d. e. a conceptual data model (E-R with attributes) is prepared. a logical model (relational) is prepared. physical files and database designs are prepared. an enterprise-wide data model is prepared. database and file definitions are prepared. Difficulty: Hard Reference: p. 201

Answer: d

Chapter 6

Essentials of Systems Analysis and Design, Second Edition

Page 124

58.

During systems design: a. b. c. d. e. a conceptual data model (E-R with attributes) is prepared. a logical model (relational) is prepared. a conceptual data model (E-R with only entities for the specific project) is prepared. an enterprise-wide data model is prepared. database and file definitions are prepared. Difficulty: Hard Reference: p. 201

Answer: b 59.

During systems implementation and operation: a. b. c. d. e. a conceptual data model (E-R with attributes) is prepared. a logical model (relational) is prepared. physical files and database designs are prepared. an enterprise-wide data model is prepared. database and file definitions are prepared. Difficulty: Hard Reference: p. 201

Answer: e 60.

The primary deliverable from the conceptual data modeling step within the analysis phase is: a. b. c. d. e. a state-transition diagram. an entity-relationship diagram. a context data flow diagram. a decision table. Structured English. Difficulty: Med Reference: p. 202

Answer: b 61.

Which of the following is produced and analyzed during conceptual data modeling? a. b. c. d. An entity relationship diagram for the projects application A data dialogue diagram for the projects application A Gantt chart for the whole database from which the new applications data are extracted A Network diagram for the whole database from which the new applications data are extracted e. A data flow diagram that shows how the new system will be physically implemented Answer: a Difficulty: Hard Reference: p. 204

62.

Which of the following is a true statement? a. A data model explains what the organization does and what rules govern how work is done in the organization. b. To construct a data model, you need to know how data are processed. c. To construct a data model, you need to know when data are processed. d. A data flow diagram graphically illustrates the structure and relationships among data items. e. During conceptual modeling, the preparation of a Network diagram is necessary. Answer: a Difficulty: Med Reference: p. 205

Page 125

Structuring System Requirements: Conceptual Data Modeling

63.

The data modeling perspective that derives the business rules for a data model from an intimate understanding of the nature of the business, rather than from any specific information requirements in screens, reports, or business forms, is referred to as the: a. b. c. d. e. top-down approach. bottom-up approach. overview approach. business approach. conceptual approach. Difficulty: Med Reference: p. 205

Answer: a 64.

Asking system users and business managers How many instances of each object might exist? would help determine: a. b. c. d. e. the data entities and their descriptions. the candidate key. attributes and secondary keys. relationships and their cardinality and degrees. integrity rules, minimum and maximum cardinality, and time dimensions of data. Difficulty: Hard Reference: p. 205

Answer: a 65.

Asking system users and managers Who is responsible for establishing legitimate values for these data? helps determine: a. b. c. d. e. the candidate key. security controls and understanding who really knows the meaning of data. relationships and their cardinality and degrees. attributes and secondary keys. integrity rules, minimum and maximum cardinality, and time dimensions of data. Difficulty: Hard Reference: p. 205

Answer: b 66.

Asking system users and business managers Is each activity or event always handled the same way or are there special circumstances? helps determine: a. b. c. d. e. the candidate key. security controls and understanding who really knows the meaning of data. relationships and their cardinality and degrees. attributes and secondary keys. integrity rules, minimum and maximum cardinality, and time dimensions of data. Difficulty: Hard Reference: p. 205

Answer: e 67.

Gathering the information you need for data modeling by reviewing specific business documents handled within the system describes the: a. b. c. d. e. top-down approach. bottom-up approach. investigative approach. business approach. conceptual approach. Difficulty: Med Reference: p. 206

Answer: b

Chapter 6

Essentials of Systems Analysis and Design, Second Edition

Page 126

68.

Reviewing computer screens, reports, and business forms for the purpose of gaining an understanding of data is indicative of the: a. b. c. d. e. investigative approach. business approach. bottom-up approach. top-down approach. conceptual approach. Difficulty: Med Reference: p. 206

Answer: c 69.

A detailed, logical, and graphical representation of the entities, associations, and data elements for an organization or business area best describes a(n): a. b. c. d. e. logic model. data flow diagram. entity-relationship diagram. structure chart. data tree. Difficulty: Med Reference: p. 206

Answer: c 70.

Which of the following symbols are used on entity-relationship diagrams? a. b. c. d. e. an arrow a square a diamond two parallel lines a circle Difficulty: Med Reference: p. 207

Answer: c 71.

On an entity-relationship diagram, a diamond represents a(n): a. b. c. d. e. data flow. entity. multivalued attribute. repeating group. relationship. Difficulty: Med Reference: p. 207

Answer: e 72.

On an entity-relationship diagram, a rectangle represents a(n): a. b. c. d. e. data flow. entity. multivalued attribute. repeating group. relationship. Difficulty: Med Reference: p. 207

Answer: b

Page 127

Structuring System Requirements: Conceptual Data Modeling

73.

A person, place, object, event, or concept in the user environment about which the organization wishes to maintain data refers to a(n): a. b. c. d. e. attribute. data element. relationship. entity. process. Difficulty: Med Reference: p. 207

Answer: d 74. A product is an example of a(n): a. b. c. d. e. data element. attribute. entity. relationship. process.

Answer: c 75.

Difficulty: Med

Reference: p. 207

A renewal is an example of a(n): a. b. c. d. e. data element. attribute. entity. relationship. action stub. Difficulty: Med Reference: p. 207

Answer: c 76.

A collection of entities that share common properties or characteristics best defines: a. b. c. d. e. entity type. entity instance. entity occurrence. entity collection. data set. Difficulty: Med Reference: p. 207

Answer: a 77.

A single occurrence of an entity type defines: a. b. c. d. e. entity instance. entity appearance. attribute. data element. multivalued attribute. Difficulty: Med Reference: p. 208

Answer: a

Chapter 6

Essentials of Systems Analysis and Design, Second Edition

Page 128

78.

Which of the following is a true statement? a. b. c. d. e. Data entities correspond to sources/sinks on a data flow diagram. Relationships correspond to data flows on a data flow diagram. A data entity will have many possible instances. Verbs are used to name entity types. An entity type is described many times in the data model. Difficulty: Med Reference: p. 208

Answer: c 79.

A named property or characteristic of an entity that is of interest to the organization defines: a. b. c. d. e. attribute. relationship. instance. associative entity. data flow. Difficulty: Med Reference: p. 208

Answer: a 80.

An attribute (or combination of attributes) that uniquely identifies each instance of an entity type defines: a. b. c. d. e. data element occurrence. trigger. candidate key. associative entity. data marker. Difficulty: Med Reference: p. 209

Answer: c 81.

When selecting an identifier, one should: a. use intelligent keys. b. use large composite keys instead of single-attribute surrogate keys. c. choose a candidate key that will not change its value over the life of each instance of the entity type. d. choose a candidate key such that for each instance of the entity, the attribute is guaranteed to have valid values or is null. e. choose a candidate key that allows for duplicate values. Answer: c Difficulty: Med Reference: p. 209

82.

Vehicle identification number, color, weight, and horsepower best exemplify: a. b. c. d. e. entities. entity types. data markers. identifiers. attributes. Difficulty: Med Reference: p. 209

Answer: e

Page 129

Structuring System Requirements: Conceptual Data Modeling

83.

A candidate key that has been selected as the unique, identifying characteristic for an entity type is called a(n): a. b. c. d. e. attribute. identifier. secondary key. gerund. index. Difficulty: Med Reference: p. 209

Answer: b 84.

On an entity-relationship diagram, the entitys identifier is: a. b. c. d. e. identified by using a double-lined ellipse. underlined on an E-R diagram. bold on an E-R diagram. written in all capital letters on an E-R diagram. placed in italics. Difficulty: Med Reference: p. 210

Answer: b 85.

An attribute that can have more than one value for each entity instance is referred to as: a. b. c. d. e. a gerund. a multivalued attribute. a nonexclusive attribute. a data replica. none of the above. Difficulty: Med Reference: p. 210

Answer: b 86.

If each employee can have more than one skill, then skill is referred to as a: a. b. c. d. e. gerund. multivalued attribute. nonexclusive attribute. repeating attribute. data replica. Difficulty: Med Reference: p. 210

Answer: b 87.

A set of two or more multivalued attributes that are logically related defines: a. b. c. d. e. relationship. associative entity. repeating group. class. repeating entity. Difficulty: Med Reference: p. 210

Answer: c

Chapter 6

Essentials of Systems Analysis and Design, Second Edition

Page 130

88.

An association between the instances of one or more entity types that is of interest to the organization best defines: a. b. c. d. e. occurrence. relationship. natural connection. cardinality. entity link. Difficulty: Med Reference: p. 211

Answer: b 89.

Which of the following is a true statement? a. The goal of conceptual modeling is to capture as much of the meaning of data as is possible. b. The efficiencies gained by maintaining systems at the rule rather than code level drastically reduce cost. c. If a thorough repository of data descriptions is kept, the system can be regenerated as the business rules change. d. The more details about data that we can model, the better the system we can design and build. e. All of the above are true statements. Answer: e Difficulty: Med Reference: p. 212

90.

The number of entity types that participate in a relationship refers to: a. b. c. d. e. degree. association. count. cardinality. normalization. Difficulty: Med Reference: p. 212

Answer: a 91.

If STUDENT and COURSE participate in a relationship, this is an example of a(n): a. b. c. d. e. unary relationship. binary relationship. ternary relationship. extraordinary relationship. coupled relationship. Difficulty: Med Reference: p. 213

Answer: b 92.

A ternary relationship occurs when a relationship exists among instances of: a. b. c. d. e. the same entity. two entity types. three entity types. four entity types. nine entity types. Difficulty: Med Reference: p. 213

Answer: c

Page 131

Structuring System Requirements: Conceptual Data Modeling

93.

A relationship between the instances of one entity type is a: a. b. c. d. e. unary relationship. binary relationship. ternary relationship. singular occurrence. partnership occurrence. Difficulty: Med Reference: p. 213

Answer: a 94.

A relationship between instances of two entity types is a: a. b. c. d. e. unary relationship. binary relationship. ternary relationship. multiple occurrence. partnership occurrence. Difficulty: Med Reference: p. 213

Answer: b 95.

A simultaneous relationship among instances of three entity types is a: a. b. c. d. e. unary relationship. binary relationship. ternary relationship. multiple occurrence. recursive join. Difficulty: Med Reference: p. 213

Answer: c 96.

The number of instances of entity B that can (or must) be associated with each instance of entity A refers to: a. b. c. d. e. cardinality. domain. ternary occurrence. participation level. join level. Difficulty: Med Reference: p. 213

Answer: a 97.

The minimum number of instances of entity B that may be associated with each instance of entity A defines the: a. b. c. d. e. degree of the relationship. minimum cardinality of the relationship. maximum cardinality of the relationship. domain of the relationship. join level. Difficulty: Med Reference: p. 214

Answer: b

Chapter 6

Essentials of Systems Analysis and Design, Second Edition

Page 132

98.

If entity B is a mandatory participant, then: a. b. c. d. e. the minimum cardinality of the relationship is two. the minimum cardinality of the relationship cannot be defined. the minimum cardinality of the relationship is one. the minimum cardinality of the relationship is optional. the join level is not null. Difficulty: Med Reference: p. 214

Answer: c 99.

A many maximum cardinality is noted on the E-R diagram by: a. b. c. d. e. placing a crows foot notation near the entity. placing a zero through the line near the entity. using a double ellipse near the entity. placing two slash marks near the entity. using brackets. Difficulty: Hard Reference: p. 214

Answer: a 100.

A relationship that the data modeler chooses to model as an entity type best defines: a. b. c. d. e. recursive relationship. associative entity. domain. complex relationship. complex entity. Difficulty: Med Reference: p. 215

Answer: b

Fill In the Blanks

101. A conceptual model is a detailed model that shows the overall structure of organizational data while being independent of any database management system or other implementation considerations. Difficulty: 102. Med Reference: p. 200

A top-down approach derives the data model from an intimate understanding of the nature of the business, rather than from any specific information requirements in computer displays, reports, or business forms. Difficulty: Med Reference: p. 205

103.

A bottom-up approach reviews specific business documents, such as computer displays, reports, and business forms, handled within the system. Difficulty: Med Reference: p. 206

Page 133

Structuring System Requirements: Conceptual Data Modeling

104.

An entity-relationship diagram is a detailed, logical, and graphical representation of the entities, associations, and data elements for an organization or business area. Difficulty: Med Reference: p. 206

105.

An entity is a person, place, object, event, or concept in the user environment about which the organization wishes to maintain data. Difficulty: Med Reference: p. 207

106.

An entity type is a collection of entities that share common properties or characteristics. Difficulty: Med Reference: p. 207

107.

An entity instance is a single occurrence of an entity type. Difficulty: Med Reference: p. 208

108.

An attribute is a named property or characteristic of an entity that is of interest to the organization. Difficulty: Med Reference: p. 208

109.

A candidate key is an attribute or combination of attributes that uniquely identifies each instance of an entity type. Difficulty: Med Reference: p. 209

110.

An identifier is a candidate key that has been selected as the unique, identifying characteristic for an entity type. Difficulty: Med Reference: p. 209

111.

A multivalued attribute is an attribute that may take on more than one value for each entity instance. Difficulty: Med Reference: p. 210

112.

A repeating group is a set of two or more multivalued attributes that are logically related. Difficulty: Med Reference: p. 210

113.

One approach to handling multivalued attributes is to separate the data into a weak entity. Difficulty: Hard Reference: p. 210

114.

A relationship is an association between the instances of one or more entity types that is of interest to the organization. Difficulty: Med Reference: p. 211

115.

Degree refers to the number of entity types that participate in a relationship. Difficulty: Med Reference: p. 212

Chapter 6

Essentials of Systems Analysis and Design, Second Edition

Page 134

116.

A unary relationship is a relationship between the instances of one entity type. Difficulty: Hard Reference: p. 213

117.

Recursive relationship is another name for a unary relationship. Difficulty: Hard Reference: p. 213

118.

A binary relationship is a relationship between instances of two entity types. Difficulty: Med Reference: p. 213

119.

A ternary relationship is a simultaneous relationship among instances of three entity types. Difficulty: Hard Reference: p. 213

120.

Cardinality refers to the number of instances of entity B that can (or must) be associated with each instance of entity A. Difficulty: Med Reference: p. 213

121.

The minimum cardinality of a relationship is the minimum number of instances of entity B that may be associated with each instance of entity A. Difficulty: Med Reference: p. 214

122.

The maximum cardinality is the maximum number of instances of entity B that may be associated with each instance of entity A. Difficulty: Med Reference: p. 214

123.

If the minimum number of instances of an entity is zero, then we can say that the entity is an optional participant in the relationship. Difficulty: Hard Reference: p. 214

124.

On an entity-relationship diagram, a crows foot notation designates a many maximum cardinality. Difficulty: Hard Reference: p. 214

125.

An associative entity 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. Difficulty: Med Reference: p. 215

Page 135

Structuring System Requirements: Conceptual Data Modeling

Matching Questions
Match each of the following terms with its corresponding definition. a. b. c. d. e. 126. Entity Entity type Attribute Multivalued attribute Entity instance

A person, place, object, event, or concept in the user environment about which the organization wishes to maintain data. Answer: a Reference: p. 207 A single occurrence of an entity type. Answer: e Reference: p. 208

127.

128.

A named property or characteristic of an entity that is of interest to the organization. Answer: c Reference: p. 208

129.

A collection of entities that share common properties or characteristics. Answer: b Reference: p. 207

130.

An attribute that can have more than one value for each entity instance. Answer: d Reference: p. 210

Match each of the following terms with its corresponding definition. a. b. c. d. e. f. 131. Unary relationship Ternary relationship Binary relationship Relationship Repeating group Associative entity

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. Answer: f Reference: p. 215

132.

A set of two or more multivalued attributes that are logically related. Answer: e Reference: p. 210

133.

An association between the instances of one or more entity types that is of interest to the organization. Answer: d Reference: p. 211

Chapter 6

Essentials of Systems Analysis and Design, Second Edition

Page 136

134.

A relationship between instances of two entity types. Answer: c Reference: p. 213

135.

A simultaneous relationship among instances of three entity types. Answer: b Reference: p. 213

136.

A relationship between the instances of one entity type. Answer: a Reference: p. 213

For each of the following statements, answer a if it is a true statement or answer b if the statement is false. 137. The name of the identifier of each entity is underlined on an E-R diagram. Answer: 138. a Reference: p. 210

To illustrate a multivalued attribute, use a double-lined ellipse. Answer: a Reference: p. 210

139.

On E-R diagrams, relationships are labeled with verb phrases. Answer: a Reference: p. 211

140.

The goal of conceptual data modeling is to identify as much of the processing activity as possible. Answer: b Reference: p. 212

141.

To illustrate a multivalued attribute, separate the repeating data into another entity, then using a relationship, link the weak entity to its associated regular entity. Answer: a Reference: p. 210

142.

A recursive relationship is a relationship between the instances of two entity types. Answer: b Reference: p. 213

Page 137

Structuring System Requirements: Conceptual Data Modeling

For each of the examples listed below, indicate if it is a relationship, an entity, or an attribute. (Answers may occur more than once.). a. Attribute b. Entity c. Relationship 143. sale Answer: 144. quantity sold Answer: 145. is ordered on Answer: 146. sells Answer: 147. inventory item Answer: 148. product Answer: 149. item description Answer: 150. invoice Answer: 151. received on Answer: 152. invoice item Answer: b Reference: p. 207 c Reference: p. 211 b Reference: p. 207 a Reference: p. 208 b Reference: p. 207 b Reference: p. 207 c Reference: p. 211 c Reference: p. 211 a Reference: p. 208 b Reference: p. 207

Chapter 6

Essentials of Systems Analysis and Design, Second Edition

Page 138

For each of the following statements, answer a if it is a true statement, or answer b if the statement is false. 153. A singular noun is used to name an entity type. Answer: 154. a Reference: p. 207

Upper- and lowercase letters are used in naming an entity type. Answer: b Reference: pp. 207-208

155.

A diamond is used to represent an entity. Answer: b Reference: p. 207

156.

An entity instance is a single occurrence of an entity type. Answer: a Reference: p. 208

157.

Many instances of an entity type may be represented by data stored in the database. Answer: a Reference: p. 208

Essay Questions
158. Define the following key data modeling terms: entity, attribute, relationship, degree, cardinality, and associative entity. An entity is a person, place, object, event, or concept in the user environment about which the organization wishes to collect and maintain data. An attribute is a named property or characteristic of an entity that is of interest to the organization. A relationship is an association between the instances of one or more entity types that is of interest to the organization. Degree defines the number of entity types that participate in a relationship. Cardinality specifies the number of instances of entity B that can (or must) be associated with each instance of entity A. An associative entity associates the instances of one or more entity types and contains attributes that are peculiar to the relationship between those entity instances. 159. Discuss unary, binary, and ternary relationships. The number of entity types participating in a relationship defines the degree of the relationship. The most common relationships are unary, binary, and ternary. A unary relationship is a relationship between the instances of one entity type. An example of this type of relationship is the person entity. One person (or instance) can be married to another person (or instance). The binary relationship is a relationship between instances of two entity types. An example of this relationship is of a supplier and part. The binary relationship is the most common type of relationship encountered in data modeling. The ternary relationship is a simultaneous relationship among instances of three entity types. An example is a supplier shipping a part to a warehouse.

Page 139

Structuring System Requirements: Conceptual Data Modeling

160.

Contrast data modeling to process modeling and logic modeling. Data modeling focuses on the data that must be stored by the system. Data flow diagrams and the processing logic techniques demonstrate how, where, and when data are used or modified by the system. However, these techniques do not illustrate the definition, structure, and relationships within the data. By providing this view, data modeling complements the process modeling and logic modeling techniques.

161.

Briefly identify the four entity-relationship diagrams that are produced and analyzed during conceptual data modeling. The four entity-relationship diagrams are: (1) an entity-relationship diagram that illustrates the data needed in the projects application; (2) an entity-relationship diagram for the system being replaced; (3) an entity-relationship diagram that illustrates the entire database from which the new applications data are extracted; and (4) an entity-relationship diagram for the entire database for the existing application system.

162.

What are multivalued attributes and repeating groups? Provide an example of each. A multivalued attribute is an attribute that may assume more than one value for each entity instance. A repeating group is a related set of multivalued attributes. Using a student and the courses she takes as an example, the course grade is an example of a multivalued attribute. The course number, course name, and grade would repeat for each course that the student takes.