Database Management:: Ray R. Larson University of California, Berkeley School of Information Management and Systems
Database Management:: Ray R. Larson University of California, Berkeley School of Information Management and Systems
Ray R. Larson University of California, Berkeley School of Information Management and Systems SIMS 257: Database Management
IS 257 Spring 2004 2004.01.20 - SLIDE 1
Overview
Announcements
TA Mayjane Co
2004.01.20 - SLIDE 2
Course Overview
Description of the Course Assignments Readings Grading Schedule Web site: http://sims.berkeley.edu/courses/is257/s04
2004.01.20 - SLIDE 3
Course Description
This course is concerned with the design of the database itself -- not with the design of database system software.
We will discuss DBMS internals only as they relate to the database and its design and structure
We will spend a fair amount time on database application design, especially on options for Web application database support -- but this will not be primary focus.
IS 257 Spring 2004 2004.01.20 - SLIDE 4
Assignments
Two kinds of assignments
Using a pre-built database for search and retrieval and database modification queries Designing, populating, and running queries against your own personal database
Types of database project
Individual Work related Course only Projects from around campus that need doing Group Course related SIMS Final project
IS 257 Spring 2004 2004.01.20 - SLIDE 5
Readings
Textbook is:
Jeffrey A. Hoffer, Mary B. Prescott and Fred R. McFadden. Modern Database Management (Sixth Edition). Prentice Hall (Pearson Educational) : Upper Saddle River, NJ, 2002. ISBN 0-13-061183-2
2004.01.20 - SLIDE 6
Grading
Grades will be based on:
Assignments (30%) Personal/Group Database project (60%) Class participation (10%) (No midterm or final)
2004.01.20 - SLIDE 7
Schedule
on website: http://sims.berkeley.edu/courses/is257/s04 /Schedule.html
2004.01.20 - SLIDE 8
What is a Database?
2004.01.20 - SLIDE 9
Database: A collection of similar records with relationships between the records. (Rowley)
bibliographic, statistical, business data, images, etc.
2004.01.20 - SLIDE 10
Database
A Database is a collection of stored operational data used by the application systems of some particular enterprise. (C.J. Date)
Paper Databases
Still contain a large portion of the worlds knowledge
2004.01.20 - SLIDE 11
2004.01.20 - SLIDE 12
2004.01.20 - SLIDE 13
2004.01.20 - SLIDE 14
Why DBMS?
History
50s and 60s all applications were custom built for particular needs File based Many similar/duplicative applications dealing with collections of business data Early DBMS were extensions of programming languages 1970 - E.F. Codd and the Relational Model 1979 - Ashton-Tate & first Microcomputer DBMS
IS 257 Spring 2004 2004.01.20 - SLIDE 15
File
Toys Addresses
Naughty
Nice Toys
2004.01.20 - SLIDE 16
2004.01.20 - SLIDE 17
DBMS Benefits
Minimal Data Redundancy Consistency of Data Integration of Data Sharing of Data Ease of Application Development Uniform Security, Privacy, and Integrity Controls Data Accessibility and Responsiveness Data Independence Reduced Program Maintenance
2004.01.20 - SLIDE 18
2004.01.20 - SLIDE 19
Database Environment
CASE Tools
User Interface
Application Programs
Repository
DBMS
Database
2004.01.20 - SLIDE 20
Database Components
DBMS
===============
Design tools
Table Creation Form Creation Query Creation Report Creation Procedural language compiler (4GL) ============= Run time
Form processor Query processor Report Writer Language Run time
Database
Application Programs
2004.01.20 - SLIDE 21
2004.01.20 - SLIDE 22
PC Databases
E.G. Access FoxPro Dbase Etc.
2004.01.20 - SLIDE 23
Centralized Databases
Cental Computer
2004.01.20 - SLIDE 24
Distributed Databases
Location B
Location C
computer
computer
computer
Location A
IS 257 Spring 2004
Homogeneous Databases
2004.01.20 - SLIDE 26
Distributed Databases
Heterogeneous Or Federated Databases Database Server Client
Remote Comp.
Remote Comp.
2004.01.20 - SLIDE 27
2004.01.20 - SLIDE 28
WorkGroup databases
Small group use where everyone has access to the database over a LAN
Departmental databases
Larger than a workgroup but similar
Enterprises databases
For the entire organization over an intranet (or sometimes the internet)
IS 257 Spring 2004 2004.01.20 - SLIDE 29
Read
Read current data from the database
Update
Update or modify current database data
Delete
Remove current data from the database
2004.01.20 - SLIDE 30
Entity
Person, Place, Thing, Event, Concept...
Attributes
Data elements (facts) about some entity Also sometimes called fields or items or domains
Data values
instances of a particular attribute for a particular entity
2004.01.20 - SLIDE 31
File
Collection of records AKA Relation or Table in relational DBMS
2004.01.20 - SLIDE 32
Primary Key
an attribute or set of attributes that uniquely identifies each record in a file
2004.01.20 - SLIDE 33
DBA
Database Administrator - person responsible for the Database Administration Function
2004.01.20 - SLIDE 34
Database Administration
Responsibility for physical database design and technical issues in database management
Data Steward
Responsibility for some subset of the organizations data, and all of the interactions (applications, user access, etc.) for that data
2004.01.20 - SLIDE 35
2004.01.20 - SLIDE 36
Models (1)
Application 1 Application 2 Application 3 Application 4
External Model
Application 1
External Model
External Model
External Model
Conceptual requirements
Application 2
Conceptual requirements
Application 3
Conceptual requirements
Application 4
Conceptual Model
Logical Model
Internal Model
Conceptual requirements
2004.01.20 - SLIDE 37
Publisher
Subjects
2004.01.20 - SLIDE 38
2004.01.20 - SLIDE 39
Book ID 1 2 3 4 5
Title pubid Introductio The history New stuff ab Another title And yet more
2 4 3 2 1
Author id 1 2 3 4 5
Book ID 1 2 3 4 4
Subid 2 1 3 2 3
Subid Subject 1 cataloging 2 history 3 stuff
2004.01.20 - SLIDE 40
Publisher
Subjects
2004.01.20 - SLIDE 41
2004.01.20 - SLIDE 42
Design 1
Conversion 3
Integration 4 Operations 5
2004.01.20 - SLIDE 43
Design
Determination of the needs of the organization Development of the Conceptual Model of the database
Typically using Entity-Relationship diagramming techniques
2004.01.20 - SLIDE 44
Physical Creation
Development of the Physical Model of the Database
data formats and types determination of indexes, etc.
Load a prototype database and test Determine and implement security, privacy and access controls Determine and implement integrity constraints
2004.01.20 - SLIDE 45
Conversion
Convert existing data sets and applications to use the new database
May need programs, conversion utilities to convert old data to new formats.
2004.01.20 - SLIDE 46
Integration
Overlaps with Phase 3 Integration of converted applications and new applications into the new database
2004.01.20 - SLIDE 47
Operations
All applications run full-scale Privacy, security, access control must be in place. Recovery and Backup procedures must be established and used
2004.01.20 - SLIDE 48
2004.01.20 - SLIDE 49
2004.01.20 - SLIDE 50
Next Time
2004.01.20 - SLIDE 51