UCCD 1203

Database Development and Applications

FICT UTAR - Jan2021

Reminder:
Intellectual Property
◼ Copyright must be seriously protected. The University
takes a strong stand against any illegal photocopying and
distributing of all materials provided to students. Students
are forewarned of the consequences and the penalty that
may be meted out if they are “caught in the act”.
◼ All the materials provided to student SHOULD NOT be
posted/distributed at any online platform or any other
ways possible without the permission.

FICT UTAR - Jan2021

This Week’s Agenda

◼ Assessments and expectations

◼ Plans for Jan 2021
◼ Introduction to Database Systems

FICT UTAR - Jan2021

Course name: UCCD1203 Database Development and Applications
Programme: Bachelor of Information Systems (Hons) Business Information Systems
Bachelor of Information Systems (Hons) Information Systems Engineering
Bachelor of Computer Science (Hons) Computer Science
Bachelor of Information Technology (Hons) Communication and Networking
Bachelor of Information Technology (Hons) Computer Engineering
Year of Study: Year One/Year Three
Year /Semester: 202101
Credit Hour & 2 represents lecture: (2 hours x 12weeks)
Contact Hour: 1 represents practical: (2 hours  10 weeks)
Lecturer: Miss Norazira Binti A Jalil (noraziraj@utar.edu.my) Room No: NG-035
Tutors: Ms. Yap Seok Gee (yapsg@utar.edu.my)
Ms. Chan Lee Kwun (chanlk@utar.edu.my)
Dr.Nur Syadhila binti Che Lah (syadhila@utar.edu.my)
Ts Soong Hoong Cheng (soonghc@utar.edu.my)
Ts Dr Anbuselvan a/l Sangodiah (anbuselvan@utar.edu.my)
Dr Aamir Amin (aamir@utar.edu.my)
Mode of Delivery: Lecture and Practical
Objective: To introduce the concepts, techniques and technologies associated with the development of relational database
management systems;
To build the fundamental knowledge and essential skills on developing database application.
Learning Outcome: Course Outcomes
Upon completion of this course, a student shall be able to:
1. Explain various database objects, fundamental database vocabulary and data management techniques.
2. Develop an appropriate Entity Relationship Diagram (ERD) based on a case study.
3. Describe relational design principles based on dependencies and normal forms.
4. Construct Structure Query Language (SQL) statements.
FICT UTAR - Jan2021
 Textbooks
◼ Main Text
Coronel, C., Rob, P., & Morris, S. (2019). Database Systems:
Design, Implementation, and Management. (13th Ed.). Boston,
MA: Course Technology, Cengage Learning
◼ Additional Text
1. Kroenke & Auer (2019). Database Concepts. (8th Ed.).
Prentice Hall.
2. Mannino, M. V. (2015). Database Design, Application
Development, and Administration. (6th Ed.). Chicago:
Chicago Business Press.
3. Connolly, T. M., & Begg, C. E. (2015). Database Solutions.
(6th Ed.). Harlow, England: Pearson/Addison-Wesley.

FICT UTAR - Jan2021

Continuous Assessments

◼ Quiz 5%
◼ Midterm 15%
◼ Group Assignment 10% 50%
◼ Practical Assessments 20%

◼ Final Assessment 50%

FICT UTAR - Jan2021

Plan for Jan 2021
◼ Database Assignment(10%) – due Week 7
◼ Quiz (5%) – Week 5
◼ Midterm(15%) – Week 8
◼ Lab assessment 1 (10%) –Week 9/10
◼ Lab assessment 2 (10%) – Week 11/12

FICT UTAR - Jan2021

Database Assignment (10%)
◼ Case will be given.
◼ Group of 4 members, if possible, from same
program.
◼ Timely assignment arrival (For each day
that you are late, 10 marks will be taken off
from your total marks.)

FICT UTAR - Jan2021

Lab assessments 1 & 2 : 10% each (Individual
Activities)
◼ The purpose of the lab assessments is to ensure that
students keep up with the practical.

◼ To be prepared for the assessments, you need to

understand the relevant topics.

◼ The format of the assessments: multiple choice,

hands-on problem solving questions, etc.

FICT UTAR - Jan2021

