Lecture 1

Kazi Rifat Ahmed

Lecturer
Department of Software Engineering
Daffodil International University
 ● Introduction
● Data & Information
● Difference of Data &
Information
● File Processing System
Outline ● View of Data
● Level of Abstractions
● Instances & Schemas
● Three Schema Architecture
● Data Independence
● Data Models
● Components of Database
● Database Administrator
Data & Information
● Data is a collection of raw, unorganised facts and details like
text, observations, figures, symbols and descriptions of
things etc.
● In other words, data does not carry any specific purpose and
has no significance by itself.
● Moreover, data is measured in terms of bits and bytes –
which are basic units of information in the context of
computer storage and processing.
Data & Information (Con.)
● Information is processed, organised and structured data.
● It provides context for data and enables decision making.
● For example, a single customer’s sale at a restaurant is data
– this becomes information when the business is able to
identify the most popular or least popular dish.
Data & Information (Con.)
Math English Science
Student Score Score Score Student

Alex 78 92 85 Alex

Sarah 89 78 95 Sarah

Chris 95 88 92 Chris
Difference Between Data & Information
Data Information

Data is unorganised and unrefined facts Information comprises processed,

organised data presented in a
meaningful context

Data is an individual unit that contains raw Information is a group of data that
materials which do not carry any specific collectively carries a logical
meaning. meaning.

Data doesn’t depend on information. Information depends on data.

