- Prof.

Ishani Saha
Computer Department
MPSTME (NMIMS)
Description of ICA Marks TERM WORK Marks
Class Test 1 10 Assignment 5
Class Test 2 10 Lab Work 10
Term Work 30 Project 10
Total Marks : 50 Quiz 5
Total Marks : 30
Outcomes: After Completion of the Course, students would be able to:
1. Understand the terminology, features, types, advantages and characteristics embodied in database systems.
2. Design database system architecture and data models
3. Formulate and solve problems using structure query languages with optimization
4. Understand indexing techniques, concurrency control techniques, database security advanced concepts.

Detailed Syllabus:
Unit Description Duration

1 Introduction: Introduction to Database. Hierarchical, Network and Relational Models. 3

2 Database system architecture: Data Abstraction, Data Independence, Data Definition Language (DDL), Data 3
Manipulation Language (DML).

3 Data models: Entity-relationship model, network model, relational and object oriented data models, integrity 6
constraints, data manipulation operations.
4 Relational query languages: Relational algebra, Tuple and domain relational calculus, SQL3, DDL and DML constructs, 6
Open source and Commercial DBMS - MYSQL, ORACLE, DB2, SQL server.
5 Relational database design: Domain and data dependency, Armstrong's axioms, Functional Dependencies, Normal 5
forms, Dependency preservation, Lossless design.
6 Query processing and optimization: Evaluation of relational algebra expressions, Query equivalence, Join strategies, 5
Query optimization algorithms.
7 Storage strategies: Indices, B-trees, Hashing. 3
8 Transaction processing: Concurrency control, ACID property, Serializability of scheduling, Locking and timestamp 6
based schedulers, Multi-version and optimistic Concurrency Control schemes, Database recovery.
9 Database Security: Authentication, Authorization and access control, DAC, MAC and RBAC models, Intrusion 4
detection, SQL injection.
10 Introduction to Advanced topics: Object oriented and object relational databases, Logical databases, Web databases, 4
Distributed databases, Data warehousing and data mining, Unstructured database, Dataswarm
  Total 45
Text Books:
Abraham Silberschatz, Henry F. Korth and S. Sudarshan, “Database System Concepts”, McGraw Hill
Education, 6th Edition,2013

Reference Books:
R. Elmasri and S. Navathe, “Fundamentals of Database Systems.”, Pearson Education, 7 th Edition,
2017
 Chapter 1
• The Need for Databases
• Data Models
 Database Management System (DBMS)
• DBMS contains information about a particular enterprise
• Collection of interrelated data
• Set of programs to access the data
• An environment that is both convenient and efficient to use
• Database Applications:
• Banking: transactions
• Airlines: reservations, schedules
• Universities: registration, grades
• Sales: customers, products, purchases
• Online retailers: order tracking, customized recommendations
• Manufacturing: production, inventory, orders, supply chain
• Human resources: employee records, salaries, tax deductions
• Databases can be very large.
• Databases touch all aspects of our lives
 University Database Example
• Application program examples
• Add new students, instructors, and courses
• Register students for courses, and generate class rosters
• Assign grades to students, compute grade point averages (GPA) and generate
transcripts
Drawbacks of using file systems to store
data
• Data redundancy and inconsistency
• Multiple file formats, duplication of information in different files
• Difficulty in accessing data
• Need to write a new program to carry out each new task
• Data isolation
• Multiple files and formats
• Integrity problems
• Integrity constraints (e.g., account balance > 0) become “buried” in program code
rather than being stated explicitly
• Hard to add new constraints or change existing ones
 Drawbacks of using file systems to store
data (cont.)
• Atomicity of updates
• Failures may leave database in an inconsistent state with partial updates carried out
• Example: Transfer of funds from one account to another should either complete or not happen at all
• Concurrent access by multiple users
• Concurrent access needed for performance
• Uncontrolled concurrent accesses can lead to inconsistencies
• Example: Two people reading a balance (say 100) and updating it by withdrawing money (say 50 each) at the same
time
• Security problems
• Hard to provide user access to some, but not all, data

Database systems offer solutions to all the above problems

10
 The Hierarchical Model
• Developed in the 1960s to manage large amounts of data for complex
manufacturing projects
• Basic logical structure is represented by an upside-down “tree”

11
The Hierarchical Model (continued)

12
 The Hierarchical Model (continued)
• The hierarchical structure contains levels, or segments
• Depicts a set of one-to-many (1:M) relationships between a parent
and its children segments
• Each parent can have many children
• Each child has only one parent