Practical
◼ Starting from Week 2
◼ Don’t miss any practical sessions
◼ 3 sessions using Access
◼ 6 sessions using Oracle - SQL
◼ 1 ERD

FICT UTAR - Jan2021

Student Conduct

◼ Pre-class preparation
◼ Attend class on time
◼ Download the slides before class
◼ Timely assignment arrival
◼ Professionally prepared assignments
◼ Professional class & practical behavior
◼ Communication

FICT UTAR - Jan2021

FICT UTAR - Jan2021
FICT UTAR - Jan2021
FICT UTAR - Jan2021
Consultation Hours
Miss Norazira Dr Nur Syadhila
Monday, 2:00pm - 4:00pm Monday, 10.30am - 12.30pm
Tuesday, 10:00am - 12:00pm Wednesday, 2.00pm - 4.00pm

By appointment:
Ms Teams:
noraziraj@utar.edu.my (related to lecture)
syadhila@utar.edu.my (related to assignment)

1. Send message to make appointment

2. State when you prefer to meet
3. Attach your timetable

FICT UTAR - Jan2021

Class Attendance

FICT UTAR - Jan2021

In class quizzes/assessments (for Attendance)

◼ Hi-hive (scan the QR code)

◼ Ad-hoc quizzes will be given during the

lecture or practical.

◼ Do not miss any lectures or practical.

FICT UTAR - Jan2021

Replacement for Practical session
◼ Email (same) your tutor and the tutor that you
attended the practical

◼ Programme –IA/IB/CS/CN/CT
◼ Course/subject– UCCD1203
◼ Lecture: L1, L2, L3
◼ Practical

FICT UTAR - Jan2021

WBLE

FICT UTAR - Jan2021

http://wble-kpr.utar.edu.my&sesskey=bc4jqhKsZc

FICT UTAR - Jan2021

 UCCD 1203
Database Development and Applications

Topic 1
Introduction to
Database Systems

FICT UTAR - Jan2021

Objectives
◼ Introduction of database systems
◼ Problems with file-based approach
◼ Database(DB) and Database Management
System (DBMS)
◼ Characteristics of Database
◼ Components of Database System Environment
◼ Functions of DBMS

FICT UTAR - Jan2021

Question
If you had one of the jobs listed below, how might
you use a database?
(1) mechanic in an auto-repair shop
(2) taxi driver
(3) landscape gardener

FICT UTAR - Jan2021

Why learn it?
◼ Data is at the center of many things.
◼ All kind of information are stored in
databases.
◼ We interact with databases every day,
consciously or unconsciously.

FICT UTAR - Jan2021

Database technology in our daily life
◼ Examples of Database Applications
◼ Purchases from the supermarket
◼ Purchases using credit card
◼ Booking a holiday at the travel agents
◼ Using the local library
◼ Using the Internet
◼ Studying at university
◼ etc…

FICT UTAR - Jan2021

Database Technology
◼ Provide timely and useful information, accurate
data
◼ improve daily operation
◼ quality decision making
◼ gain competitive advantages
◼…

FICT UTAR - Jan2021

Hierarchy of Data

is the smallest unit of data representation

Data stored in computer systems form a hierarchy extending from a

single bit to a database.
FICT UTAR - Jan2021
Hierarchy of Data

Eight bits make a byte which can represent

a character or a special symbol

Data stored in computer systems form a hierarchy extending from a

single bit to a database.
FICT UTAR - Jan2021
Hierarchy of Data

grouping of characters

Data stored in computer systems form a hierarchy extending from a

single bit to a database.
FICT UTAR - Jan2021
Hierarchy of Data

a collection of fields

Data stored in computer systems form a hierarchy extending from a

single bit to a database.
FICT UTAR - Jan2021
Hierarchy of Data

a group of related records.

Data stored in computer systems form a hierarchy extending from a

single bit to a database.
FICT UTAR - Jan2021
Hierarchy of Data
collection of logically related records or
files

Data stored in computer systems form a hierarchy extending from a

single bit to a database.
FICT UTAR - Jan2021
 Hierarchy of Data
