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

Similar documents
Multiple Choice Questions

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

Modern Systems Analysis and Design

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

Introduction to Relational Databases. Introduction to Relational Databases cont: Introduction to Relational Databases cont: Relational Data structure

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

Chapter 6. Advanced Data Modeling. Database Systems: Design, Implementation, and Management, Seventh Edition, Rob and Coronel

MINGGU Ke 8 Analisa dan Perancangan Sistem Informasi

Conceptual Data Modeling

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

Relational Database Components

MIDTERM EXAMINATION Spring 2010 CS403- Database Management Systems (Session - 4) Ref No: Time: 60 min Marks: 38

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

Entity-Relationship Model. From Chapter 5, Kroenke book

A Data Modeling Process. Determining System Requirements. Planning the Project. Specifying Relationships. Specifying Entities

Data Modeling: Beginning and Advanced HDT825 Five Days

CS403- Database Management Systems Solved MCQS From Midterm Papers. CS403- Database Management Systems MIDTERM EXAMINATION - Spring 2010

Introduction to Database. Dr Simon Jones Thanks to Mariam Mohaideen

Modern Systems Analysis and Design Seventh Edition

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

normalization are being violated o Apply the rule of Third Normal Form to resolve a violation in the model

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

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

Solved MCQ on fundamental of DBMS. Set-1

Information Technology Audit & Cyber Security

Chapter 3 Database Modeling and Design II. Database Modeling

Database Management System 6 ER Modeling...

Chapter 6: Entity-Relationship Model. The Next Step: Designing DB Schema. Identifying Entities and their Attributes. The E-R Model.

8) A top-to-bottom relationship among the items in a database is established by a

The Next Step: Designing DB Schema. Chapter 6: Entity-Relationship Model. The E-R Model. Identifying Entities and their Attributes.

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

Chapter 1: The Database Environment

Chapter 17. Methodology Logical Database Design for the Relational Model

Basant Group of Institution

Mahathma Gandhi University

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

Chapter 4. The Relational Model

The Entity Relationship Model

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

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

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

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


Chapter 12. Entity-Relationship Modeling

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

OBJECTIVES. How to derive a set of relations from a conceptual data model. How to validate these relations using the technique of normalization.

System Analysis & design

Contents. Database. Information Policy. C03. Entity Relationship Model WKU-IP-C03 Database / Entity Relationship Model

Chapter 2: Entity-Relationship Model

A l Ain University Of Science and Technology

A l Ain University Of Science and Technology

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

Lecture2: Database Environment

Modern Systems Analysis and Design Sixth Edition

4. Entity Relationship Model

Chapter 4. In this chapter, you will learn:

Conceptual Design. The Entity-Relationship (ER) Model

CSE 530A. ER Model. Washington University Fall 2013

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

Conceptual Database Design

Introduction to modeling

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

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

Translation of ER-diagram into Relational Schema. Dr. Sunnie S. Chung CIS430/530

COMP102: Introduction to Databases, 9.1

FAQ: Relational Databases in Accounting Systems

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

Entity Relationship Diagram (ERD) Dr. Moustafa Elazhary

KDI EER: The Extended ER Model

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

Database Design & Programming with SQL: Part 1 Learning Objectives

Week. Lecture Topic day (including assignment/test) 1 st 1 st Introduction to Module 1 st. Practical

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

Entity Relationship Diagram (ERD): Basics

Data Modeling Online Training

Data about data is database Select correct option: True False Partially True None of the Above

Chapter # 4 Entity Relationship (ER) Modeling

Data Modeling. Yanlei Diao UMass Amherst. Slides Courtesy of R. Ramakrishnan and J. Gehrke

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

Entity Relationship Modelling

CPS510 Database System Design Primitive SYSTEM STRUCTURE

Essentials of Database Management

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

Topic 5: Mapping of EER Diagrams to Relations

Techno India Batanagar Computer Science and Engineering. Model Questions. Subject Name: Database Management System Subject Code: CS 601

Represent entities and relations with diagrams

CMP-3440 Database Systems

Full file at

Databases The McGraw-Hill Companies, Inc. All rights reserved.

