Computational View of Big Data

Data Visualization

Data Access Data Analysis

Data Understanding Data Integration

Formatting, Cleaning

Storage Data
Big Data & Related Disciplines
Human-Computer Interaction
Data Visualization

Databases Information Retrieval Machine Learning

Data Access Data Analysis

Data Mining
Computer Vision Speech Recognition
Data Understanding Data Integration
Natural Language Processing Data Warehousing

Formatting, Cleaning
Signal Processing Many Applications!

Storage Data
Information Theory
 Data Science Methodology

9/4/2024 3
INTRODUCTION
TO DATABASES
S1 Sains Data
FMIPA UNESA
2024
 LEARNING
OBJECTIVES

9/4/2024
What Does a Database Have to do with Our
Everyday Life?
• More than you may realize…

9/4/2024 7
Databases support the operation of
businesses across all sectors of industry
• Finance and Banking−Maintaining customer records and
transaction details
• Retailing −Stock control
• Telecommunications −Call logs
• Airline −Travel reservations
 Contoh

Order

Shopee Customer

Alamat, item, dll

9/4/2024 9
 Contoh

What if we use • Terbatas pada ratusan ribu baris.

EXCEL ? • Data sering kali terikat pada satu file,
sehingga sulit diakses bersamaan.

• Dapat menangani jutaan data besar dengan