◼ Data are logically organized into:
◼ Bit - a bit is the smallest unit of data representation (value of a bit may be a 0 or
1). Eight bits make a byte which can represent a character or a special symbol in
a character code.
◼ Field - a field consists of a grouping of characters. A data field represents an
attribute (a characteristic or quality) of some entity (object, person, place, or
event).
◼ Record - a record represents a collection of attributes that describe a real-world
entity. A record consists of fields, with each field describing an attribute of the
entity.
◼ File - a group of related records. Files are frequently classified by the
application for which they are primarily used (employee file). A primary key in
a file is the field (or fields) whose value identifies a record among others in a
data file.
◼ Database - It is an integrated collection of logically related records or files. A
database consolidates records previously stored in separate files into a common
pool of data records that provides data for many applications.

FICT UTAR - Jan2021

Data versus Information: Data

• Raw facts
• Not processed (yet)
• Not meaningful to the
audience/reader

FICT UTAR - Jan2021

Data versus Information : Information

•Processed data
–Summarized Monthly Sales Report
for West Region
–Organized
Sales Rep: Charles Mann
–Labeled Emp No. 791545
Item Qty Sold Price
•Meaningful to audience TM Shoes 1200 $100

•Knowledge derived from

data, the result of combining,
comparing and performing
calculation on data
FICT UTAR - Jan2021
 Data vs. Information

◼ Data becomes information when shown in context to

reference values (limits, past information, correlated
data, what’s expected, etc.)

◼ What is 800? Is it good or bad?

Depends on the limits, and the scale, and our goals.

FICT UTAR - Jan2021

Good or bad?

FICT UTAR - Jan2021

And now?

FICT UTAR - Jan2021

Cat’s blood work results: Is it Good or Bad?

Context helps users understand data

FICT UTAR - Jan2021
Data, information, knowledge
◼ Data- raw fact/figure, no meaning until processed
and given a context.

◼ Information – data which has been processed

within a context in order to give it a meaning.

◼ Knowledge – capability to understand the

relationship between pieces of information and
what to actually do with the information.

FICT UTAR - Jan2021

Data, Information, Knowledge
24/12/15, 1/6/15, 25/5/15,
Raw data 10/10/15, 25/12/15, 1/1/15,
4/1/15, 5/10/15, 7/9/15, 26/12/15

Context dates when a holiday

cottage has been booked.

Processing

Information 1/1/15, 4/1/15

25/5/15, 1/6/15
5/10/15, 10/10/15
24/12/15, 25/12/15,26/12/15

FICT UTAR - Jan2021

FICT UTAR - Jan2021
 Graphical displays data into useful
information that managers can use for
decision making and interpretation
FICT UTAR - Jan2021
 Database Technology Evolution
Era Orientation Major Features
1960s File File structures, supported sequential and
random searching
1970s Network Network and hierarchies of related records
Navigation
1980s Relational Mathematical relations and associated
operators, non-procedural languages,
optimization technology
1990s Object can store and manipulate multimedia data,
distributed processing.

2000s Post-relational databases fast key-value stores and document-oriented

Multi-dimensional databases, graph database systems, cloud-
databases based, Real-time
NoSQL
NewSQL
FICT UTAR - Jan2021
Current Market
◼ Relational DBMSs still anchor the software industry
◼ Oracle, Microsoft, IBM,…..
◼ Open source: MySQL, PostgreSQL
◼ Emerging variants: In-memory, column oriented,…
◼ Open Source “NoSQL” is growing
◼ Analytics: Hadoop MapReduce, Spark
◼ Key-value stores: Cassandra, Mongo, Counch,…
◼ Cloud hosted database/real-time: Firebase
◼ Cloud services are expanding quickly
◼ Amazon Web Service (AWS), MS Azure, Google
Cloud,… FICT UTAR - Jan2021
FICT UTAR - Jan2021
FICT UTAR - Jan2021
Revolution of Data
◼ Data is moving in from variety of sources
◼ Mobile
◼ social network
◼ GPS
◼ IoT
◼ Cameras, microphone
◼ Point of sales
◼ RFID
◼ ….

FICT UTAR - Jan2021

Database System vs. File System

FICT UTAR - Jan2021

Evolution of File System Data Processing:
Manual File System

◼ Traditionally composed of collection of file folders kept in

file cabinet
◼ Organization within folders was based on data’s expected use
(ideally logically related)
◼ System was adequate for small amounts of data with few
reporting requirements
◼ Finding and using data in growing collections of file folders
became time-consuming and cumbersome

