Lecture #1: Course Introduction

CPSC 608: Advanced Database Systems

January 18, 1999

Hoh In
Texas A&M University

CPSC 608: L#1 1 Copyright © 1999 Hoh In

 The Goals of Today
• Understand why do I need to take this Course
• Decide whether I have to continue or drop by
estimating course loading

CPSC 608: L#1 2 Copyright © 1999 Hoh In

 Contents
• Prologue: CI-DBMS vs DI-DBMS
• The Theme of this Course
• Overview of the Course Structure
• Epilogue and Feedback

CPSC 608: L#1 3 Copyright © 1999 Hoh In

 Prologue: CI-DBMS vs. DI-DBMS
• What is different?
– File system vs. Database
– DB vs. DBMS
– Central Integrated DBMS vs. Distributed Integrated
DBMS

CPSC 608: L#1 4 Copyright © 1999 Hoh In

 File Processing vs. Database Processing

CPSC 608: L#1 5 Copyright © 1999 Hoh In

 CI-DBMS vs. DI-DBMS

CPSC 608: L#1 6 Copyright © 1999 Hoh In

 Example: An Engineering Firm

CPSC 608: L#1 7 Copyright © 1999 Hoh In

 What are the issues?
• Layers of Transparency

CPSC 608: L#1 8 Copyright © 1999 Hoh In

 Data Independence
• A fundamental form of transparency in DBMS
• Immunity of user applications to changes in:
– the definition of data
– the organization of data
• Data Independence
– Physical data independence
• Hiding the details of the storage structure from user
applications
– Logical data independence
• Hiding logical structure of the database

CPSC 608: L#1 9 Copyright © 1999 Hoh In

 Network Transparency
• Called “distribution transparency”
• Feel no difference between CI-DBMS and DI-
DBMS
• Hiding the operational details of the network
• Two types:
– Location transparency
– Naming transparency

CPSC 608: L#1 10 Copyright © 1999 Hoh In

 Replication Transparency
• Data Replication
– Benefits:
• Performance (increase the locality of reference)
• Availability and Reliability (tolerance of single failure)
– Problems:
• Integrity among duplicated data
– Issues:
• The number of copies of database object
• Distribution of duplicated data
• Replication Transparency
– Hiding the operational details of duplicated data
CPSC 608: L#1 11 Copyright © 1999 Hoh In
 Fragmentation Transparency
• Break each database relation down into smaller
fragments
– For performance, availability, reliability
– Two types:
• Horizontal fragmentation: divide the tuples (rows)
• Vertical fragmentation: divide the attributes (columns)
• Hiding the operational details of fragmentation
– Support a global query
• Inside the system, it will be translated into several fragment
queries

CPSC 608: L#1 12 Copyright © 1999 Hoh In

 Transparency Issues
• Who should provide what transparency?
• How do existing systems fare?

CPSC 608: L#1 13 Copyright © 1999 Hoh In

 Other Issues?
• Reliability
– Through Distributed Transactions
• Performance
• System Expandability
• Complexity
• Cost
• Distributed of Control
• Security

CPSC 608: L#1 14 Copyright © 1999 Hoh In

 Contents
• Prologue: Components vs. Lego Blocks
• The Theme of this Course
• Overview of the Course Structure
• Epilogue and Feedback

CPSC 608: L#1 15 Copyright © 1999 Hoh In

 The Theme of this Course

How to develop ………

the best …….
distributed ……
Database?

CPSC 608: L#1 16 Copyright © 1999 Hoh In

 Why Database?
• An integrated collection of data elements derived
from an application
– e.g., the data associated with a banking application or
an airline reservation system
– DBMS: a software interface between the user and the
database
• Allows designers to structure their information
• Allows users to query and modify that information
• Helps manage very large amounts of data and many concurrent
operations on the data

CPSC 608: L#1 17 Copyright © 1999 Hoh In

 Why Distributed?

Sales
Engineering
Accounting

Manufacturing

Shipping/ Payables/
Receiving Inventory Receivables

• Distributed Hardware needs Distributed Software !

Source: OMG Documentation

CPSC 608: L#1 Copyright © 1999 Hoh In
 Future Networks

Source: OMG Documentation

CPSC 608: L#1 Copyright © 1999 Hoh In
 Focus on Interoperability

• There will not be consensus on hardware platforms;

• There will not be consensus on operating systems;
• There will not be consensus on network protocols;
• There will not be consensus on application formats.

There must be consensus

on interoperability.

Source: OMG Documentation

CPSC 608: L#1 20 Copyright © 1999 Hoh In
 How to define “The Best”?
• Stakeholder-sensitive
• Domain-sensitive
– Real-time systems vs. Human-life critical systems
• Situation- or Environment-sensitive
• Evolution-sensitive
– Now vs Future

