Multiple Choice Questions

Similar documents
Modern Systems Analysis and Design Seventh Edition

Information Technology Audit & Cyber Security

Database Systems: Design, Implementation, and Management Tenth Edition. Chapter 4 Entity Relationship (ER) Modeling

Database Principles: Fundamentals of Design, Implementation, and Management Tenth Edition. Chapter 7 Data Modeling with Entity Relationship Diagrams

David M. Kroenke and David J. Auer Database Processing Fundamentals, Design, and Implementation

Chapter 3 Database Modeling and Design II. Database Modeling

Database Systems: Design, Implementation, and Management Tenth Edition. Chapter 4 Entity Relationship (ER) Modeling

Systems Analysis and Design Methods Chapter 7: Data Modeling and Analysis

Non-overlappingoverlapping. Final outcome of the worked example On pages R&C pages R&C page 157 Fig 3.52

Chapter 4. In this chapter, you will learn:

MULTIPLE CHOICE. Choose the one alternative that best completes the statement or answers the question.

DATABASE SYSTEMS. Chapter 5 Entity Relationship (ER) Modelling DESIGN IMPLEMENTATION AND MANAGEMENT INTERNATIONAL EDITION ROB CORONEL CROCKETT

Chapter 4 Entity Relationship Modeling In this chapter, you will learn:

Represent entities and relations with diagrams

Data Modeling Online Training

The Entity-Relationship Model. The Entity-Relationship model. The ER model. The Entity-Relationship model. E-R Model Constructs. E-R Model Constructs

Chapter 17. Methodology Logical Database Design for the Relational Model

Elements of the E-R Model

CMP-3440 Database Systems

Objectives of logical design... Transforming the ERD diagram into relations. Relational database components. Mapping a composite attribute

Chapter 2: Entity-Relationship Model. Entity Sets. Entity Sets customer and loan. Attributes. Relationship Sets. A database can be modeled as:

Entity-Relationship Model. From Chapter 5, Kroenke book

IMS1002/CSE1205 Lectures 1

Chapter 12. Entity-Relationship Modeling

E-R Model. Hi! Here in this lecture we are going to discuss about the E-R Model.

Entity Relationship Diagram (ERD): Basics

Chapter 2 Conceptual Modeling. Objectives

Agenda: Understanding Relationship Types Degree and Cardinality with Examples

Lecture 09. Spring 2018 Borough of Manhattan Community College

The Entity Relationship Model

Example: specific person, company, event, plant

Fundamentals, Design, and Implementation, 9/e Copyright 2004 Database Processing: Fundamentals, Design, and Implementation, 9/e by David M.

COMP102: Introduction to Databases, 9.1

Design Process Modeling Constraints E-R Diagram Design Issues Weak Entity Sets Extended E-R Features Design of the Bank Database Reduction to

Unit 2 - Data Modeling. Pratian Technologies (India) Pvt. Ltd.

Database Management System 6 ER Modeling...

Chapter 2: Entity-Relationship Model

Intro to DB CHAPTER 6

Introduction to Database. Dr Simon Jones Thanks to Mariam Mohaideen

Chapter 6: Entity-Relationship Model

Chapter # 4 Entity Relationship (ER) Modeling

Entity-Relationship Model

A l Ain University Of Science and Technology

Topic 5: Mapping of EER Diagrams to Relations

Lab # 1. Structuring System Requirements: Diagrams

Objectives Definition iti of terms Importance of data modeling Write good names and definitions for entities, relationships, and attributes Distinguis

Chapter 3 The Enhanced E-R Model

Chapter 6: Entity-Relationship Model

Related download: Instructor Manual for Modern Database Management 12th Edition by Hoffer Venkataraman Topi (Case studies included)

Data Analysis 1. Chapter 2.1 V3.1. Napier University Dr Gordon Russell

Conceptual Data Modeling and the Entity- Relationship Model. Department of Computer Science Northern Illinois University September 2014

Chapter 8 The Enhanced Entity- Relationship (EER) Model

Entity Relationship Modelling

Chapter 1: The Database Environment

Chapter 6: Entity-Relationship Model. E-R Diagrams

4. Entity Relationship Model

Relational Model (cont d) & Entity Relational Model. Lecture 2

Database Principles: Fundamentals of Design, Implementation, and Management Tenth Edition. Chapter 7 Data Modeling with Entity Relationship Diagrams

Essentials of Database Management

Database Principles: Fundamentals of Design, Implementation, and Management Tenth Edition. Chapter 8 Data Modeling Advanced Concepts

Data Modelling. Static Data in the organisation Fundamental building block of the system Two perspectives (Process and Data) Of Data.

