Database Design

Introduction

What is a Database
Database collection of organized data

Legacy database the database is old and been

in the company for quite some time

Examples of databases:
Address books
Telephone directory
Library information
Bookstores

Finance softwares
maps

Uses of databases
Tracking of long-term statistics and trends

Automating manual processes to eliminate paper

shuffling
Managing different types of transactions
performed by an individual or business
Maintaining historic information

OLTP and OLAP

Online Transaction Processing(OLTP)
Database used to process data in a regular basis
Examples: grading system, sales, reservation
Online Analytical Processing(OLAP)
Supply end users with response to queries being
submitted
Concerned with bulk data loads
Decision Support Systems and Data Warehouses

Database Environment
Mainframe environment consists of powerful

mainframe computer that allowed multiple user

connections. Multiple terminals are networked to
the main computer
Client/server environment involves a main
computer , called the server, and one or more
personal computers are connected into it
Internet computing environment relies on the
internet for networks, the server is called the Web
Server

Where Does a Database

Originate?
Business rules

Business processes
Data
Analysis
Entities
Attributes
Re-engineering

Business Rules
It affects the business in many ways

Tells how data is created, stored, and retrieved,

and manipulated
Categories of business rules:
-database oriented
-application oriented

Business Processes
Daily/timed activities of the company

Can be manual or automated

Example:
1.
2.
3.
4.
5.

Order is received from customer

Inventory is checked for availability
Customers order if confirmed
Warehouse is contacted
Product and invoice are shipped to the
customer

Information and Data

Information knowledge of something

Data information related to the organization

Types of data:
Static/historical accessed only when needed
Dynamic/transactional used more often

Requirements Analysis
Analyzing the needs of a business

Rules and process are considered aside from

data
Some of basic information needed:
Objectives and goals pertaining to the system
Proposed requirements
Business process and rules
Documents of current information

Entities and Attributes

Entities
Business object that represent a group, or
category of data
Examples:titles, topics
Attributes
Sub group of information within an entity
Example: within a book title there can be the
actual title, the publisher, and author

Business process re-engineering

Task of reworking process in order to streamline

the operations
Redesigning the entire system
Improvement of methods

Elements of a Database
Schema

Schema objects
Tables
Fields and columns
Records or rows
Keys
Relationships
Data types

Database Schema
Schema group of related objects in a database
Conceptual/logical model
Internal/physical model
External/view model

Tables
Primary unit of physical storage in the database

Types of data:
Data tables
Join tables
Subset tables
Validation tables

Columns
Category of information in the database

Represents related part of a table

Smallest logical structure

Rows
Collection of all columns in a table associated

with a single occurrence

Single record in a table

Data Types
Alphanumeric

Numeric
Date and Time
Boolean
Character Large Objects
Binary Large Objects

Database Integrity
Insurance of accurate data in database

Constraints validate the values of the data

Referential integrity process of ensuring that

data is consistent between related tables

Keys
Primary Keys
Unique data in a
table
Foreign Keys
Reference a
primary key in
another table

Relationships
Relationships reduce data redundancy

Normalization process of reducing data

redundancy
Types of relationships:
One-one
One-many
Many-many

Design Methodology
Process of designing a database with a plan

Advantages:
Step by step guide
Minimal trial and error
Easier documentation
Easier to modify the database

Application Design
Creating an interface for the end user through

which the database can be accessed

Consists of set of forms that allow the end user to
manipulate data

Characteristics of a good
database
Storage needs met

Available data
Secured data
Accurate and easy to manage
Acceptable performance to the user
Minimal redundant data