Data Design

Chapter 7 6
Contents
1. Data design concepts
2. DBMS components
3. Web-based database design
4. Data design terminology
5. Data relationship
6. Normalization
7. Database models
8. Data storage
9. Data control
6.1 Data design concepts
Data Design Concept

 Data Structure
 Is a framework for organizing & storing data
 Consist of files / tables - link in various way
 files / tables ➔ contains data about people, places,things
or event
 Have 2 types of data structures:
 File-Oriented System
 Database Management System
 Itsdepend on how the system’s file & tables are
organized & link
Data Design Concept
File Processing System / File Oriented System
 Data Design Concept
Database Management System
Data Design Concept

File-oriented system
 Stores & managed data in one / more separate
file – called File Processing
 Use to handle large volumes of structured data
 Older system utilized it, because its suited to
mainframe hardware & batch input
 Less common today, but in certain situation it
is more efficient & cost less than DBMS
 Disadvantage:
 Data Redundancy – Same data is stored in more
than one place
 Data Integrity – Update are not applied in every
file
 Rigid Data Structure – Slow & inefficient in
retrieving information
 Data Design Concept
 Types of File for File Processing System

 Master File➔ a master file stores relatively

permanent data about an entity. E.g. Student Name,
Student ID, Course Name, Course ID.

 Table File➔ a table file contains reference data

used by the information system. As with master file,
table files are relatively static and are not updated by
IS.

 Transaction File➔ a transaction file stores records

that contain day-to-day business and operational
data. E.g. Saving Account in a bank, charges, payment
 Data Design Concept

 Types of File for File Processing System

 Work / Scratch File➔ a work file is a temporary file created

by an information system for a single task. Most often a work file is
created by one process in the information system and used by another
process within the same system. E.g. Special Report (Students with a
CGAP > 3.00)

 Security File➔a security file is created and saved for backup

and recovery purposes. E.g. audit trail files (users that have used
the system, from what time - what time).

 History File➔ a history file is a file copy created and saved for
historical or archiving purposes. New history files, unlike new
security files, do not replace the old files
6.2 DBMS components
DBMS Components

 The Evolution from Files System to Database System

Consists of linked data files, also called tables, that form an

overall data structure.Database environment offers greater
flexibility and efficiency.

Provides an overall framework that avoids data redundancy

and supports a real-time, dynamic environment.

(DBMS)➔ is a collection of tools, features, and interfaces that

enables users to add, update, manage, access, and analyze the
contents of a database.

The main advantage of a DBMS is that it offers timely,

interactive, and flexible data access.
DBMS Components

 Advantages of DBMS:
 Scalability
 Client Server
 Economy Scale
 Flexible Data Sharing
 Enterprise-Wide Application
 Stronger Standards
 Controlled Redundancy
 Better Security
 Increased Programmer Productivity
 Data Independence
DBMS Components

 DBMS Tradeoffs:
 More expensive hardware, software, data networks
for supporting multi user environment

 More complex on the learning-increase TCO

 Proceduresbackup, recovery & security are more

complicated & critical.

 DBMS failures will seriously disrupts business

operations.
DBMS Components
 DBMS Components:
❑ A DBMS provides an
interface between a
database and users who
need to access the
data.

❑ In addition to interfaces
for users, database
administrators, and
related systems, a
DBMS also has a data
manipulation language,
a schema and sub-
schemas, and a physical
data repository
DBMS Components

 DBMS Components:
❑Users
• Query language
allows a user to specify a task without specifying how the task will
be accomplished.
• Query by example (QBE)
allows the user to provide an example of the
data requested.
• SQL (structured query language)
a query language that allows PC users to
communicate with servers and mainframe
computers.

❑ Database Administrators
• A DBA is responsible for DBMS management and support
DBMS Components
❑ Related information systems
• A DBMS can support several related information systems that
provide input to, and require specific data from, the DBMS
❑ Data Manipulation Language
• A data manipulation language (DML) controls database operations,
including storing, retrieving, updating, and deleting data
❑ Schema
• The complete definition of a database, including descriptions of all
fields, tables, and relationships.
• Sub-schemas
A subschema defines only those portions of the database that a
particular system or user needs or is allowed to access.
❑ Physical Data Repository
• The data dictionary is transformed into a physical data repository,
which also contains the schema and sub-schemas
• The physical repository might be centralized, or distributed at
several locations.
6.3 Web-based database design
Web Based Database Design
Web Based Database Design
 Internet Terminology:

