Download Document

Unit 1:
Database Systems: Architecture and Components
Instructor: Qing Yan, M.D., Ph.D.
INSTRUCTOR INFORMATION
 Instructor Name and Credentials:
Qing Yan, M.D., Ph.D.
 Kaplan Email Address:
QYan@kaplan.edu
SEMINAR INFORMATION
 Seminar Day and Time (EST):
Monday 10:00-11:00 PM
 AIM Instant Messenger Name:
qingyansf@gmail.com
 AIM Office Hours (EST):
Wednesday 8:00-9:00 PM, Monday 9:00-10:00 PM
COURSE MATERIALS
 Textbook Information
 Title: Data Modeling and Database Design, 1st
Edition
 Author(s): Richard Scamell & Dr. Narayan S.
Umanath
 ISBN: ISBN-10: 1423900839 ISBN-13: 9781423900832
 Publisher: Cengage
COURSE DESCRIPTION
 This course covers data modeling for health care
systems.
 Students will be introduced to the following topics:
 entity-relationship modeling,
 normal forms,
 database creation,
 data manipulation using SQL.
 Students will complete hands-on assignments and
case studies related to the health care industry.
COURSE OUTCOMES
 Course Outcomes: By the end of this course, you should
be able to:
 Produce an entity-relationship diagram.
 Apply the process of normalization.
 Create queries to solve problems.
 General Education Outcomes: the following General
Education outcomes are assessed during this course:
 Solve real-world problems using mathematical skills.
 Demonstrate college-level communication through the
composition of original materials in Standard American
English.
COURSE CALENDAR
Unit # and Topic
Learning Activities
Assessments
Self-Check Quiz
Self-Check Quiz
Unit 1: Welcome to Class
Database Questions
Assignment Rubric
Case Study Evaluation
Assignment Rubric
Database Questions
Assignment Rubric
Database Questions
Assignment Rubric
Oracle Script File
GEL Reflection Paper
Assignment Rubric
SQL Query Statements
Assignment Rubric
SQL Statements
Assignment Rubric
SQL Statements
Assignment Rubric
Final Project Using DML & DDL Commands
Assignment Rubric
Unit 2: Conceptual Data Modeling
Unit 3: Entity Relationship Modeling
Unit 4: The Relational Data Model
Unit 5: Normalization
Unit 6: Database Creation
Unit 7: Data Manipulation
Unit 8: Data Manipulation Continued
Unit 9: Data Manipulation Continued
Unit 10
INSTRUCTOR’S GRADING
CRITERIA/TIMETABLE
 All course projects submitted on time will be graded
within five days of their due date (the Sunday of the
following unit).
 Late work will be graded within five days of the
submission date.
 Discussion board grades will be updated each week no
later than Sunday of the week following the Unit’s
completion.
LATE POLICY (1)
 Extenuating Circumstances: Please contact me to
make alternative arrangements. We will work together
to come up with a mutually acceptable alternative. Prior
notification does not automatically result in a waiver of the
late penalties.
 Examples of extenuating circumstances: personal/family
member hospitalization, death in the family,
weather/environmental evacuation due to fire/hurricane.
Computer-related issues and internet connectivity
issues are not considered extenuating circumstances.
LATE POLICY (2)
Without Extenuating Circumstances:
 Up to one week (1-7 calendar days) late 20% deduction in
points
 After one week (8-14 calendar days) late 30% deduction in
points
 No work will be accepted more than two (2) weeks
after the due date.
 Note: In order for you to make up a quiz, exam or
discussion thread, you must contact me by email at least
one day prior to the day you want to make up the work so
that access can be provided. Additionally, you must notify
me by email when you have submitted late work.
PROJECTS
 Projects
Projects are assignments that require you to submit
coursework to the instructor via the dropbox.
 Projects are due Tuesday 11:59 pm ET of their assigned
Unit.
DISCUSSION BOARDS
The Discussion Board Requirement:
 Post a minimum of three posts per discussion
question. One initial response and two replies to your
classmates.
 Posting on a minimum of three different days, for