What if we
mudah.
use • Memungkinkan akses data secara bersamaan oleh
DATABASE ? banyak pengguna secara real-time.
• Cepat dan mudah untuk memanipulasi data
(menambah data baru, delete, edit dan lainnya
• Format data yang terstandarisasi dan konsisten

9/4/2024 10
 What is Database ?
What is data ?
Data, known facts that can be recorded and that have implicit meaning.

Database
• A highly organized, interrelated, and structured set
of data about a particular enterprise.
• A collection of data that is organized systematically
so that it can be easily accessed, managed and
updated.

9/4/2024 11
 What is Database Management System (DBMS)?

DBMS
• a general-purpose software system that facilitates the processes of
defining, constructing, manipulating, and sharing databases among
various users and applications.
• An environment that is both convenient and efficient to use

Database systems are used to manage collections of data that are:

• Highly valuable
• Relatively large
• Accessed by multiple users and applications, often at the same time.

9/4/2024 12
A simplified
architecture
for a
database
system

9/4/2024 13
Who are we?

9/4/2024 14
 Database Development Process
(with a Conceptual Data Model)
Mini-world for the example:
• Part of a UNIVERSITY environment
Some mini-world entities:
• STUDENTs
• COURSEs
• SECTIONs (of COURSEs)
• (Academic) DEPARTMENTs
• INSTRUCTORs
Some mini-world relationships:
• SECTIONs are of specific COURSEs
• STUDENTs take SECTIONs
• COURSEs have prerequisite COURSEs
• INSTRUCTORs teach SECTIONs
• COURSEs are offered by DEPARTMENTs
• STUDENTs major in DEPARTMENTs
9/4/2024 15
 University database

each STUDENT record includes data to represent

the student’s Name, Student_number, Class
(freshman or ‘1’, sophomore or ‘2’, and so forth), SECTION file stores data on each section of a
Major (mathematics or ‘MATH’ and computer course
science or ‘CS’)

PREREQUISITE file stores the

each COURSE record includes data to prerequisites of each course
represent the Course_name, GRADE_REPORT file stores the
Course_number, Credit_hours, and grades that students receive in
Department. the various sections they have
completed
9/4/2024 16
 University database

• Some mini-world relationships:

o SECTIONs are of specific COURSEs
o STUDENTs take SECTIONs
o COURSEs have prerequisite COURSEs
o INSTRUCTORs teach SECTIONs
o COURSEs are offered by DEPARTMENTs
o STUDENTs major in DEPARTMENTs
• Note: The above entities and relationships are typically expressed in a
conceptual data model, such as the entity-relationship (ER) data or UML
class model (see Chapters 3, 4)

9/4/2024 17
 Characteristics of the Database Approach

1. Self-describing nature of
a database system
• A DBMS catalog stores the
description of a particular
database (e.g. data
structures, types, and
constraints)
• The description is called
meta-data*.
• This allows the DBMS
software to work with
different database
applications.

9/4/2024 18
 Characteristics of the Database Approach
2. Insulation between programs and data, and data abstraction
• Called program-data independence.
• Allows changing data structures and storage organization without having
to change the DBMS access programs
Data abstraction:
• A data model is used to hide storage details and present the users with a
conceptual view of the database.
• Programs refer to the data model constructs rather than data storage
details

3. Support of multiple views of the data

• Each user may see a different view of the database, which describes only
the data of interest to that user.
9/4/2024 19
 Characteristics of the Database Approach

4. Sharing of data and multiuser transaction processing

• Allowing a set of concurrent users to retrieve from and to update the database.
• Concurrency control within the DBMS guarantees that each transaction is
correctly executed or aborted
• Recovery subsystem ensures each completed transaction has its effect
permanently recorded in the database
• OLTP (Online Transaction Processing) is a major part of database applications;
allows hundreds of concurrent transactions to execute per second.
9/4/2024 20
 Database Users – Actors on the Scene

Those who actually use and control the database content, and those who design,
develop and maintain database applications (called “Actors on the Scene”), and
• Database administrators : authorizing access rights
• Database designers : define the structure, the constraints, and functions or
transactions against the database.
• End-users:
o Casual : access database occasionally when needed
o Naïve or parametric : user that job is always constant query and update data,
such as Bank-tellers or reservation clerks
o Sophisticated : These include business analysts, scientists, engineers, others
o Stand-alone : maintain personal databases using ready-to-use packaged
applications

9/4/2024 21
 Database Users – Actors on the Scene

• System analysts and application developers (Software Engineer)

o System analysts: They understand the user requirements of naïve and
sophisticated users and design applications including canned
transactions to meet those requirements.
o Application programmers: Implement the specifications developed by
analysts and test and debug them before deployment.
o Business analysts: There is an increasing need for such people who can
analyze vast amounts of business data and real-time data (“Big Data”) for
better decision making related to planning, advertising, marketing etc.

9/4/2024 22
 Database Users – Workers behind the Scene

Those who design and develop the DBMS software and related tools, and the
computer systems operators (called “Workers Behind the Scene”).
• System designers and implementors: Design and implement DBMS
packages in the form of modules and interfaces and test and debug them.
The DBMS must interface with applications, language compilers, operating
system components, etc.
• Tool developers: Design and implement software systems called tools for
modeling and designing databases, performance monitoring, prototyping,
test data generation, user interface creation, simulation etc. that facilitate
building of applications and allow using database effectively.
• Operators and maintenance personnel: They manage the actual running
and maintenance of the database system hardware and software
environment.

9/4/2024 23
 Advantages of Using the DBMS Approach

1. Controlling redundancy in data storage and in development and

maintenance efforts : Sharing of data among multiple users.
2. Restricting unauthorized access to data. Only the DBA staff uses
privileged commands and facilities.
3. Providing persistent storage for program Objects: E.g., Object-
oriented DBMSs make program objects persistent– see Chapter
12.
4. Providing storage structures (e.g. indexes) for efficient query
processing – see Chapter 17.

9/4/2024 24
 Advantages of Using the DBMS Approach

5. Providing Storage Structures and Search Techniques for Efficient

Query Processing
6. Providing Backup and Recovery
7. Providing Multiple User Interfaces
8. Representing Complex Relationships among Data
9. Enforcing Integrity Constraints
[Link] Inferencing and Actions Using Rules and Triggers

9/4/2024 25
 Additional Implications of Using the Database
Approach
• Potential for enforcing standards:
• Standards refer to data item names, display formats, screens, report structures, meta-
data (description of data), Web page layouts, etc.
• Reduced application development time:
• Incremental time to add each new application is reduced.
• Flexibility to change data structures:
• Database structure may evolve as new requirements are defined.
• Availability of current information:
• Extremely important for on-line transaction systems such as shopping, airline, hotel, car
reservations.
• Economies of scale:
• Wasteful overlap of resources and personnel can be avoided by consolidating data and
applications across departments.

9/4/2024 26
 History of Database Applications
1960s : The database software resided in the mainframe computer, and storage
capacity increases. The main types of early database systems were based on
hierarchical models (e.g., IBM’s Information Management System, IMS) and
network models (e.g., Integrated Data Store, IDS)
1970s : E. F. Codd proposes the relational model for databases, which abstracted
the logical organization of data from its physical storage.
1976 : P. Chen proposes the entity relationship model (ERM) for database design
Early-1980s : The first commercially available relational database management
systems (RDBMSs) began to emerge. Notable examples include IBM's DB2, Oracle,
and Microsoft SQL Server. These systems used SQL as their query language
Mid-1980s : SQL (Structured Query Language) became the standard language
for relational databases. SQL was initially developed by IBM in the 1970s but
became widely adopted and standardized by ANSI and ISO.

9/4/2024 27
 History of Database Applications
Early 1990s : The Object-Relational Database Management System
(ORDBMS) model was developed. This model combined features of object-
oriented databases with relational databases, leading to the integration of
object-oriented concepts in relational DBMSs
Mid-1990s : The World Wide Web became widely accessible, significantly
impacting data management and application development. During this period,
personal productivity tools like Microsoft Access (a desktop relational
database system) and ODBC (Open Database Connectivity) (a standard API
for database access) gained popularity.

9/4/2024 28
 History of Database Applications
Early 2000s :
The growth of database applications continued with the rise of major
commercial websites (e.g., Yahoo, Amazon, Google). IBM, Microsoft, and
Oracle dominated the database market. The growth of e-commerce saw the
adoption of new web standards and technologies to improve online shopping
experiences. XML was widely used for data exchange in e-commerce
transactions, and technologies
New Requirements: The increasing volume and variety of data led to the
development of new types of databases to handle unstructured or semi-
structured data, such as social media posts. This era saw the emergence of
NoSQL databases, which were designed to handle large-scale data with
flexible schemas and non-relational data models. NoSQL stands for "Not Only
SQL," indicating that these databases can support both relational and non-
relational data.

9/4/2024 29
 Two Common Types of DBMS
• Relational DBMS (RDBMS)
Tipe DBMS yang menyimpan data dalam bentuk tabular dan diketahui
hubungan antar tabel satu dengan tabel lainnya.

• No SQL DBMS
Disebut juga Non-Relational DBMS, merupakan tipe DBMS yang tidak
menyimpan data dalam bentuk tabular. Biasanya berguna untuk menyimpan
unstructured data.

9/4/2024 30
 SQL vs NoSQL
• NoSQL tidak membutuhkan skema penyimpanan, sedangkan database SQL
memiliki skema penyimpanan yang jelas dan terstruktur.
• Database SQL lebih baik dalam memproses multi-row transactions
sedangkan NoSQL lebih cocok untuk data tidak terstruktur seperti
Dokumen/JSON.

RDBMS NoSQL
9/4/2024 31
 When Not to Use a DBMS

• Main inhibitors (costs) of using a DBMS:

• High initial investment and possible need for additional hardware
• Overhead for providing generality, security, concurrency control,
recovery, and integrity functions
• When a DBMS may be unnecessary:
• If the database and applications are simple, well defined, and not
expected to change
• If access to data by multiple users is not required
• When a DBMS may be infeasible
• In embedded systems where a general-purpose DBMS may not fit in
available storage

9/4/2024 32
 When Not to Use a DBMS

• When no DBMS may suffice:

• If there are stringent real-time requirements that may not be met because
of DBMS overhead (e.g., telephone switching systems)
• If the database system is not able to handle the complexity of data
because of modeling limitations (e.g., in complex genome and protein
databases)
• If the database users need special operations not supported by the
DBMS (e.g., GIS and location-based services).

9/4/2024 33
Tugas
Identifikasi main activity sebuah aplikasi dan tentukan
entitas dan relationships database nya.

9/4/2024 34
THANK YOU