Database Design 1

DATABASE DESIGN
Introduction
Slide 1
INITIAL TERMINOLOGY
 Data - facts that are recorded and can be accessed

• Data formats – text, numbers, figures, graphics, images, audio/video
recordings and more
• Data is recorded and kept because it is considered to be of use to an
intended user
 Information - refers to the data that is accessed by a user
for some particular purpose
• Typically, getting the needed information from a collection of data
requires performing an activity, such as searching through, processing,
or manipulating the data in some form or fashion
Slide 2
INITIAL TERMINOLOGY
 Metadata - data that describes the structure and the

properties of the data
• Metadata is essential for the proper understanding and use of the data
Data without metadata - example

Data with metadata - example
Slide 3
INITIAL TERMINOLOGY
 Database - structured collection of related data stored on a

computer medium
• Organizes the data in a way that facilitates efficient access to the
information captured in the data
 Database metadata – represents the structure of the
database
• Database content that is not the data itself (data about the data)
• Contains:
o Names of data structures
o Data types
o Data descriptions
o Other information describing the characteristics of the data
Slide 4
INITIAL TERMINOLOGY
 Database management system (DBMS) - software used

for:
• Creation of databases
• Insertion, storage, retrieval, update, and deletion of the data in the
database
• Maintenance of databases
 Database system - computer-based system whose purpose
is to enable an efficient interaction between the users and the
information captured in a database
Slide 5
INITIAL TERMINOLOGY
Typical database system architecture
Front-end applications - provide a mechanism for

easy interaction between the users and the DBMS
Slide 6
INITIAL TERMINOLOGY
 End-users (business-users) - users using a database system to

support their tasks and processes
 Indirect interaction - end-user communicating with the database
through front-end applications
 Direct interaction - end-user communicating with the database
directly through DBMS
Slide 7
STEPS IN THE DEVELOPMENT OF DATABASE
SYSTEMS
 Databases can vary in their scope from small single-user

(personal) databases to large enterprise databases that can
be used by thousands of end-users
 Regardless of their scope, all databases go through the same
fundamental development steps (requirements, modeling,
implementation, deployment, use, etc.)
Slide 8
SYSTEMS
 Requirements collection, definition, and visualization -

results in the requirements specifying which data the future
database system will hold and in what fashion, and what the
capabilities and functionalities of the database system will be
• The collected requirements should be clearly defined and stated in a
written document, and then visualized
• Conceptual database model – a visualization of requirements by
using a conceptual data modeling technique (such as entity-
relationship [ER] modeling)
Slide 9
SYSTEMS
 Requirements collection, definition, and visualization
Slide 10
SYSTEMS
Iterative nature of the database requirements collection,
definition, and visualization process
Slide 11
SYSTEMS
 Database modeling (logical database modeling ) -

creation of the database model that is implementable by the
DBMS software
• Logical database modeling follows conceptual database modeling
Slide 12
SYSTEMS
 Database implementation - using a DBMS to implement

the database model as an actual database
• Most modern databases are implemented using a relational DBMS
(RDBMS) software
• SQL (Structured Query Language) is a language used by most RDBMS
packages
Slide 13
SYSTEMS
 Developing front-end applications - designing and

creating applications for indirect use by the end-users
• Front-end applications are based on the database model and the
requirements specifying the front-end functionalities
• Front-end applications contain interfaces (such as forms and reports)
accessible via a navigation mechanism (such as a menu)
Database front-end example
Slide 14
SYSTEMS
 Database deployment - releasing the database system for

use by the end users
 Database use - the insertion, modification, deletion and
retrieval of the data in the database system
• Example of data in a database that can be inserted, modified, deleted
or retrieved
Slide 15
SYSTEMS
 Database administration and maintenance - performing

activities that support the database end user, including
dealing with technical issues, such as:
• Providing security for the information contained in the database
• Ensuring sufficient hard-drive space for the database content
• Implementing the backup and recovery procedures
 THE NEXT VERSION OF THE DATABASE

• The new version of the database follows the same development steps
as the initial version
Slide 16
PEOPLE INVOLVED WITH DATABASE SYSTEMS
 Database analysts, designers, and developers

• Database analysts - involved in the requirements collection,
definition, and visualization stage
• Database designers (a.k.a. database modelers or architects) -
involved in the database modeling stage
• Database developers – in charge of implementing the database
model as a functioning database using the DBMS software
 Front-end applications analysts and developers
• Front-end application analysts - in charge of collecting and
defining requirements for front-end applications
• Front-end applications developers - in charge of creating the
front-end applications
Slide 17
PEOPLE INVOLVED WITH DATABASE SYSTEMS
 Database administrators (DBAs) - perform the tasks

related to the maintenance and administration of a database
system
 Database end users - use a database system to support
their work- or life-related tasks and processes
• Users differ in:
o Level of technical sophistication
o Amount of data that they need
o Frequency with which they access the database system
Slide 18
OPERATIONAL VERSUS ANALYTICAL
DATABASES
 Operational information (transactional information) - the

information collected and used in support of day-to-day operational needs
in businesses and other organizations
• Ex: Performing an ATM withdrawal, purchasing an airline ticket
 Operational database - collects and presents operational information in
support of daily operational procedures and processes
 Analytical information - the information collected and used in support
of analytical tasks
• Analytical information is based on operational (transactional) information
• Ex: Pattern of use of ATM machines, such as what hours of the day have the most
withdrawals
 Analytical database - collects and presents analytical information in
support of analytical tasks
Slide 19

Database Design 1

Uploaded by

Copyright:

Available Formats

Database Design 1

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Database Design 1

Uploaded by

Copyright:

Available Formats

DATABASE DESIGN

 Data - facts that are recorded and can be accessed

 Metadata - data that describes the structure and the

Data without metadata - example

 Database - structured collection of related data stored on a

o Other information describing the characteristics of the data

 Database management system (DBMS) - software used

Typical database system architecture

Front-end applications - provide a mechanism for

 End-users (business-users) - users using a database system to

 Databases can vary in their scope from small single-user

 Requirements collection, definition, and visualization -

 Requirements collection, definition, and visualization

 Database modeling (logical database modeling ) -

 Database implementation - using a DBMS to implement

 Developing front-end applications - designing and

 Database deployment - releasing the database system for

 Database administration and maintenance - performing

 THE NEXT VERSION OF THE DATABASE

 Database analysts, designers, and developers

 Database administrators (DBAs) - perform the tasks

 Operational information (transactional information) - the

You might also like