1/24/2012. Chapter 7 Outline. Chapter 7 Outline (cont d.) CS 440: Database Management Systems

Conceptual Database Design (ER modeling) Chapter Three

Full file at

A l Ain University Of Science and Technology

Database Foundations. 4-1 Oracle SQL Developer Data Modeler. Copyright 2015, Oracle and/or its affiliates. All rights reserved.

Using High-Level Conceptual Data Models for Database Design A Sample Database Application Entity Types, Entity Sets, Attributes, and Keys

COMP 244. Entity Relationship Model Basics. Entity-Relationship Models. Key elements of the E-R model DATABASE CONCEPTS & APPLICATIONS

Essentials of Database Management (Hoffer et al.) Chapter 2 Modeling Data in the Organization

The DBMS accepts requests for data from the application program and instructs the operating system to transfer the appropriate data.

Chapter 8: Enhanced ER Model

DATA MODELING USING THE ENTITY-RELATIONSHIP MODEL. 1 Powered by POeT Solvers Limited

Chapter 6: Entity-Relationship Model

Chapter 2 Entity-Relationship Data Modeling: Tools and Techniques. Fundamentals, Design, and Implementation, 9/e

Distributed Database Systems By Syed Bakhtawar Shah Abid Lecturer in Computer Science

THE ENTITY- RELATIONSHIP (ER) MODEL CHAPTER 7 (6/E) CHAPTER 3 (5/E)

MIT Database Management Systems Lesson 03: Entity Relationship Diagrams

Chapter 7: Entity-Relationship Model

Conceptual Data Modeling

Chapter 7: Entity-Relationship Model

Chapter 10. Object-Oriented Analysis and Modeling Using the UML. McGraw-Hill/Irwin

More on the Chen Notation

CS403- Database Management Systems Solved Objective Midterm Papers For Preparation of Midterm Exam

Basant Group of Institution

Mahathma Gandhi University

CSIT5300: Advanced Database Systems

Conceptual Database Design. COSC 304 Introduction to Database Systems. Entity-Relationship Modeling. Entity-Relationship Modeling

Chapter 7: Entity-Relationship Model

Modern Systems Analysis and Design

MTAT Introduction to Databases

Chapter 2 Entity-Relationship Data Modeling: Tools and Techniques. Fundamentals, Design, and Implementation, 9/e

DATA MODELS FOR SEMISTRUCTURED DATA

Database Management System CS403 Lecture No 1 Database definitions: 1 A shared collection of logically related data, designed to meet the information

Major components of ER diagram Practices

Data Modeling Using the Entity-Relationship (ER) Model

Chapter 9: Relational DB Design byer/eer to Relational Mapping Relational Database Design Using ER-to- Relational Mapping Mapping EER Model

Database Design. IIO30100 Tietokantojen suunnittelu. Michal Zabovsky. Presentation overview

Module 2 : Entity-Relationship Model 15

Objectives Definition iti of terms List five properties of relations State two properties of candidate keys Define first, second, and third normal for

CS352 Lecture - The Entity-Relationship Model

Transcription:

Chapter 9 Structuring System Data Requirements 193 Chapter 9 Structuring System Data Requirements Multiple Choice Questions 1. 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. all of the above 2. 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. 3. The most common format used for data modeling is: a. state-transition diagramming b. entity-relationship diagramming c. process modeling d. decision table diagramming 4. Conceptual data modeling is typically done in parallel with other requirements analysis and structuring steps during: a. logical design b. physical design d. implementation 5. An E-R model with attributes is prepared during: a. design b. project identification and selection d. project initiation and planning 6. 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. top-down approach b. bottom-up approach c. overview approach d. business approach

Chapter 9 Structuring System Requirements: Conceptual Data Modeling 194 7. The three main constructs of the entity-relationship modeling notation include each of the following except: a. data entities b. data flows c. relationships d. attributes 8. A person, place, object, event, or concept in the user environment about which the organization wishes to maintain data refers to a(n): b. data element c. relationship d. entity 9. A single occurrence of an entity type defines: a. entity instance b. entity appearance c. attribute d. data element 10. A named property or characteristic of an entity that is of interest to the organization defines: c. instance 11. An attribute (or combination of attributes) that uniquely identifies each instance of an entity type defines: a. data element occurrence b. trigger c. candidate key 12. For each entity, the name of the identifier is: a. identified by using a double-lined ellipse b. underlined on an E-R diagram c. bold on an E-R diagram d. written in all capital letters on an E-R diagram 13. A set of two or more multivalued attributes that are logically related defines: a. relationship b. gerund c. repeating group d. class 14. An association between the instances of one or more entity types that is of interest to the organization best defines: a. occurrence c. coupling d. cardinality

