advance dbms lecture2

8/7/2019 Advance DBMS Lecture2

1/35

CPSC 608: L#2 1 Copyright 1999 Hoh In

Lecture #2: Current Issues and

Potential Class Project Topics

CPSC 608: Distributed Database Systems

January 20, 1999

Hoh In

Texas A&M University


2/35


Review:File Processing vs. Database Processing


3/35


Review: CI-DBMS vs. DI-DBMS


4/35


Review: Layers of Transparency


5/35


Review: The Theme of this Course

How to develop

the best .

distributed

Database?


6/35


Review: Technology Review (Part I)

Distributed Computing Environment

CORBA COM/DCOM

JavaBeans / EJB (Enterprise JavaBeans)

XML Basic Database Review

Relational DBMS

MS Access Oracle DBMS

Basic Network Review


7/35


Review: Distributed Database Systems (Part II)

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)


8/35


The Goals of Today

Understand the current issues of Distributed

Database Systems Explore the topics for potential class projects


9/35


Contents

Prologue: Team Building and Operation

Overview of the Current Issues

Suggestions of Class Project Topics

Epilogue and Feedback


10/35


Prologue: Class Project Concept of Operation

RFP (Request For Proposal) &

Presentation of potential topics

Review

Team building

Research (papers, products)

Submit proposals

Selected projects

Critiques

Archive


11/35


Team Structure Team Size: Variable (from 2 to the class size)

Team Structure

Project Manager

Evaluate the performance (grading: 50 points) of assistant

manager and/or team members

Grading constraints: summation of grading points should be(team members * 50 points) like fixed budget

Assistant Manager (if the project is large)

Evaluate the performance of team members and report to

Project manager Team member

Evaluate the performance of project manager and assistant

manager (and suggest to the instructor)


12/35


Manager Responsibilities Submit project proposal

Select assistant managers and divide students into teams

Plan and document the project schedule Lead and guide team members in developing a reference architecture

Document the reference architecture

Insure that team members have adequate resources to implement the

application (e.g. software, computers, reference material, web projectaccounts)

Submit weekly status report i.e. assess project progress on a weekly

basis

Insure that the requirements of the project are being met

Insure that project deadlines are being met

Assist with programming tasks where needed

Prepare project presentation


13/35


Assistant Manager Responsibilities

Coordinate team meetings

Communicate with customer to gather the right requirements Document the application requirements

Lead and guide team members in developing the application specific

architecture, while utilizing the reference architecture

Document the application specific architecture Lead and guide team members in selecting an implementation

approach

Assign specific programming tasks to team members

Insure that each team member is making adequate progress on his/herassigned tasks

Assist with programming tasks where needed

Submit weekly status report


14/35


Team Member Responsibilities

Contribute to the development of the reference architecture

Contribute to the development of the application specificarchitecture

Do research on implementation approaches (i.e. Corba,

COM/DCOM, XML, Oracle, MS Access)

Become educated on the programming tools/languages

needed to implement the application

Do the majority of programming tasks

Submit weekly status report


15/35


Activity Analysis I (99 Fall)A c t i v i t y 1 2 3 4 5 6 7 T o ta l

M a n a g e m e n t

L ife C yc le P lann ing 1 0 .5 7 1 0.5 10

C ontro l and M on itoring 0.75 0.5 0 .5 1 .5 3.25

C lient In teraction 3.5 1.5 5

T eam Interac tion 24.5 1 5.5 2 0 .5 17 17 7.5 2 104

ARB Rev iew

E n v i r o n m e n t

T ra in ing and P reparation 0.5 10 27.5 24.5 16 7 .5 86

Insta lla tion and A dm inis tration 3 4 5.5 2 2 16.5

Projec t W eb S ite & D e liverab les M anagem ent 5 .5 2 3.5 5 .5 1.5 1 19

Custom Toolsmith ing

R e q u i r e m e n t s

W inW in Negot ia t ions

O pera tiona l C oncept D escrip tion 4.5 3 .5 10.5 18 .5

S ys tem and Softw are R equirem ents D efin ition 8.5 11 2 21.5

D e s i g n

S ystem and S oftw are A rch itecture D escrip tion 2 4 13 .5 5 24.5

C O T S Assessm ent and E va luation 1 1

CO TS Base l in ing

I m p l e m e n t a t i o n

P roto typ ing 2 3 3 49 72 129

C ritica l C om ponent Im p lem enta tion 9 .5 25 36 70.5A s s e s s m e n t

Bus iness C ase Ana lys is 1 1

Fea sibi l ity Rat ionale D escr ipt ion

T est P lann ing 4 4

D e p l o y m e n t