CPSC 608: L#1 21 Copyright © 1999 Hoh In

 Stakeholder Concern
• Schedule & Budget estimation
Customer • Feasibility & Risk assessment
User • Consistency with requirements and usage
scenarios
Architecture and • Requirements traceability
• Support of tradeoff analysis
System Engineer • Completeness, consistency of architecture
Developer • Sufficient details for design
• Reference on selecting/assembling components

Maintainer • Guidance of s/w modification and

architecture evolution

CPSC 608: L#1 22 Copyright © 1999 Hoh In

 How to Develop?
• Distributed Database Design
• Distributed Query Processing
• Distributed Directory Management
• Distributed Concurrency Control
• Distributed Deadlock Management
• Reliability of Distributed DBMS
• Operating System Support
• Heterogeneous Databases

CPSC 608: L#1 23 Copyright © 1999 Hoh In

 Contents
• Prologue: CI-DBMS vs. DI-DBMS
• The Theme of this Course
• Overview of the Course Structure
– Part I: Technology Review
– Part II: Distributed Database Systems
– Part III: Group Projects
– Homework Assignments
– Class Project and Exam
– BBS and Lab Days
• Epilogue and Feedback

CPSC 608: L#1 24 Copyright © 1999 Hoh In

 Part I: Technology Review
• Distributed Computing Environment
– CORBA
– COM/DCOM
– JavaBeans / EJB (Enterprise JavaBeans)
– XML
• Basic Database Review
– Relational DBMS
– MS Access
– Oracle DBMS
• Basic Network Review
CPSC 608: L#1 25 Copyright © 1999 Hoh In
 Part II: Distributed Database Systems (DDS)
• DDS Architecture (Chapter 4)
• DDS Design (Chapter 5)
• Semantic Data Control (Chapter 6)
• Query Processing:Decomposition,
Localization, Optimization (Chapter 7, 8)
• Transaction Management (Chapter 10)
• Database Interoperability (Chapter 15)

CPSC 608: L#1 26 Copyright © 1999 Hoh In

 Part III: Group Projects
• Class Project
– Integrated, Exchangeable, Extendable, Shared Information Mediator
(IEESIM)
• Integrated views (information fusion) from different information
– Benefits: transparency; verification and validation of information
• Support of Exchangeable Data Format Flexibility (e.g., XML)
• Easy to extend to third-party tools without significant interface work
• Using Shared Database among individual tools
• Collecting information from various information sources (e.g., application,
web sites)
– [Team] Application development and its documentation (300 points)
– [Individual] Critiques OR Research Term paper (100 points)
• Write your critiques for improving your software development process
• Develop a research idea and write a paper

CPSC 608: L#1 27 Copyright © 1999 Hoh In

 Homework Assignments
• Total 300 points
• TBD, but
– MS Access
– Oracle
– Normalization of RDB
– Reading assignment
• Pop-Quiz: verification of your reading

CPSC 608: L#1 28 Copyright © 1999 Hoh In

 Exams
• Midterm I -- Test for Part I (150 points)
– To test your understanding technology review so that you are
ready to apply this knowledge to build up your distributed database
systems
• Midterm II -- Test for Part II (150 points)
– To test your understanding technology review so that
you are ready to apply this knowledge to build up your
distributed database systems

CPSC 608: L#1 29 Copyright © 1999 Hoh In

 BBS and Lab Days
• BBS (Bulletin Board System) is available
– For What?
• To communicate efficiently between me and you
– Ask questions through the BBS so that I don’t need to repeat to answer
the similar questions
– Post your opinions and suggestions for class improvement
• To communicate efficiently among all of you
– You can also answer the questions your colleagues ask. Note that I am
not the only person who I have to answer. I will count on the persons as
an eager participator (which means an opportunity to get extra bonus)

• Lab Days will be determined if necessary

– Potential times: after 7pm (1 or 2 hours)
– For What: WinWin, CORBA, DCOM, JavaBeans, MS Access, Oracles

CPSC 608: L#1 30 Copyright © 1999 Hoh In

 Grading Ranges

1000

B A
CPSC 608: L#1 31 Copyright © 1999 Hoh In
 Contents
• Prologue: Components vs. Lego Blocks
• The Theme of this Course
• Overview of the Course Structure
• Epilogue and Feedback

CPSC 608: L#1 32 Copyright © 1999 Hoh In

 Epilogue and Feedback
• I want my class to be:
– Dynamic/Reflective
– Productive
– Useful (in your future career)
– Efficient and Effective
• What do you earn through this class?

CPSC 608: L#1 33 Copyright © 1999 Hoh In