Chapter 9 Structuring System Data Requirements 195 15. If STUDENT and COURSE participate in a relationship, their relationship is a(n): a. unary relationship b. binary relationship c. ternary relationship d. extraordinary relationship 16. The number of instances of entity B that can (or must) be associated with each instance of entity A refers to: a. cardinality b. domain c. ternary occurrence d. participation level 17. A relationship that the data modeler chooses to model as an entity type best defines: a. recursive relationship b. associative entity c. domain d. complex relationship 18. A subgrouping of the entities in an entity type that is meaningful to the organization and that shares common attributes or relationships distinct from other subgroupings best defines: a. child node b. disjoined entity c. subtype d. supertype 19. Which of the following specifies that an entity instance can simultaneously be a member of two (or more) subtypes? a. total specialization rule b. partial specialization rule c. disjoint rule d. overlap rule 20. The data manipulation operation (insert, delete, or update) that initiates the operation is called a(n): a. condition b. action c. user rule d. event

Chapter 9 Structuring System Requirements: Conceptual Data Modeling 196 Answers 1. 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. all of the above Answer: d Difficulty: Med Reference: p. 283 2. 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. Answer: c Difficulty: Med Reference: p. 284 3. The most common format used for data modeling is: a. state-transition diagramming b. entity-relationship diagramming c. process modeling d. decision table diagramming Answer: b Difficulty: Med Reference: p. 286 4. Conceptual data modeling is typically done in parallel with other requirements analysis and structuring steps during: a. logical design b. physical design d. implementation Answer: c Difficulty: Med Reference: p. 285 5. An E-R model with attributes is prepared during: a. design b. project identification and selection d. project initiation and planning Answer: c Difficulty: Med Reference: p. 287

Chapter 9 Structuring System Data Requirements 197 6. 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. top-down approach b. bottom-up approach c. overview approach d. business approach Answer: a Difficulty: Med Reference: p. 288 7. The three main constructs of the entity-relationship modeling notation include each of the following except: a. data entities b. data flows c. relationships d. attributes Answer: b Difficulty: Med Reference: p. 290 8. A person, place, object, event, or concept in the user environment about which the organization wishes to maintain data refers to a(n): b. data element c. relationship d. entity Answer: d Difficulty: Med Reference: p. 290 9. A single occurrence of an entity type defines: a. entity instance b. entity appearance c. attribute d. data element Answer: a Difficulty: Med Reference: p. 291 10. A named property or characteristic of an entity that is of interest to the organization defines: c. instance Answer: a Difficulty: Med Reference: p. 293 11. An attribute (or combination of attributes) that uniquely identifies each instance of an entity type defines: a. data element occurrence b. trigger c. candidate key Answer: c Difficulty: Med Reference: p. 294

Chapter 9 Structuring System Requirements: Conceptual Data Modeling 198 12. For each entity, the name of the identifier is: a. identified by using a double-lined ellipse b. underlined on an E-R diagram c. bold on an E-R diagram d. written in all capital letters on an E-R diagram Answer: b Difficulty: Med Reference: p. 294 13. A set of two or more multivalued attributes that are logically related defines: a. relationship b. gerund c. repeating group d. class Answer: c Difficulty: Med Reference: p. 295 14. An association between the instances of one or more entity types that is of interest to the organization best defines: a. occurrence c. coupling d. cardinality Answer: b Difficulty: Med Reference: p. 296 15. If STUDENT and COURSE participate in a relationship, their relationship is a(n): a. unary relationship b. binary relationship c. ternary relationship d. extraordinary relationship Answer: b Difficulty: Med Reference: p. 299 16. The number of instances of entity B that can (or must) be associated with each instance of entity A refers to: a. cardinality b. domain c. ternary occurrence d. participation level Answer: a Difficulty: Med Reference: p. 300 17. A relationship that the data modeler chooses to model as an entity type best defines: a. recursive relationship b. associative entity c. domain d. complex relationship Answer: b Difficulty: Med Reference: p. 302

Chapter 9 Structuring System Data Requirements 199 18. A subgrouping of the entities in an entity type that is meaningful to the organization and that shares common attributes or relationships distinct from other subgroupings best defines: a. child node b. disjoined entity c. subtype d. supertype Answer: c Difficulty: Med Reference: p. 305 19. Which of the following specifies that an entity instance can simultaneously be a member of two (or more) subtypes? a. total specialization rule b. partial specialization rule c. disjoint rule d. overlap rule Answer: d Difficulty: Med Reference: p. 306 20. The data manipulation operation (insert, delete, or update) that initiates the operation is called a(n): a. condition b. action c. user rule d. event Answer: d Difficulty: Hard Reference: p. 309