example: Wednesday, Friday and Monday.
 The first post must be made by Saturday.
Q&A
 Questions?
Unit 1 Objectives
 Define the difference between data, metadata, and
information
 Define what is a database and what is a database
management system
 Read about the role of data models in database design
Chapter 1 – Database Systems:
Architecture and Components
14
Unit 1 To-Do List
 Introduce yourself
Meet your classmates and professor
 Complete the reading
Textbook (Chapter 1) and Web
 Participate in the discussion board
20 points
 Attend the introductory seminar or complete FLA quiz
20 points
Chapter 1 – Database Systems:
Architecture and Components
15
Key Concepts
 Data
 Unorganized facts about things, events, activities, and
transactions.
 Information
 Data that has been organized into a specific context
such that it has value to its recipient.
 A database
 A self-describing collection of integrated files
Chapter 1 – Database Systems:
Architecture and Components
16
Terminology
 Data
 Information
 Metadata
From: Umanath, N.S., & Scamell, R. (2007). Data Modeling and Database Design. Boston: Thomson Course Technology.
Chapter 1 – Database Systems:
Architecture and Components
Data Management
1. Creation of data
2. Retrieval of data
3. Update or modification of data
4. Deletion of data
For that, data must be accessed and, for the ease
of access, data must be organized.
From: Umanath, N.S., & Scamell, R. (2007). Data Modeling and Database Design. Boston: Thomson Course Technology.
Chapter 1 – Database Systems:
Architecture and Components
18
Exercise
Assume you want to organize your DVD collection.
The only tool available is an Excel sheet. What
would your columns and rows in Excel look like?
From: Umanath, N.S., & Scamell, R. (2007). Data Modeling and Database Design. Boston: Thomson Course Technology.
Chapter 1 – Database Systems:
Architecture and Components
19
Exercise (continued)
Maybe like this?
From: Umanath, N.S., & Scamell, R. (2007). Data Modeling and Database Design. Boston: Thomson Course Technology.
Chapter 1 – Database Systems:
Architecture and Components
20
Data Management
Only two approaches for accessing data exist:
 Sequential access – from (n-1) records -> the nth
record
 Direct access – for ad hoc querying
Important:
A DBMS facilitates access of data without
burdening the user with details of how the data is
physically organized.
From: Umanath, N.S., & Scamell, R. (2007). Data Modeling and Database Design. Boston: Thomson Course Technology.
Chapter 1 – Database Systems:
Architecture and Components
21
History of Data Management
Object-oriented DBMS
Relational DBMS
Network DBMS
Hierarchical DBMS
File systems
1950
1960
1970
1980
1990
2000
From: Umanath, N.S., & Scamell, R. (2007). Data Modeling and Database Design. Boston: Thomson Course Technology.
Chapter 1 – Database Systems:
Architecture and Components
22
Limitations of File-Processing
Systems
 Lack of Data Integrity
Data integrity (data values are correct, consistent, complete, and
current) is often violated in isolated environments.

Lack of Standards
Organizations find it hard to enforce standards for naming data
items as well as for accessing, updating, and protecting data.

Lack of Flexibility/Maintainability
File-processing systems are not amenable to structural changes in
data and are therefore dependent upon a programmer who can
either write or modify program code.
Chapter 1 – Database Systems:
From: Umanath, N.S., & Scamell, R. (2007). Data Modeling and Database Design. Boston: Thomson Course Technology.
Architecture and Components
23
Limitations of File-Processing
Systems (continued)
The limitations to file-processing systems are due to:
 Lack of Data Integration
Data are separated and isolated in a file-processing
environment.
 Lack of Program-Data Independence