Raw data alone is insufficient for decision Information is sufficient for decision
making making
Database Management System
● A database-management system (DBMS) is a collection of
interrelated data and a set of programs to access those data.
● The collection of data, usually referred to as the database,
contains information relevant to an enterprise.
● The primary goal of a DBMS is to provide a way to store and
retrieve database information that is both convenient and
efficient.
Database Management System (Con.)
Database Management System (Con.)
● Organized collection of logically related data is called
Database.
● In a relational database, a data item is called a column or
attribute, a record is called a row or tuple, and a file is called
a table.
Database Management System (Con.)
The primary purpose of a DBMS is :
● It provides a systematic method of creating, updating,
storing, and retrieving the data stored in a database.
● It enables end users and application programmers to share
data, and it enables data to be shared among multiple
applications.
● It provides facilities for controlling data access, enforcing
data integrity, managing concurrency control, and restoring a
database.
Database-System Applications
Databases are widely used. Here are some representative
applications:
● Enterprise Information ● Universities
○ Sales ● Airlines
○ Accounting ● Telecommunication
○ Manufacturing
○ Online retailers
● Banking and Finance
○ Credit card
transactions
○ Finance
Database Management System (Cont.)
File Processing System
● A file processing system is a collection of programs that store
and manage files in computer hard-disk.
● File processing system has more data redundancy, less data
redundancy in dbms.
● File processing system provides less flexibility in accessing
data, whereas dbms has more flexibility in accessing data.
File Processing System (Cont.)
File Processing System Problems
● Data redundancy: Data redundancy refers to the duplication of
data. Data redundancy often leads to higher storage costs and poor
access time.
● Data inconsistency: Data redundancy leads to data inconsistency,
A student's address is stored twice, potentially leading to data
inconsistency if it is changed at one place and not on all records, as
demonstrated in the example given.
● Data Isolation: Because data are scattered in various files, and files
may be in different formats, writing new application programs to
retrieve the appropriate data is difficult.
● Dependency on application programs: Changing files would lead
to change in application programs.
● Data Security: Data should be secured from unauthorised access,
for example a student in a college should not be able to see the
payroll details of the teachers.
View of Data
❖ A database system is a collection of interrelated data and a
set of programs that allow users to access and modify these
data.
❖ A major purpose of a database system is to provide users
with an abstract view of the data.
❖ That is, the system hides certain details of how the data are
stored and maintained.
View of Data (Cont.)
Data Abstraction:
Data retrieval from database should be made easy & efficient
since database user are not computer trained .
So the developer hide the complexity from user for several level
of abstraction.
View of Data (Cont.)
● Physical Level
● Logical Level
● View Level
View of Data (Cont.)
❏ Physical level: (Physical schema describes the files
and indexes used.)
❏ The lowest level of abstraction describes how the data
are actually stored.
❏ The physical level describes complex low-level data
structures in detail.
❏ The design of data structure is described at this level
called physical schema.
❏ It specify that records are stored in either as pages.
View of Data (Cont.)
❏ Logical level: (Conceptual schema defines logical
structure)
❏ This is middle level of abstraction and it describes what
data are stored in the database, and what relationship
exist among the those data, there is only one schemas
only for one database.
❏ The logical level thus describes the entire database in
terms of a small number of relatively simple structures.
❏ The logical level of abstraction is used by database
administrator, Who decide what information has to kept
inside database.
View of Data (Cont.)
❏ View level.(External schemata describe how users see
the data. )
❏ The highest level of abstraction describes only part of the
entire database. Even though the logical level uses
simpler structures, complexity remains because of the
variety of information stored in a large database.
❏ Many users of the database system do not need all this
information; instead, they need to access only a part of
the database. The view level of abstraction exists to
simplify their interaction with the system. The system
may provide many views for the same database.
Level of Abstraction (View of Data)
➢ Physical level: It describes how a record (e.g., customer) is
stored.
➢ Logical level: describes data stored in database, and the
relationships among the data.
type customer = record
name : string;
street : string;
city : integer;
end;
➢ View level: application programs hide details of data types.
Views can also hide information (e.g., salary) for security
Level of Abstraction (View of Data)
➢ Physical level: It describes how a record (e.g., customer) is
stored.
➢ Logical level: describes data stored in database, and the
relationships among the data.
type customer = record
name : string;
street : string;
city : integer;
end;
➢ View level: application programs hide details of data types.
Views can also hide information (e.g., salary) for security
Instances and Schema
❏ Schema – Design of a database is called the schema.
Schema is of three types: Physical schema, logical schema
and view schema.
❏ For example: In the following diagram, we have a schema
that shows the relationship between three tables: Course,
Student and Section. The diagram only shows the design of
the database, it doesn’t show the data present in those
tables. Schema is only a structural view (design) of a
database as shown in the diagram below.
Instances and Schemas (Cont.)
Instances and Schemas (Cont.)
➢ The design of a database at physical level is called physical
schema, how the data stored in blocks of storage is
described at this level.
➢ Design of database at logical level is called logical schema,
programmers and database administrators work at this level,
at this level data can be described as certain types of data
records gets stored in data structures, however the internal
details such as implementation of data structure is hidden at
this level (available at physical level).
➢ Design of database at view level is called view schema. This
generally describes end user interaction with database
systems.
Instances and Schemas (Cont.)
➔ Instance –The data stored in database at a particular moment of
time is called instance of database. Database schema defines the
variable declarations in tables that belong to a particular database;
the value of these variables at a moment of time is called the
instance of that database.
➔ For example, let's say we have a single table student in the
database, today the table has 100 records, so today the instance of
the database has 100 records. Let's say we are going to add
another 100 records in this table by tomorrow so the instance of
database tomorrow will have 200 records in table. In short, at a
particular moment the data stored in database is called the
instance, that changes over time when we add or delete data from
the database.
Three-Schema Architecture
➢ Internal schema at the internal level to describe physical
storage structures and access paths (e.g indexes).
○ Typically uses a physical data model.
➢ Conceptual schema at the conceptual level to describe the
structure and constraints for the whole database for a
community of users.
○ Uses a conceptual or an implementation data model.
➢ External schemas at the external level to describe the
various user views.
○ Usually uses the same data model as the conceptual schema
Three-Schema Architecture (Cont.)
Data Independence
○ Data independence can be explained using the three-schema
architecture.
○ Data independence refers characteristic of being able to
modify the schema at one level of the database system
without altering the schema at the next higher level.
Data Independence (Cont.)
Logical Data Independence:
○ Logical data independence refers characteristic of being able
to change the conceptual schema without having to change
the external schema.
○ Logical data independence is used to separate the external
level from the conceptual view.
○ If we do any changes in the conceptual view of the data,
then the user view of the data would not be affected.
○ Logical data independence occurs at the user interface level.
Data Independence (Cont.)
Physical Data Independence:
○ Physical data independence can be defined as the capacity to
change the internal schema without having to change the
conceptual schema.
○ If we do any changes in the storage size of the database system
server, then the Conceptual structure of the database will not be
affected.
○ Physical data independence is used to separate conceptual
levels from the internal levels.
○ Physical data independence occurs at the logical interface level.
Data Independence (Cont.)
Database Architecture
Database Architecture (Cont.)
Database applications are usually partitioned into two or three
parts.
❏ In a two-tier architecture, the application resides at the
client machine, where it invokes database system
functionality at the server machine through query
language statements. Application program interface
standards like ODBC and JDBC are used for interaction
between the client and the server.
Database Architecture (Cont.)
❏ In contrast, in a three-tier architecture, the client machine acts
as merely a front end and does not contain any direct database
calls. Instead, the client end communicates with an application
server, usually through a forms interface.
❏ The application server in turn communicates with a database
system to access data. The business logic of the application,
which says what actions to carry out under what conditions, is
embedded in the application server, instead of being
distributed across multiple clients. Three-tier applications are
more appropriate for large applications, and for applications
that run on the World Wide Web.
Data Models
➔ A collection of tools for describing
◆ Data
◆ Data relationships
◆ Data semantics
◆ Data constraints
➔ Relational model : The relational model uses a collection of tables to represent both data and
the relationships among those data.
➔ Entity-Relationship data model (mainly for database design) : The E-R data model is
based on a perception of a real world that consists of a collection of basic objects, called
entities and of relationships among these objects.
➔ Object-based data models (Object-oriented and Object-relational)
➔ Semi-structured data model (XML)
➔ Other older models:
◆ Network model
◆ Hierarchical model
Three Important Terms:
❖ Entity: Any object, exists physically or conceptually.
❖ Attribute: Property or characteristic of entity.
❖ Relationship: Association or link b/w two entities.