Trans i tion and S uppor t Planning


16/35


Activity Analysis II

Total Man Hours Consumed by

Activity

0

50

100

150200

250

ManHours Management

Environment

Requirements

DesignImplementation


17/35


Activity Analysis III

Weekly Man Hours Consumed by

Activity

0

20

40

60

80

100

120

1 2 3 4 5 6 7

Week

ManHour

Management

Environment

Requirements

Design

Implementatio

n


18/35


Deliverables

Document

Based on MBASE (Model-Based Architecting andSoftware Engineering)

Home page: http://sunset.usc.edu/MBASE/mbase.html

Guideline: http://sunset.usc.edu/classes/cs577a_99/guidelines/Deliverables.pdf

Operational Concept Description (OCD) System and Software Requirements Definition (SSRD)

System and Software Architecture Description (SSAD)

Life cycle Plan (LCP)

Feasibility Rationale Description (FRD)

Product: Prototypes

Critiques


19/35


Contents






20/35


Overview of Current Issues

Data Warehousing

XML-based On-Line Transaction Systems

Push-based Technologies

Mobile Database


21/35


Data Warehousing Need: A collection of technologies aimed at improving

decision making

Solution: a subject-oriented collection of data integratedfrom various operational databases

Research Issues

Data quality: data accessibility, interpretability, usefulness,believability, validation

Data warehouse management: deployment of decentralized

datamarts

Materialized view maintenance Query optimization and physical design

Data integration (including data extraction, cleaning, loading and

refreshing)


22/35


Architecture of a Data Warehouse


23/35


Centralized vs. Decentralized Data Warehouse

Fig. 16.4 Decentralized

Fig. 16.3 Centralized


24/35


XML-based On-Line Transaction Systems

Needs:

Searching of data with structure (like global SQL query result ininternet)

Exchange data between applications

Solution: Common semistructured data -- XML

eXtended Markup Language Tutorial: http://msdn.microsoft.com/xml/tutorial/default.asp

Definition: a meta-markup language, a set of rules for creating

semantic tags used to describe data (MSDN)

E.g., Ed Wood

An Example of XML-based On-Line Transaction Systems:http://www.microsoft.com/msj/0200/aspxml/aspxml.asp


25/35


Push-based Technologies

Need: solution for the following asymmetries on data

delivery and dissemination network asymmetry (different bandwidth: upstream vs. downstream) imbalance between the number of clients and the number of servers

differences in the amount of data transmitted between servers and clients

data volatility (data change)

Solution: Push-based techniques (vs. pull-based)

Challenges:

Need a priori where and when to look for data

generation of a data transmission schedule to meet clients needs

managing client caches to minimize the average wait time

propagating data updates to all the clients


26/35


Mobile Database

Need: building DBMS in mobile environment

Characteristics of mobile environment restricted network bandwidth

limited life-time power supplies (batteries)

limited number of mobile stations (vs. mobile units)

movement of mobile units

Issues:

communication characteristics

mobility

portability


27/35


Contents






28/35


Topic 1: Intranet for CS Dept.

Purpose: Develop intranet systems for Computer

Science Dept. Related URL:

http://www.cs.tamu.edu/intranet

http://www.cs.tamu.edu/intranet/doc/proj619/design/

Demo


29/35


Topic 2: IEESIM

Integrated, Exchangeable, Extendable, Shared

Information Mediator 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 interfacework

Using Shared Database among individual tools

Collecting information from various information sources (e.g.,

application, web sites) Customer: NASA JPL


30/35


Capabilities of IEESIM

Global Query Engine for IEESIM

SQL type query Provide global view

Data Integrity (checking and resolution)

Control Integrity

Management System (Indexing, optimization)

GUI (interface between users and IEESIM)

Data schema evolution support


31/35


Topic 3: Database Evolution Technique

Problem: Applications demand customization of database

(e.g., add/delete/change attributes, tables), but it degradesperformance

Solution approaches

Separation: layer-based system design may be able to prevent

change propagation from a layer to another Standardization: each application follows the standard/guideline

for their interoperability

Customer: GeoQuest


32/35


Topic 4: Migration of Legacy Databaseinto New On-Line Transaction System How does newly-designed On-Line Transaction

System cooperate with legacy database used inlegacy applications?

E.g., EMS (Energy Management System)

Presentation (RFP) Qing Zhao, EE


33/35


Project Consideration

Reliability

Through Distributed Transactions Performance

System Expandability

Complexity

Cost

Distributed of Control

Security


34/35


Contents


Overview of the Current Issues Suggestions of Class Project Topics



35/35



Any suggestion or feedback?

advance dbms lecture2

Documents