Unit 1: Database Systems: Architecture and Components Instructor: Qing Yan, M.D., Ph.D.

Unit 1: Database Systems: Architecture and Components

Instructor: Qing Yan, M.D., Ph.D.

INSTRUCTOR INFORMATIONInstructor Name and Credentials:

Qing Yan, M.D., Ph.D.Kaplan Email Address:

[email protected]

SEMINAR INFORMATIONSeminar Day and Time (EST):

Monday 10:00-11:00 PMAIM Instant Messenger Name:

[email protected] Office Hours (EST):Wednesday 8:00-9:00 PM, Monday 9:00-10:00

PM

COURSE MATERIALSTextbook InformationTitle: Data Modeling and Database Design,

1st Edition Author(s): Richard Scamell & Dr. Narayan

S. Umanath ISBN: ISBN-10: 1423900839 ISBN-13:

9781423900832Publisher: Cengage

COURSE DESCRIPTIONThis 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 OUTCOMESCourse 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 CALENDARUnit # and Topic Learning Activities Assessments

Unit 1: Welcome to Class

Self-Check Quiz Self-Check Quiz

Unit 2: Conceptual Data Modeling

Database Questions Assignment Rubric

Unit 3: Entity Relationship Modeling

Case Study Evaluation Assignment Rubric

Unit 4: The Relational Data Model

Database Questions Assignment Rubric

Unit 5: NormalizationDatabase Questions Assignment Rubric

Unit 6: Database Creation

Oracle Script FileGEL Reflection Paper

Assignment Rubric

Unit 7: Data ManipulationSQL Query Statements Assignment Rubric

Unit 8: Data Manipulation Continued

SQL Statements Assignment Rubric

Unit 9: Data Manipulation Continued

SQL Statements Assignment Rubric

Unit 10

Final Project Using DML & DDL Commands Assignment Rubric

INSTRUCTOR’S GRADING CRITERIA/TIMETABLEAll 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 pointsAfter one week (8-14 calendar days) late 30% deduction in pointsNo 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.

PROJECTSProjectsProjects 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 BOARDSThe 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 & AQuestions?

Unit 1 ObjectivesDefine 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 ListIntroduce yourself

Meet your classmates and professorComplete the reading

Textbook (Chapter 1) and Web Participate in the discussion board

20 pointsAttend the introductory seminar or complete

FLA quiz20 points


Key Concepts Data

Unorganized facts about things, events, activities, and transactions.

InformationData 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


TerminologyDataInformationMetadata

Chapter 1 – Database Systems: Architecture and Components

From: Umanath, N.S., & Scamell, R. (2007). Data Modeling and Database Design. Boston: Thomson Course Technology.

Data Management1. Creation of data2. Retrieval of data3. Update or modification of data4. Deletion of data

For that, data must be accessed and, for the ease of access, data must be organized.



ExerciseAssume 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?



Exercise (continued)Maybe like this?



Data ManagementOnly two approaches for accessing data

exist: Sequential access – from (n-1) records ->

the nth record Direct access – for ad hoc queryingImportant:

A DBMS facilitates access of data without burdening the user with details of how the data is physically organized.



History of Data Management


1950 1960 1970 1980 1990 2000

File systems

Hierarchical DBMS

Network DBMS

Relational DBMS

Object-oriented DBMS


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 StandardsOrganizations find it hard to enforce standards for naming data items as well as for accessing, updating, and protecting data.

Lack of Flexibility/MaintainabilityFile-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.



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 IndependenceThe structure of each file is embedded in the application programs.



Limitations of File-Processing Systems (continued)

Student ProcessingApplications

Faculty and StaffProcessingApplications

AlumniProcessingApplications

STUDENTFiles

ALUMNIFiles

FACULTY and STAFF Files

Users

Users

Users

Figure 1.1 An example of a fi le processing environment



So, What Is Desirable? Integrated data

Not data in isolation to be integrated by the application program/programmer

Data IndependenceApplication program(s) immune to changes in

storage structure and access strategyIndependent user views of data



History of Data ManagementIn 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 three-schema architecture: conceptual, internal and external schema.



Conceptual SchemaCore of the architectureRepresents the global view of the structure of

the entire database for a community of usersCaptures 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



Internal SchemaDescribes 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 dependentConcerned with the efficiency of data storage

and access mechanisms



External SchemaRepresents different user views, each

describing portions of the databaseTechnology independentViews are generated exclusively by logical

references



What is a Database System? A self-describing collection of integrated

records

Self-describingThe structure of the database (metadata) is recorded within the database system – not in the application programs.

IntegratedThe responsibility for 'integrating' data items as needed is assumed by the DBMS instead of the programmer.



Characteristics of a Database SystemDatabaseA 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



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.



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.



Components of a DBMSThe 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.




Query Language[SQL]

Data Manipulation Language[DML/SQL]

Security & Recovery[DCL/SQL]

Report Generator

Access RoutinesData Definition Language

[DDL/SQL]

Database Management System [DBMS]Software component

Figure 1.5 Components of a database system

Database{Contains Data}

Computer-aidedSof tware Engineering

Tools[CASE Tools]

Data Repository{Data Models

Metadata}

Data Dictionary{DBMS Metadata}

Components of a Database System



Student ProcessingApplications

Faculty and StaffProcessingApplications

AlumniProcessingApplications

DatabaseManagement

System

Users

Users

Users

Database

Figure 1.6 An example of a database system

An Example of a Database System


Types of Database SystemsNumber of users

Single-user Desktop database system

Multi-user Workgroup database system Enterprise database system

ScopeDesktop database systemWorkgroup database systemEnterprise database system



Some Commercial DBMSIBM & DB2:

www-306.ibm.com/software/data/db2/

Oracle: www.oracle.com/database/index.html

Microsoft & SQL Server: www.microsoft.com/sql/default.mspx



Important TermsData Integrity

(correct, consistent, complete and current)

Data Redundancy



Data ModelsA model is an expression of “observed or

unobservable” reality. Example: chair versus departmentA 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).



Steps in Database DesignConceptual design ---> Conceptual schema

capturing user-specified business rulesTool: e.g., ER modelingPresentation Layer ER Model

ER diagram and semantic integrity constraints

Design-Specific ER ModelCoarse and fine level of granularity



Steps in Database Design (continued)

Logical Design ---> Logical schema Tool: normalizationArchitecture: hierarchical, network, or

relationalPhysical Design

Specifying internal storage structure and access strategies



SummarySyllabusClass policiesData, information, metadataData managementFeatures of database systemsData models and database design

Q & AQuestions?

Date post:	17-Jan-2016
Category:	Documents
Upload:	noel-pitts
View:	227 times
Download:	0 times

Unit 1: Database Systems: Architecture and Components Instructor: Qing Yan, M.D., Ph.D.

Documents