FICT UTAR - Jan2021

Evolution of File System Data Processing:
Computerized File System
◼ Could be technically complex, requiring hiring of data
processing (DP) specialists
◼ DP specialists created file structures, wrote software, and
designed application programs
◼ Resulted in numerous “home-grown” systems being
created
◼ Computer files were similar in design to manual files
◼ Lots of data files with related, often overlapping data.
◼ No control over data consistency

FICT UTAR - Jan2021

Before Database….

FICT UTAR - Jan2021

 Lakeview Equipment Rentals
Job Contractor Phone EqpType EqpNo DailyRate StartDt EndDt Charge

Sea View KH Services 213.444.1 Backhoe 10400 $750 6/17 6/19 $2,250
Bldg 181

Highland Comstock, 232.492.3 Backhoe 10400 $750 6/24 6/24 750.00

Center Inc 383

Sea View KH Services 213.444.1 Medium 335 $350 6/17 7/3 $750
Bldg 181 Crane

Sea View KH Services 213.444.1 Backhoe 10020 $650 7/1 7/3 $5,950
Bldg 181

Sea View KH Services 213.444.1 Scaffolding $135 6/15 $1950

Bldg 181

Highland Comstock, 232.492.3 Medium 335 $400 7/1 7/8 $3200.00

Center Inc 383 Crane

Village RB 508.555.3 Backhoe 10020 $750 7/8 7/11 $3,000

Square Partnersh 233
ip

FICT UTAR - Jan2021

Donor Donation 1 Donation 2 Donation 3 Donation 4
Angel Pinelli
421-99-1243

Victor Gomez $200 Solar Scholars

351-12-9867 (Powering schools
with solar panels)
1/4/2015

Victor Gomez $100 Pear Creek $100 DanubeLand $50 Forest Asia
351-12-9867 (Cleaning up litter Trust (Planting trees in
and pollutants from (Purchasing and Asia) 4/1/2016
Pear Creek) preserving land in the
11/6/2015 Danube watershed)
24/12/2015
Jack Lee $150 Forest Asia $150 Forest Asia $100 Pear Creek
231-49-0802 ( Planting trees in ( Planting trees in (Cleaning up litter
Asia) 1/7/2015 Asia) 1/2/2016 and pollutants from
Pear Creek)
1/2/2016

FICT UTAR - Jan2021

Revolution of Data
◼ Data is moving in from variety of sources
◼ Mobile
◼ social network
◼ GPS
◼ IoT
◼ Cameras, microphone
◼ Point of sales
◼ RFID
◼ ….

FICT UTAR - Jan2021

SOLUTION: Operational Database

Database

A shared collection of logically related

data and a description of data, designed
to meet the information need of an
organization.

End user data (raw facts)

Metadata (data about data)
FICT UTAR - Jan2021
End user data

FICT UTAR - Jan2021

 Descriptions of the properties or characteristics of
the data, including data types, field sizes, allowable
values, and data context
FICT UTAR - Jan2021
Illustrating Metadata with Microsoft Access

FICT UTAR - Jan2021

Types of Databases

◼ Databases can be classified according to:

◼ Number of users
◼ Database location(s)
◼ Expected type and extent of use

FICT UTAR - Jan2021

Number of users
◼ Single-user database supports only one user at a
time
◼ Desktop database: single-user; runs on PC
◼ Multiuser database supports multiple users at the
same time
◼ Workgroup and Enterprise databases
◼ E-Commerce database/web database/internet
database

FICT UTAR - Jan2021

Database location(s)
◼ Centralized database: data located at a
single site

◼ Distributed database: data distributed

across several different sites

FICT UTAR - Jan2021

 Expected type and extent of use
◼ Operational systems(Transactional database):
◼ Support day-to-day operations of an organization,
◼ Also referred to as on-line transaction processing (OLTP).
◼ Main tasks: processing of a huge number of concurrent
transactions, and ensuring data integrity.
◼ Analytical systems (Data warehouse):
◼ support knowledge workers (e.g., manager, executive,
analyst) in decision making,
◼ stores historical data used for tactical or strategic decisions
(pricing decision, sales forecasts, …)
◼ Also referred to as on-line analytical processing (OLAP).

FICT UTAR - Jan2021

Where we are…
Now we’re here…

