Chap010 - Chapter 10, View Integration and Implementation...

Info iconThis preview shows pages 1–3. Sign up to view the full content.

View Full Document Right Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: Chapter 10, View Integration and Implementation Compromises True/False Questions 1. One reason for creating separate business process level REA models for each transaction cycle is that each cycle represents a manageable set of entities. Ans: True 2. The conceptual models for each business process view should be converted to logical level models before they are integrated into a common view. Ans: False Response: View integration should be done at the conceptual level directly after view modeling. Then the entire integrated model should be converted to a logical level model. 3. Some information needs require data from multiple business processes. Ans: True 4. View integration may be used in the normal course of database design for a single enterprise; alternatively it may be used to consolidate separate databases as a result of a corporate merger, acquisition, or other form of business consolidation. Ans: True 5. The first step in view integration is to examine each relationship in the model and resolve any relationship conflicts. Ans: False Response: The first step is to identify common entities. Relationships are examined in the third step. 6. Entity name conflict occurs when the same entity in different conceptual models is not labeled identically. Ans: True 7. Homonyms are two or more different words used to describe the same thing. Ans: False Response: Two or more different words used to describe the same thing are synonyms. A homonym is the same word used to describe two or more different things. 178 Dunn/Cherrington/Hollander, Enterprise Information Systems: A Pattern Based Approach, 3e Chapter 10, View Integration and Implementation Compromises 8. When an entity participates in multiple relationships and it isn't convenient to place the relationships close to each other, a copy of the entity may be portrayed with a diagonal slash in the bottom right corner of the entity and no attributes attached to the entity copy. Ans: True 9. Relationship structure conflicts exist when the same relationship is assigned different cardinalities in different views. Ans: True 10. Implementation compromises are made only at the physical implementation level of database design. Ans: False Response: Compromises may also be made at the conceptual and logical levels. 11. Exclusion of an entity or relationship because of inadequate measurement mechanisms is one example of a conceptual level modeling implementation compromise. Ans: True 12. Conceptually congruent events are pairs or groups of events that always occur simultaneously. Ans: True 13. A compromised implementation in which conceptually congruent events have been consolidated contains more tables than an uncompromised implementation for the same enterprise....
View Full Document

This note was uploaded on 01/17/2011 for the course INFO SYSTE ACC 115 taught by Professor Baker during the Spring '10 term at Strayer.

Page1 / 23

Chap010 - Chapter 10, View Integration and Implementation...

This preview shows document pages 1 - 3. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online