PESIT Bangalore South Campus

Similar documents
Chapter 2 Database System Concepts and Architecture

Introduction to Database Systems

Chapter 1 Databases and Database Users

Copyright 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley. Chapter 1 Outline

Database Systems. Session 1 Main Theme Introduction to Database Systems Dr. Jean-Claude Franchitti

Database System. Session 1 Main Theme Introduction to Database Systems Dr. Jean-Claude Franchitti

DATABASE SYSTEM CONCEPTS AND ARCHITECTURE CHAPTER 2

COIS Databases

Introduction: Database management system

Introduction. Introduction: Database management system. Introduction: DBS concepts & architecture. Introduction: DBS versus File system

What is a database? COSC 304 Introduction to Database Systems. Database Introduction. Example Problem. Databases in the Real-World

1 File Processing Systems

Chapter 3. Data Modeling Using the Entity-Relationship (ER) Model

Database Management Systems

Concepts of Database Management Seventh Edition. Chapter 9 Database Management Approaches

Database System Architecture & System Catalog Instructor: Mourad Benchikh Text Books: Elmasri & Navathe Chap. 17 Silberschatz & Korth Chap.

Chapter 3. Database Environment - Objectives. Multi-user DBMS Architectures. Teleprocessing. File-Server

not necessarily strictly sequential feedback loops exist, i.e. may need to revisit earlier stages during a later stage

IT2305 Database Systems I (Compulsory)

DATABASE MANAGEMENT SYSTEMS. Question Bank:

Entity-Relationship Model

Chapter 1: Introduction

Database System Concepts

Chapter 10 Practical Database Design Methodology and Use of UML Diagrams

Basic Concepts of Database Systems

CHAPTER 2 DATABASE MANAGEMENT SYSTEM AND SECURITY

International Journal of Engineering Technology, Management and Applied Sciences. November 2014, Volume 2 Issue 6, ISSN

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

ECS 165A: Introduction to Database Systems

COURSE NAME: Database Management. TOPIC: Database Design LECTURE 3. The Database System Life Cycle (DBLC) The database life cycle contains six phases;

IT2304: Database Systems 1 (DBS 1)

Author: Abhishek Taneja

Chapter 1: Introduction. Database Management System (DBMS)

Module 1: Getting Started with Databases and Transact-SQL in SQL Server 2008

Relational Database Basics Review

B.Sc (Computer Science) Database Management Systems UNIT-V

Software Engineering. System Models. Based on Software Engineering, 7 th Edition by Ian Sommerville

Object Oriented Databases. OOAD Fall 2012 Arjun Gopalakrishna Bhavya Udayashankar

DATABASES AND DATABASE USERS

Foundations of Information Management

Chapter 1: Introduction. Database Management System (DBMS) University Database Example

12 File and Database Concepts 13 File and Database Concepts A many-to-many relationship means that one record in a particular record type can be relat

Databases What the Specification Says

Chapter 1: Introduction

Chapter 6 FOUNDATIONS OF BUSINESS INTELLIGENCE: DATABASES AND INFORMATION MANAGEMENT Learning Objectives

TIM 50 - Business Information Systems

Bridge from Entity Relationship modeling to creating SQL databases, tables, & relations

Foundations of Business Intelligence: Databases and Information Management

ICS 434 Advanced Database Systems

Introduction to database management systems

Writing Queries Using Microsoft SQL Server 2008 Transact-SQL

Introduction to Database Systems. Chapter 1 Introduction. Chapter 1 Introduction

DATABASE MANAGEMENT SYSTEM

VALLIAMMAI ENGNIEERING COLLEGE SRM Nagar, Kattankulathur

Chapter 7 Data Modeling Using the Entity- Relationship (ER) Model

Chapter 1 File Organization 1.0 OBJECTIVES 1.1 INTRODUCTION 1.2 STORAGE DEVICES CHARACTERISTICS

MIS S S t S ru r ct u ur u e r & & Pl P a l nn n i n n i g

The Entity-Relationship Model

Course MIS. Foundations of Business Intelligence

æ A collection of interrelated and persistent data èusually referred to as the database èdbèè.

COMP5138 Relational Database Management Systems. Databases are Everywhere!

CS587 Project final report

Writing Queries Using Microsoft SQL Server 2008 Transact-SQL

Database Systems. Lecture 1: Introduction

Demystified CONTENTS Acknowledgments xvii Introduction xix CHAPTER 1 Database Fundamentals CHAPTER 2 Exploring Relational Database Components

Oracle Data Integrator: Administration and Development

Lesson 8: Introduction to Databases E-R Data Modeling

DBMS Questions. 3.) For which two constraints are indexes created when the constraint is added?

Oracle BI 11g R1: Build Repositories

C/S Basic Concepts. The Gartner Model. Gartner Group Model. GM: distributed presentation. GM: distributed logic. GM: remote presentation