The structure of each file is embedded in the application
programs.
From: Umanath, N.S., & Scamell, R. (2007). Data Modeling and Database Design. Boston: Thomson Course Technology.
Chapter 1 – Database Systems:
Architecture and Components
24
Limitations of File-Processing
Systems (continued)
STUDENT
Files
Student
Processing
Applications
Users
FACULTY and
STAFF Files
Faculty and Staff
Processing
Applications
ALUMNI
Files
Alumni
Processing
Applications
Users
Users
Figure 1.1 An example of a file processing environment
From: Umanath, N.S., & Scamell, R. (2007). Data Modeling and Database Design. Boston: Thomson Course Technology.
Chapter 1 – Database Systems:
Architecture and Components
25
So, What Is Desirable?
 Integrated data
 Not data in isolation to be integrated by the application
program/programmer
 Data Independence
 Application program(s) immune to changes in storage
structure and access strategy
 Independent user views of data
From: Umanath, N.S., & Scamell, R. (2007). Data Modeling and Database Design. Boston: Thomson Course Technology.
Chapter 1 – Database Systems:
Architecture and Components
26
History of Data Management
In the 1970s, the Standards Planning and
Requirements Committee (SPARC) of the American
National Standards Institute (ANSI) proposed what
came to be known as the ANSI/SPARC threeschema architecture: conceptual, internal and
external schema.
From: Umanath, N.S., & Scamell, R. (2007). Data Modeling and Database Design. Boston: Thomson Course Technology.
Chapter 1 – Database Systems:
Architecture and Components
27
Conceptual Schema
 Core of the architecture
 Represents the global view of the structure of the




entire database for a community of users
Captures data specification (metadata)
Describes all data items and relationships between
data together with integrity constraints
Separates data from the program (or views from the
physical storage structure)
Technology independent
From: Umanath, N.S., & Scamell, R. (2007). Data Modeling and Database Design. Boston: Thomson Course Technology.
Chapter 1 – Database Systems:
Architecture and Components
28
Internal Schema
 Describes the physical structure of the stored data
(e.g., how the data is actually laid out on storage
devices)
 Describes the mechanism used to implement access
strategies (e.g., indexes, hashed addresses, etc.)
 Technology dependent
 Concerned with the efficiency of data storage and
access mechanisms
From: Umanath, N.S., & Scamell, R. (2007). Data Modeling and Database Design. Boston: Thomson Course Technology.
Chapter 1 – Database Systems:
Architecture and Components
29
External Schema
 Represents different user views, each describing
portions of the database
 Technology independent
 Views are generated exclusively by logical
references
From: Umanath, N.S., & Scamell, R. (2007). Data Modeling and Database Design. Boston: Thomson Course Technology.
Chapter 1 – Database Systems:
Architecture and Components
30
What is a Database System?
 A self-describing collection of integrated records
Self-describing
The structure of the database (metadata) is
recorded within the database system – not in the
application programs.
Integrated
The responsibility for 'integrating' data items as
needed is assumed by the DBMS instead of the
programmer.
From: Umanath, N.S., & Scamell, R. (2007). Data Modeling and Database Design. Boston: Thomson Course Technology.
Chapter 1 – Database Systems:
Architecture and Components
31
Characteristics of a Database
System
Database
A single, integrated set of files
Database Management System (DBMS)
A collection of general-purpose software that facilitates
the process of defining, constructing, and manipulating
a database for various applications
From: Umanath, N.S., & Scamell, R. (2007). Data Modeling and Database Design. Boston: Thomson Course Technology.
Chapter 1 – Database Systems:
Architecture and Components
32
What
is a Database?
A database is a self-describing collection of interrelated
files.
 Data consists of recorded facts that have implicit
meaning.
 Viewed through the lens of metadata, the meaning of
recorded data becomes explicit.
 A database is self-describing in that the metadata is
recorded within the database – not in applications
programs.
From: Umanath, N.S., & Scamell, R. (2007). Data Modeling and Database Design. Boston: Thomson Course Technology.
Chapter 1 – Database Systems:
Architecture and Components
33
What is a Database Management
System (DBMS)?
A DBMS is a collection of general-purpose software that
facilitates the processes of defining, constructing, and
manipulating a database.
From: Umanath, N.S., & Scamell, R. (2007). Data Modeling and Database Design. Boston: Thomson Course Technology.
Chapter 1 – Database Systems:
Architecture and Components
34
Components
of
a
DBMS
The major components of a DBMS include
 one or more query languages;
 tools for generating reports;
 facilities for providing security, integrity, backup and