13
 The Hierarchical Model (continued)
• Advantages
• Many of the hierarchical data model’s features formed the foundation for
current data models
• Its database application advantages are replicated, albeit in a different form,
in current database environments
• Generated a large installed (mainframe) base, created a pool of programmers
who developed numerous tried-and-true business applications

14
 The Hierarchical Model (continued)
• Disadvantages
• Complex to implement
• Difficult to manage
• Implementation limitations
• Lack of standards

15
 The Network Model
• It was in 1971 that the Conference on Data System Languages or CODASYL
officially or formally defined the Network model. The network databases
arrange its data as a directed graph
• Created to
• Represent complex data relationships more effectively
• Improve database performance
• Impose a database standard

16
 The Network Model (continued)
• Schema Data Definition Language (DDL)
• Enables database administrator to define schema components
• Subschema DDL
• Allows application programs to define database components that will be used
• DML
• Works with the data in the database

17
 The Network Model (continued)
• Resembles hierarchical model
• Collection of records in 1:M relationships
• Set
• Relationship
• Composed of at least two record types
• Owner
• Equivalent to the hierarchical model’s parent
• Member
• Equivalent to the hierarchical model’s child

18
The Network Model (continued)

19
 The Network Model (continued)
Advantages

• Multi-parent support.
• Somewhat same simplicity as the hierarchical model.
• More useful than the hierarchical data model.
• Deals with even larger amounts of information than the hierarchical model.
• Promotes data integrity.
• Data independence.
• Improved data access.
 The Network Model (continued)
• Disadvantages
• Too cumbersome
• Data relationships must be predefined.
• Much more complex than the hierarchical data model.
• Users are still required to know the physical representation of the database
• Information can be related in various and complicated ways.

21
 The Relational Model
• Developed by Codd (IBM) in 1970
• Conceptually simple
• Computers lacked power to implement the relational model
• Today, microcomputers can run sophisticated relational database
software

22
 The Relational Model (continued)
• Relational Database Management System (RDBMS)
• Performs same basic functions provided by hierarchical and network
DBMS systems, in addition to a host of other functions
• Most important advantage of the RDBMS is its ability to hide the
complexities of the relational model from the user

23
 The Relational Model (continued)
• Table (relations)
• Matrix consisting of a series of row/column intersections
• Related to each other through sharing a common entity characteristic
• Relational diagram
• Representation of relational database’s entities, attributes within those
entities, and relationships between those entities

24
 The Relational Model
(continued)
• Relational Table
• Stores a collection of related entities
• Resembles a file
• Relational table is purely logical structure
• How data are physically stored in the database is of no concern to
the user or the designer
• This property became the source of a real database revolution

25
The Relational Model (continued)

26
The Relational Model (continued)

27
 The Relational Model (continued)
• Rise to dominance due in part to its powerful and flexible query
language
• Structured Query Language (SQL) allows the user to specify what
must be done without specifying how it must be done
• SQL-based relational database application involves:
• User interface
• A set of tables stored in the database

28
 Relational Model
• All the data is stored in various tables.
• Example of tabular data in the relational model
Relational Model
 The Entity Relationship Model
• Widely accepted and adapted graphical tool for data modeling
• Introduced by Chen in 1976
• Graphical representation of entities and their relationships in a
database structure

31
 The Entity Relationship Model (continued)
• Entity relationship diagram (ERD)
• Uses graphic representations to model database components
• Entity is mapped to a relational table
• Entity instance (or occurrence) is row in table
• Entity set is collection of like entities
• Connectivity labels types of relationships
• Diamond connected to related entities through a relationship line

32
The Entity Relationship Model (continued)

33
The Entity Relationship Model (continued)

34
 The Object Oriented Model
• Modeled both data and their relationships in a single structure known
as an object
• Object-oriented data model (OODM) is the basis for the object-
oriented database management system (OODBMS)
• OODM is said to be a semantic data model

35
 The Object Oriented Model (continued)
• Object described by its factual content
• Like relational model’s entity
• Includes information about relationships between facts within object, and
relationships with other objects
• Unlike relational model’s entity
• Subsequent OODM development allowed an object to also contain all
operations
• Object becomes basic building block for autonomous structures

36
 The Object Oriented Model (continued)
• Object is an abstraction of a real-world entity
• Attributes describe the properties of an object
• Objects that share similar characteristics are grouped in classes
• Classes are organized in a class hierarchy
• Inheritance is the ability of an object within the class hierarchy to
inherit the attributes and methods of classes above it

37
END