A Multidatabase System as 4-Tiered Client-Server Distributed Heterogeneous Database System

Cloud Computing and Advanced Relationship Analytics

Lesson 4 Web Service Interface Definition (Part I)

Data Analysis 1. SET08104 Database Systems. Napier University

Databases and BigData

Software Architecture Document

Design of Data Archive in Virtual Test Architecture

Unit 2.1. Data Analysis 1 - V Data Analysis 1. Dr Gordon Russell, Napier University

MySQL for Beginners Ed 3

1. INTRODUCTION TO RDBMS

Foundations of Business Intelligence: Databases and Information Management

Database Systems Introduction Dr P Sreenivasa Kumar

COMP 378 Database Systems Notes for Chapter 7 of Database System Concepts Database Design and the Entity-Relationship Model

Chapter 8 The Enhanced Entity- Relationship (EER) Model

STRATEGIES ON SOFTWARE INTEGRATION

D83167 Oracle Data Integrator 12c: Integration and Administration

Oracle Warehouse Builder 10g

A Review of Database Schemas

Oracle Data Integrator 12c: Integration and Administration

CSE 233. Database System Overview

NoSQL systems: introduction and data models. Riccardo Torlone Università Roma Tre

Oracle Data Integrator 11g: Integration and Administration

CHAPTER 5: BUSINESS ANALYTICS

Course: CSC 222 Database Design and Management I (3 credits Compulsory)

How to Choose Between Hadoop, NoSQL and RDBMS

A framework for web-based product data management using J2EE

Chapter 9 Political Enterprise Database Management System (PDBHS or PEDBHS)

Transcription:

USN 1 P E PESIT Bangalore South Campus Hosur road, 1km before Electronic City, Bengaluru -100 Department of Information Science & Engineering INTERNAL ASSESSMENT TEST 1 Date : 17/08/2016 Max Marks: 50 Subject & Code : DBMS/ 10CS54 Section: 5 th A & B Name of faculty: Mr. Vijay Sagar Time: 11:30AM 1:00PM Note: ANSWER ANY FIVE FULL QUESTIONS a) Discuss any 3 characteristics of the database approach. (7 Marks) The main characteristics of the database approach versus the file-processing approach are the following: Self-describing nature of a database system Insulation between programs and data, and data abstraction Support of multiple views of the data Sharing of data and multiuser transaction processing Self-Describing Nature of a Database System A fundamental characteristic of the database approach is that the database system contains not only the database itself but also a complete definition or description of the database structure and onstraintsthis definition is stored in the DBMS catalog, which contains information such as the structure of each file, the type and storage format of each data item, and various constraints on the data. The information stored in the catalog is called meta-data.

Insulation between Programs and Data,and Data Abstraction In traditional file processing, the structure of data files is embedded in the application programs, so any changes to the structure of a file may require changing all programs that access that file. By contrast, DBMS access programs do not require such changes in most cases. The structure of data files is stored in the DBMS catalog separately from the access programs. We call this property program-data independence. The characteristic that allows program-data independence and program-operation independence is called data abstraction. A DBMS provides users with a conceptual representation of data that does not include many of the details of how the data is stored or how the operations are implemented. Support of Multiple Views of the Data A database typically has many types of users, each of whom may require a different perspective or view of the database. A view may be a subset of the database or it may contain virtual data that is derived from the database files but is not explicitly stored. Some users may not need to be aware of whether the data they refer to is stored or derived. A multiuser DBMS whose users have a variety of distinct applications must provide facilities for defining multiple views b) What are the implicit properties of a database? (3 Marks) A database has the following implicit properties: >A database represents some aspect of the real world, sometimes called the miniworld or the universe of discourse (UoD). Changes to the miniworld are reflected in the database. >A database is a logically coherent collection of data with some inherent meaning. A random assortment of data cannot correctly be referred to as a database. > A database is designed, built, and populated with data for a specific purpose. It has an intended group of users and some preconceived applications in which these users are interested.

a) Briefly describe any four advantages of the DBMS approach. (8 Marks) Controlling Redundancy In traditional software development utilizing file processing, every user group maintains its own files for handling its data-processing applications. This redundancy in storing the same data multiple times leads to several problems. First, there is the need to perform a single logical update times: once for each file where student data is recorded. This leads to duplication of effort. Second, storage space is wasted when the same data is stored repeatedly, and this problem may be serious for large databases. Third, files that represent the same data may become inconsistent. In the database approach, the views of different user groups are integrated during database design. Ideally, we should have a database design that stores each logical data item in only one place in the database. b) Name Actors on the scene. (2 Marks) 1. Database Administrators 2. Database Designers 3. End Users(Casual,Naïve and parametric) 4. System Analysts and Application Programmers a) What is a data model? Discuss the categories of data models. (6 Marks) Criteria for classification: Data model. Relational data model SQL systems, widely used.