16/06/56. Databases. Databases. Databases The McGraw-Hill Companies, Inc. All rights reserved.

Database Design and the E-R Model (7.4, )

Database Design. Database Design I: The Entity-Relationship Model. Entity Type (con t) Representation in Relational Model.

Test Bank for A Guide to SQL 9th Edition by Pratt

File Processing Approaches

ER-to-Relational Mapping

Database Systems. Overview - important points. Lecture 5. Some introductory information ERD diagrams Normalization Other stuff 08/03/2015

Course Outline Faculty of Computing and Information Technology

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

Chapter 1 SQL and Data

Chapter 7: Entity-Relationship Model

Transcription:

Systems Analysis and Design Methods Chapter 7: Data Modeling and Analysis Multiple Choice Questions 1. Which of the following sentence is NOT correct about a logical model: A. is implementation dependent B. shows what a system is or does C. illustrates the essence of the system D. is a conceptual model 2. Which of the following sentence is NOT correct about a physical model: A. is implementation independent B. shows only what a system should do, not how it should do it C. is a conceptual model D. can only be used to represent a new system 3. Logical models: A. increase biases that are the result of the way the current system is implemented B. increase the risk of missing business requirements C. allow us to confuse the end users because they are so technical D. show what a system is or does 4. Physical models: A. can be biased based on the way the current system is implemented B. show what a system should do, not how it should do it C. describe how a system is implemented D. can include the technical jargon associated with the implementation of the system 7-1

5. An entity can be a class of: A. persons B. places C. objects D. all of the above 6. Which of the following consists of other attributes? A. a domain B. a compound attribute C. an entity existence D. a data type 7. A group of attributes that uniquely identifies an instance of an entity is called: A. an entity relationship B. a default value C. a concatenated key D. a domain The correct answer is C. 8. A natural business association that exists between one or more entities is known as: A. a domain B. an entity C. an associative entity D. a relationship 9. A binary relationship: A. can be also ternary at the same time B. has a degree of 2 C. has a cardinality of 2 D. is recursive 7-2

10. When each participating entity in a relationship has its own independent primary key, the relationship is known as: A. primary B. associative C. nonidentifying D. identifying The correct answer is C. 11. A relationship where many instances of one entity can be associated with many instances of another entity is known as: A. specific B. recursion C. redundant D. non-specific 12. A technique wherein attributes that are common to several types of an entity are grouped into their own entity called a supertype is called: A. recursion B. normalization C. generalization D. subsetting The correct answer is C. 13. An entity whose instances inherit some common attributes from another entity and then add other attributes that are unique to an instance of itself is known as: A. a subtype B. a compound type C. a complex type D. a supertype 7-3

14. During requirements analysis, what order of model development is used to arrive at the logical data model? A. context data model; fully attributed data model; key-based data model; normalized data model B. normalized data model; context data model; fully attributed data model; keybased data model C. normalized data model; key-based data model; fully attributed data model; context data model D. context data model; key-based data model; fully attributed data model; normalized data model 15. Which of the following is a technique for identifying entities? A. study existing forms B. interview users C. reverse engineer existing files and databases D. all the above 16. A true entity: A. must have many possible instances B. should have a meaningful name that is usually a noun C. should be defined in business terms D. all of the above 17. A code that uses blocks of numbers that are divided into groups that have some business meaning is known as a: A. serial code B. sequential code C. hierarchical code D. block code 7-4

18. Which of the following is a criteria for making a good data model? A. Simplicity B. Redundancy. C. Precise to accurately describe the business. D. Data attributes should be flexible and useful in multiple entities. 19. An entity is in second normal form if: A. all the values of nonprimary keys are dependent on the full primary key. B. any nonkey attributes that are dependent on only part of the primary key should be moved to any entity where that partial key is the actual full key. C. it must already be in first normal form. D. all of the above. 20. A table in which rows indicate entities (and possible attributes) and the columns indicate locations, and the cells indicate the document level of access including create, read, update or delete, is known as: A. an entity relationship table B. data-to-location CRUD matrix C. a decision table D. a normalization table True or False Questions 21. Models are used in systems analysis and design to help structure unstructured problems. 22. A physical model is also known as an essential model, conceptual model and business model. A logical model is also known as an essential model, conceptual model and business model. 7-5

