Sei sulla pagina 1di 33

Lecture #1: Course Introduction

CPSC 608: Advanced Database Systems

Hoh In
Texas A&M University

CPSC 608: L#1 1 Copyright © 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 © 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 © 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 © Hoh In


File Processing vs. Database Processing

CPSC 608: L#1 5 Copyright © Hoh In


CI-DBMS vs. DI-DBMS

CPSC 608: L#1 6 Copyright © Hoh In


Example: An Engineering Firm

CPSC 608: L#1 7 Copyright © Hoh In


What are the issues?
• Layers of Transparency

CPSC 608: L#1 8 Copyright © 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 © 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 © 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 © 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 © Hoh In


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

CPSC 608: L#1 13 Copyright © Hoh In


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

CPSC 608: L#1 14 Copyright © 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 15 Copyright © Hoh In


The Theme of this Course

How to develop ………


the best …….
distributed ……
Database?

CPSC 608: L#1 16 Copyright © 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 © 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 © Hoh In
Future Networks

Source: OMG Documentation


CPSC 608: L#1 Copyright © 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 © 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 © Hoh In


Stakeholder Concern
Customer •
Schedule & Budget estimation

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 © 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 © 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 and Wireless Database Systems
– Part III: Group Projects
– Exams, Project, Homework Assignments
– BBS and Lab Days
• Epilogue and Feedback

CPSC 608: L#1 24 Copyright © Hoh In


Part I: Technology Review
• Distributed Computing Environment
– Distributed Infrastructure (e.g., .NET, EJB, CORBA)
– XML (e.g., WML for Wireless)
• Basic Database Review (Chapter 1 and 2)
– Relational DBMS, MS Access, Oracle DBMS
• Web Database
– Java, Servlet, Web server, ASP, JSP, SOAP
• Wireless Database
– J2ME, The .NET Compact Framework

CPSC 608: L#1 25 Copyright © Hoh In


Part II: Distributed Database Systems (DDS)
• DB Basic Concepts (Chapter 1,2)
• DDS Architecture (Chapter 4)
• DDS Design (Chapter 5)
• Semantic Data Control (Chapter 6)
• Query Processing:Decomposition,
Localization, Optimization (Chapter 7, 8, 9)
• Transaction Management (Chapter 10)
• Database Interoperability (Chapter 15)
• Database Issues (Chapter 16)

CPSC 608: L#1 26 Copyright © Hoh In


Exams (40 pts)
• Midterm I -- Test for Part I (20 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 (20 points)
– To test your understanding distributed database theories and
models.

CPSC 608: L#1 27 Copyright © Hoh In


Group Project (30 points)
• Topic: Distributed, Wireless Database Systems

• Deliverables
– Web site (all documents, source codes, useful links, etc)
– Program components; Demo; Documentation (User, Reference,
Installation Manuals)
– Demonstration for all CS/EE/other students, faculty
– Poster and 1-pager advertisement
• Grading Criteria (each - up to 5 points)
– Creativity (Something new), Difficulty, Completeness, Demo, Report,
Code Quality
– Excellent (5 pts); Very Good (4 pts); Good (3); Fair (2); Poor (1)

CPSC 608: L#1 28 Copyright © Hoh In


Homework Assignments (30 points)
• HW#1 (5 pts):
– Internet application (based on Oracle database)
• HW#2 (5 pts):
– Web-based Database application
• HW#3 (20 pts):
– Case Studies: In-depth Paper writing and presentation
• Grading for each HW:
– No return (- 100%);
– Missing capabilities, delayed, poor quality (50%)
– Satisfied (80%)
– Excellent (100%)

CPSC 608: L#1 29 Copyright © Hoh In


Lab Days
• Lab 1: MS Access
• Lab 2: Oracle & SQL
• Lab 3: Web-based Database
• Lab 4: Wireless Database Technologies
• Lab 5: DB Interoperability (.NET, EJB, CORBA)

CPSC 608: L#1 30 Copyright © Hoh In


Grading Ranges
• A: More than and equal to 90
• B: More than and equal to 80 and less than 90
• C: More than and equal to 70 and less than 80
• F: Others.

CPSC 608: L#1 31 Copyright © 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 32 Copyright © 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 © Hoh In

Potrebbero piacerti anche