* These 3 terms make Entity-Relationship

Model.
Components of the Database
➢ User: People who interact with the database.
○ Application Programmers
○ End users
○ Data Administrator
➢ Software: Lies between the stored data and the users.
○ DBMS
○ Application Software
○ User Interface
Components of the Database
➢ Hardware: Physical device on which database resides.
○ Computers
○ Hard Drives
○ Cables, etc.
➢ Data: Numbers, characters, pictures.
○ 1001, Juan Dela Cruz, Student.
Database Administrator
One of the main reasons for using DBMSs is to have central
control of both the data and the programs that access those
data. A person who has such central control over the system is
called a database administrator (DBA). The functions of a
DBA include:
● Schema definition: The DBA creates the original database
schema by executing a set of data definition statements in
the DDL.
● Storage structure and access-method definition.
Database Administrator
● Schema and physical-organization modification: The DBA carries out
changes to the schema and physical organization to reflect the changing needs of
the organization, or to alter the physical organization to improve performance.
● Granting of authorization for data access:. By granting different types of
authorization, the database administrator can regulate which parts of the
database various users can access.
● Routine maintenance. Examples of the database administrator’s routine
maintenance activities are:
○ Periodically backing up the database, either onto tapes or onto remote servers, to prevent loss of data in
case of disasters such as flooding.
○ Ensuring that enough free disk space is available for normal operations, and upgrading disk space as
required.
○ Monitoring jobs running on the database and ensuring that performance is not degraded by very
expensive tasks submitted by some users.
References
1. https://byjus.com/biology/difference-between-data-and-information/
2. https://medium.com/@rohanrpatil20/file-processing-system-database-manage
ment-system-40167a60f4ae#:~:text=A%20file%20processing%20system%2
0is,more%20flexibility%20in%20accessing%20data
.
3. https://beginnersbook.com/2015/04/dbms-vs-file-system/
4. https://www.javatpoint.com/dbms-data-independence
5. Reference Book: DATABASE SYSTEM CONCEPTS SIXTH EDITION
Abraham Silberschatz Yale University Henry F. Korth Lehigh
University S. Sudarshan Indian Institute of Technology, Bombay
Thank You