23. Logical models are implementation dependent. Logical models are implementation independent. 24. Logical models are also known as implementation models and technical models. Physical models are also known as implementation models and technical models. 25. Logical models allow us to communicate with end users in non-technical or less technical languages. Thus, we don't lose business requirements in the technical jargon of the computing discipline. 26. Data modeling is also sometimes known as conceptual business modeling. Data modeling is also sometimes known as information modeling. 27. An exigency is something about which the business needs to store data. An entity is something about which the business needs to store data. 28. An attribute is also known as an element, a property or a field. 7-6

29. The value type of an attribute defines what type of data can be stored in that attribute. The data type of an attribute defines what type of data can be stored in that attribute. 30. The default value for an attribute is the value that will be recorded if not specified by the user. 31. A condensed key is a group of attributes that uniquely identifies an instance of an entity. A concatenated key is a group of attributes that uniquely identifies an instance of an entity. 32. An alternate key is also known as a primary key. An alternate key is also known as a secondary key. 33. A relationship may represent an event that links the entities or merely a logical affinity that exists between the entities. 34. Concatenability defines the minimum and maximum number of occurrences of one entity that may be related to a single occurrence of another entity. Cardinality defines the minimum and maximum number of occurrences of one entity that may be related to a single occurrence of another entity. 7-7

35. Instances within an entity may not have a relationship with other instances in the same entity. A recursive relationship identifies a relationship that may exist between different instances of the same entity. 36. A foreign key is a primary key of one entity that is contributed to another entity to identify instances of a relationship. 37. Identifying relationships are those in which the child entity contributes its secondary key to become part of the parent entity. Identifying relationships are those in which the parent entity contributes its primary key to become part of the primary key of the child entity. 38. A many-to-many relationship is one in which many instances of one entity are associated with many instances of another entity. 39. An entity subtype is an entity whose instances store attributes that are common to one or more entity supertypes. An entity supertype is an entity whose instances store attributes that are common to one or more entity subtypes. 40. The data model for a single information system is usually called the enterprise data model. The data model for a single information system is usually called an application data model. An enterprise data model typically identifies only the most fundamental of entities of the enterprise. 7-8

41. The requirements analysis results in a physical data model that is developed in stages as follows: (1) context data model; (2) key-based data model; (3) fully attributed data model; and (4) the normalized data model. The requirements analysis results in a logical data model that is developed in stages as follows: (1) context data model; (2) key-based data model; (3) fully attributed data model; and (4) the normalized data model. 42. Another name for the physical data model is the database schema. 43. The value of a key cannot be null. 44. Block codes are similar to serial codes except that block numbers are divided into groups that have some business meaning. In significant position codes, each digit or group of digits describes a measurable or identifiable characteristic of the entity instance. Hierarchical codes provide a top-down interpretation for an entity instance by factoring an item into its group, subgroup and so forth. 45. A good data model is complex because it has to represent so much information about a company in one place. A good data model is simple. 46. Data analysis is a process that prepares a data model for implementation as a simple, nonredundant, flexible and adaptable database through a technique called normalization. 7-9

47. Generalization is a data analysis technique that organizes data domains such that they have data integrity through redundancy, stability and explicit enumeration. Normalization is a data analysis technique that organizes data attributes such that they are grouped to form nonredundant, stable, flexible and adaptable entities. Generalization is a technique wherein the attributes that are common to several types of an entity are grouped into their own entity, called a supertype. 48. An entity is in third normal form (3NF) if there are no attributes that can have more than one value for a single instance of the entity. Any attributes that have multiple values actually describe a separate entity, possibly an entity and relationship. This step must be done prior to doing second or first normal forms (2NF and 1NF). An entity is in first normal form (1NF) if there are no attributes that can have more than one value for a single instance of the entity. Any attributes that have multiple values actually describe a separate entity, possibly an entity and relationship. 49. Derived attributes are those attributes whose values make them good candidate keys for the entity. Derived attributes are those whose values can either be calculated from other attributes or derived through logic from the values of other attributes. 7-10