Data Data Data

entry extraction Analytical analysis
Transactional Data Store/
Database Data
warehouse
Stores real-time Stores historical
transactional data transactional and
OLTP – Online summary data
Transaction OLAP – Online
Processing Analytical
Processing

FICT UTAR - Jan2021

FICT UTAR - Jan2021
Database System Environment

Figure 1.7

FICT UTAR - Jan2021

Components of Database System Environment

◼ Hardware
◼ System’s physical devices: can range from a
PC to a network of computers, storage
devices, printer, …
◼ Software
◼ DBMS, operating system, network software
(if necessary) and also the application
programs.
◼ Data
◼ Used by the organization and a description
of the data
FICT UTAR - Jan2021
Components of Database System Environment

◼ Procedures
◼ Instructions and rules that should be applied
to the design and use of the database and
DBMS.
◼ People
◼ Data Administrator (DA)
◼ Database Administrator (DBA)
◼ Database Designers
◼ Application Programmers
◼ End Users
FICT UTAR - Jan2021
 Database Characteristics
◼ Persistent
- Lasts a long time, outlives program that operate it.
- Relevance of intended usage: only store potentially relevant data
◼ Inter-related
- Entity: cluster of data about a topic (course, student, loan)
- Relationship: connection among entities
◼ Shared
- Multiple uses: hundreds to thousands of data entry screens and
reports
- Multiple users: many people simultaneously use a database
◼ Reliability
- up all the time

FICT UTAR - Jan2021

Database Characteristics
◼ Massive
-hundreds of gigabytes for medium size organization

◼ Safe
- from system/software failure, from malicious users
- running crucial apps – eg. banking

◼ Efficient
- retrieval, storing, etc

◼ Convenient
- Simple commands to get the information

FICT UTAR - Jan2021

Database System vs. File System

FICT UTAR - Jan2021

 Database Management
Systems

A software system that enables users to

define, create, maintain and control access
to the database.

FICT UTAR - Jan2021

File System vs DBMS
Thought Experiment 1:
◼ You and your group member edit the same file
◼ You both save it at the same time
◼ Whose changes survive?
a) Yours
b) Group member’s
c) Both
d) Neither
e) ???

FICT UTAR - Jan2021

File System vs DBMS
Thought Experiment 2:
◼ You are updating the file
◼ The power goes out
◼ Which changes survive?
a)All
b)None
c) All since last
save
d)???

FICT UTAR - Jan2021

 DBMS Functions
◼ Performs functions that guarantee integrity and
consistency of data
◼ Data dictionary management
◼ defines data elements and their relationships
◼ Data storage management
◼ stores data and related data entry forms, report
definitions, etc.
◼ Data transformation and presentation
◼ translates logical requests into commands to physically
locate and retrieve the requested data

FICT UTAR - Jan2021

DBMS Functions (continued)
◼ Security management
◼ enforces user security and data privacy within database
◼ Transaction support
◼ Ensure that all the updates corresponding to a given
transaction are made or none of them are made.
◼ Multi-user access control
◼ creates structures that allow multiple users to access the data
◼ Backup and recovery management
◼ provides backup and data recovery procedures

FICT UTAR - Jan2021

DBMS Functions (continued)

◼ Data integrity management

◼ promotes and enforces integrity rules to eliminate data
integrity problems
◼ Data query language
◼ Lets user specify what must be done without having to
specify how it is to be done.

◼ Database communication interfaces

◼ allows database to accept end-user requests within a
computer network environment

FICT UTAR - Jan2021

Advantages of DBMS
◼ Control of data redundancy
◼ Data consistency
◼ Sharing of data
◼ Improved data integrity
◼ Improved security
◼ Enforcement of standards
◼ Economy of scale

FICT UTAR - Jan2021

Advantages of DBMS
◼ Balanced conflicting requirements
◼ Improved data accessibility and responsiveness
◼ Increased productivity
◼ Improved maintenance through data
independence
◼ Increased concurrency
◼ Improved backup and recovery services

FICT UTAR - Jan2021

Disadvantages of DBMS
◼ Complexity
◼ Size
◼ Cost of DBMS
◼ Additional hardware costs
◼ Cost of conversion
◼ Performance
◼ Higher impact of a failure

FICT UTAR - Jan2021