Web browser
Web page
HTML – Hypertext Markup Language
Web server
Web site
Intranet
Extranet
Protocols
Web-centric
Clients
Servers
Web Based Database Design
Web Based Database Design
❑ Data Security
• Web-based data must be totally secure, yet easily accessible
to authorized users

• To achieve this goal, well-designed systems provide security

at three levels: the database itself, the Web server, and the
telecommunication links that connect the components of
the system

❑ Database must be connected to the Internet or intranet

• Middleware➔ Software that integrates different
applications and allows them to exchange data
6.4 Data design terminology
Data Design Terminology

 Entity
 Table / File
 Field
 Record
 Key Field
 Primary Key
 Candidate Key
 Foreign Key
 Secondary Key

 Referential Integrity
6.5 Data relationships
Entity Relationship Diagram
 ERD

➔Is a graphical model of the information system that shows the

relationships among system entities.

➔Types of Relationship:
•One-to-one relationship (1:1)
•One-to-many relationship (1:M)
•Many-to-many relationship (M:N)
Database Design: One Step at a Time

1.Create the initial ERD

2.Assign all data elements to entities
3.Create 3NF designs for all tables, taking
care to identify all primary, secondary,
and foreign keys
4.Verify all data dictionary entries
5.After creating your final ERD and
normalized table designs, you can
transform them into a database
6.6 Normalization
Normalization

➔process of creating table designs, by assigning

specific fields or attributes to each of the tables.
➔Repeating Groups & Unnormalized Design

❑ First Normal Form

❑ Second Normal Form
❑ Third Normal Form
6.7 Database models
Database Model
❑ Hierarchical and Network Databases
• In a hierarchical database, data is organized like a family tree or
organization chart, with branches representing parent records and
child records
• A network database resembles a hierarchical design, but provides
somewhat more flexibility

❑ Relational Databases
• The relational model was introduced during the 1970s and became
popular because it was flexible and powerful
• Because all the tables are linked, a user can request data that
meets specific conditions
• New entities and attributes can be added at any time without
restructuring the entire database

❑ Object-Oriented Databases
• Many systems developers are using object-oriented database
(OODB) design as a natural extension of the object-oriented analysis
process
6.8 Data storage
Data Storage & Access

❑Data Warehousing
• A data warehouse is an integrated collection
of data that can support management
analysis and decision making.

❑Data Mining
• Data mining software looks for meaningful
patterns and relationships among data. For
example, data mining software could help a
consumer products firm identify potential
customers based on their prior purchases.
Data Storage & Access
❑Logical storage
• As seen through a user’s eyes

❑Logical record
• A logical record contains field values that describe a
single person, place, thing, or event

❑Physical storage
• Is strictly hardware-related, because it involves the
process of reading and writing binary data to physical
media such as a hard drive or CD-ROM.
 Data Storage & Access
 Data Storage Format

All data are stored in the form of binary digits, that have
only 2 possible values (0 or 1).There are 4 primary data
storage formats:-

❑Binary digits
A format that offers efficient storage of numeric data.
❑EBCDIC and ASCII
A data storage method used on most mainframe
computers.
❑Unicode
Unicode requires 16 bits per character, which allows it
to represent more than 65,000 unique characters.
Data Storage & Access

 Data Field
❑International Organization for
Standardization (ISO)
❑ YYYYMMDD
❑ Easy for comparison or sorting

❑Absolute date
❑ Total number of days from a specific base date.
❑ Starts on Jan 1, 1990.
❑ So in August 27, 2004 – 38226 days
❑ Its good for calculation purposes
6.9 Data control
Data Storage & Access
 Data Control
❑File and database control must include all measures necessary
to ensure that data storage is correct, complete, and secure
❑Must provide built-in control and security including:
❑Subschema, password, encryption, audit trail files, back-up &
recovery.
❑Limiting access to files and database.
❑Permission: different privileges given to group of people.
❑Encryption: converting readable data into unreadable
characters to prevent unauthorized access.
❑Backup & recovery: restore the files or database to its current
state at the time of the last backup.
❑Audit log files: record details of all access and changes made.
❑Audit fields: recorded during audit log files. Special fields
within data records to provide additional control or security
information.