recovery;
 a data manipulation language for accessing the
database;
 a data definition language used to define the
structure of data.
From: Umanath, N.S., & Scamell, R. (2007). Data Modeling and Database Design. Boston: Thomson Course Technology.
Chapter 1 – Database Systems:
Architecture and Components
35
Components of a Database System
Database Management System [DBMS]
Software component
Query Language
[SQL]
Report Generator
Security & Recovery
[DCL/SQL]
Data Definition Language
[DDL/SQL]
Data Repository
{Data Models
Metadata}
Data Manipulation
Language
[DML/SQL]
Access Routines
Data Dictionary
{DBMS Metadata}
Database
{Contains Data}
Computer-aided
Software Engineering
Tools
[CASE Tools]
Figure 1.5 Components of a database system
From: Umanath, N.S., & Scamell, R. (2007). Data Modeling and Database Design. Boston: Thomson Course Technology.
Chapter 1 – Database Systems:
Architecture and Components
36
An Example of a Database System
Student
Processing
Applications
Users
Database
Management
System
Faculty and Staff
Processing
Applications
Users
Database
Alumni
Processing
Applications
Users
Figure 1.6 An example of a database system
From: Umanath, N.S., & Scamell, R. (2007). Data Modeling and Database Design. Boston: Thomson Course Technology.
Chapter 1 – Database Systems:
Architecture and Components
37
Types of Database Systems
 Number of users
 Single-user

Desktop database system
 Multi-user


Workgroup database system
Enterprise database system
 Scope
 Desktop database system
 Workgroup database system
 Enterprise database system
From: Umanath, N.S., & Scamell, R. (2007). Data Modeling and Database Design. Boston: Thomson Course Technology.
Chapter 1 – Database Systems:
Architecture and Components
38
Some Commercial DBMS
 IBM & DB2:
www-306.ibm.com/software/data/db2/
 Oracle:
www.oracle.com/database/index.html
 Microsoft & SQL Server:
www.microsoft.com/sql/default.mspx
From: Umanath, N.S., & Scamell, R. (2007). Data Modeling and Database Design. Boston: Thomson Course Technology.
Chapter 1 – Database Systems:
Architecture and Components
39
Important Terms
 Data Integrity
(correct, consistent, complete and current)
 Data Redundancy
From: Umanath, N.S., & Scamell, R. (2007). Data Modeling and Database Design. Boston: Thomson Course Technology.
Chapter 1 – Database Systems:
Architecture and Components
40
Data Models
 A model is an expression of “observed or
unobservable” reality.
 Example: chair versus department
 A database represents some aspect of the real world
that is called the Universe of Interest.
 The initial step in the design process is the
requirements specification activity (i.e., business
rules).
From: Umanath, N.S., & Scamell, R. (2007). Data Modeling and Database Design. Boston: Thomson Course Technology.
Chapter 1 – Database Systems:
Architecture and Components
41
Steps
in
Database
Design
 Conceptual design ---> Conceptual schema
capturing user-specified business rules
 Tool: e.g., ER modeling
 Presentation Layer ER Model
ER diagram and semantic integrity constraints
 Design-Specific ER Model
Coarse and fine level of granularity
From: Umanath, N.S., & Scamell, R. (2007). Data Modeling and Database Design. Boston: Thomson Course Technology.
Chapter 1 – Database Systems:
Architecture and Components
42
Steps in Database Design
(continued)
 Logical Design ---> Logical schema
 Tool: normalization
 Architecture: hierarchical, network, or relational
 Physical Design
 Specifying internal storage structure and access
strategies
From: Umanath, N.S., & Scamell, R. (2007). Data Modeling and Database Design. Boston: Thomson Course Technology.
Chapter 1 – Database Systems:
Architecture and Components
43
Summary
 Syllabus
 Class policies
 Data, information, metadata
 Data management
 Features of database systems
 Data models and database design
Q&A
 Questions?