Object data model, defines a database in terms of objects, their properties, and their operations. Document-based, Graph-based, Column-based & key-value data models Big Data Systems and NoSQL systems. Cost. 2. Number of users. 3. Number of sites. Homogeneous DDBMSs Heterogeneous DDBMSs The relational data model represents a database as a collection of tables,where each table can be stored as a separate file. > The object data model defines a database in terms of objects, their properties, and their operations. Objects with the same structure and behavior belong to a class, and classes are organized into hierarchies. > The key-value data model associates a unique key with each value (which can be a record or object) and provides very fast access to a value given its key. > The graph data model stores objects as graph nodes and relationships among objects as directed graph edges > Some experimental DBMSs are based on the XML model called as tree-structured data model. b) Briefly explain the concept of data independence. (4 Marks) We can define two types of data independence: 1. Logical data independence is the capacity to change the conceptual schema without having to change external schemas or application programs. We may change the conceptual schema to expand the database (by adding a record type or data item), to change constraints, or to reduce the database (by removing a record type or data item). In the last case, external schemas that refer only to the remaining data should not be affected.

2. Physical data independence is the capacity to change the internal schema without having to change the conceptual schema. Hence, the external schemas need not be changed as well. Changes to the internal schema may be needed because some physical files were reorganized for example, by creating additional access structures to improve the performance of retrieval or update. If the same data as before remains in the database, we should not have to change the conceptual schema. 4a) With a neat diagram illustrate the main phases of database design. (7 Marks) A simplified diagram to illustrate the main phases of database design

b) Differentiate between composite and multi-valued attributes. (3 Marks) Composite attributes can be divided into smaller subparts, which represent more basic attributes with independent meanings. Composite attributes can form a hierarchy; for example, Street_address can be further subdivided into three simple component. A multi-valued attribute has different numbers of values for the attribute. For example, the Colors attribute of a car may be restricted to have between one and two values, if we assume that a car can have two colors at most. 5.a) With a neat diagram explain Three-Tier and n-tier architecture for web application (5 Marks) Logical three-tier client/server architecture

The three-tier architecture, adds an intermediate layer between the client and the database server and is usually used for web applications. This intermediate layer or middle tier is called the application server or the Web server, depending on the application. This server plays an intermediary role by running application programs and storing business rules (procedures or constraints) that are used to access data from the database server. It can also improve database security by checking a client s credentials before forwarding a request to the database server. Clients contain user interfaces and Web browsers. The intermediate server accepts requests from the client, processes the request and sends database queries and commands to the database server, and then acts as a conduit for passing (partially) processed data from the database server to the clients, where it may be processed further and filtered to be presented to the users. Thus, the user interface, application rules, and data access act as the three tiers. It is possible to divide the layers between the user and the stored data further into finer components, thereby giving rise to n-tier architectures, where n may be four or five tiers. b) Discuss any 5 DBMS interfaces. (5 Marks) Menu-based Interfaces for Web Clients or Browsing These interfaces present the user with lists of options (called menus) that lead the user through the formulation of a request. Forms-based Interfaces. A forms-based interface displays a form to each user.users can fill out all of the form entries to insert new data, or they can fill out only certain entries, in which case the DBMS will retrieve matching data for the remaining entries. Forms are usually designed and programmed for naive users as interfaces to canned transactions. Graphical User Interfaces. A GUI typically displays a schema to the user in diagrammatic form. The user then can specify a query by manipulating the diagram. In many cases, GUIs utilize both menus and forms.

Natural Language Interfaces. These interfaces accept requests written in English or some other language and attempt to understand them. A natural language interface usually has its own schema, which is similar to the database conceptual schema, as well as a dictionary of important words. Keyword-based Database Search. These are somewhat similar to Web search engines, which accept strings of natural language like English words and match them with documents at specific sites or Web pages on the Web at large for engines like Google. 6. Briefly describe the following: a) The degree of a relationship type. whenever an attribute of one entity type refers to another entity type, some relationship exists. A relationship type R among n entity types E1, E2,..., En defines a set of associations or a relationship set among entities from these entity types. b) Recursive Relationship with example. The same entity type participates more than once in a relationship type in different roles. In such cases the role name becomes essential for distinguishing the meaning of the role that each participating entity plays. Such relationship types are called recursive relationships or self-referencing relationships c) Weak Entity Types. An entity that does not have a key attribute A weak entity must participate in an identifying relationship type with an owner or identifying entity type Entities are identified by the combination of: A partial key of the weak entity type The particular entity they are related to in the identifying entity type

d) Min, Max Notations. Specified on each participation of an entity type E in a relationship type R Specifies that each entity e in E participates in at least min and at most max relationship instances in R Default(no constraint): min=0, max=n Must have min max, min 0, max 1 Derived from the knowledge of mini-world constraints. (10 Marks)