Advance DBMS Lecture2 | Databases | Data Warehouse

Lecture #2: Current Issues and Potential Class Project Topics

CPSC 608: Distributed Database Systems
January 20, 1999

Hoh In Texas A&M University

CPSC 608: L#2

1

Copyright © 1999 Hoh In

Review:File Processing vs. Database Processing

CPSC 608: L#2

2

Copyright © 1999 Hoh In

Review: CI-DBMS vs. DI-DBMS

CPSC 608: L#2

3

Copyright © 1999 Hoh In

Review: Layers of Transparency

CPSC 608: L#2

4

Copyright © 1999 Hoh In

Review: The Theme of this Course

How to develop ……… the best ……. distributed …… Database?

CPSC 608: L#2

5

Copyright © 1999 Hoh In

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
CPSC 608: L#2

6

Copyright © 1999 Hoh In

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)

CPSC 608: L#2

7

Copyright © 1999 Hoh In

The Goals of Today
• Understand the current issues of Distributed Database Systems • Explore the topics for potential class projects

CPSC 608: L#2

8

Copyright © 1999 Hoh In

Contents
• • • • Prologue: Team Building and Operation Overview of the Current Issues Suggestions of Class Project Topics Epilogue and Feedback

CPSC 608: L#2

9

Copyright © 1999 Hoh In

Prologue: Class Project Concept of Operation
RFP (Request For Proposal) & Presentation of potential topics Submit proposals Review
<accepted>

Archive
<rejected>

Selected projects

Team building

Critiques

Research (papers, products)
CPSC 608: L#2

10

Copyright © 1999 Hoh In

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)
CPSC 608: L#2

11

Copyright © 1999 Hoh In

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 project accounts) 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
12
Copyright © 1999 Hoh In

• • • • •

CPSC 608: L#2

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/her assigned tasks Assist with programming tasks where needed Submit weekly status report
13
Copyright © 1999 Hoh In

CPSC 608: L#2

Team Member Responsibilities
• Contribute to the development of the reference architecture • Contribute to the development of the application specific architecture • 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

CPSC 608: L#2

14

Copyright © 1999 Hoh In

Activity Analysis I (‘99 Fall)
A c tiv it y M anagem ent L ife C yc le P la n n in g C o n tro l a n d M o n ito rin g C lie n t In te ra c tio n T e a m In te ra c tio n A R B R e v ie w E n v iro n m e n t T ra in in g a n d P re p a ra tio n In s ta lla tio n a n d A d m in is tra tio n P ro je c t W e b S ite & D e liv e ra b le s M a n a g e m e n t C u s to m T o o ls m ith in g R e q u ire m e n ts W inW in N e g o tia tio n s O p e ra tio n a l C o n c e p t D e s c rip tio n S ys te m a n d S o ftw a re R e q u ire m e n ts D e fin itio n D e s ig n S ys te m a n d S o ftw a re A rc h ite c tu re D e s c rip tio n C O T S A s s e s s m e n t a n d E v a lu a tio n C O T S B a s e lin in g Im p le m e n ta tio n P ro to typ in g C ritic a l C o m p o n e n t Im p le m e n ta tio n Assessm ent B u s in e s s C a s e A n a lys is F e a s ib ility R a tio n a le D e s c rip tio n T e s t P la n n in g D e p lo y m e n t T ra n s itio n a n d S u p p o rt P la n n in g 1 2 3 4 7 1 .5 17 5 1 0 .5 17 6 0 .5 1 .5 7 .5 2 7 T o ta l 10 3 .2 5 5 104 1 0 .5 0 .7 5 0 .5 3 .5 2 4 .5 1 5 .5 2 0 .5

0 .5 5 .5

10 2

2 7 .5 2 4 .5 3 4 3 .5 5 .5

16 5 .5 1 .5

7 .5 2 1

2

86 1 6 .5 19

4 .5 8 .5

3 .5 11 2

1 0 .5 2 4 1 1 3 .5 5

1 8 .5 2 1 .5 2 4 .5 1

2

3

3 9 .5

49 25 1 4

72 36

129 7 0 .5 1 4

CPSC 608: L#2

15

Copyright © 1999 Hoh In

Activity Analysis II
Total Man Hours Consumed by Activity
250 200 150 100 50 0 Management Environment Requirements Design Implementation

CPSC 608: L#2

Man Hours

16

Copyright © 1999 Hoh In

Activity Analysis III
Weekly Man Hours Consumed by Activity
120 100 M nH u a o rs 80 60 40 20 0 1 2 3 4 Week 5 6 7 Requirements Design Implementatio n Management Environment

CPSC 608: L#2

17

Copyright © 1999 Hoh In

Deliverables
• Document
– Based on MBASE (Model-Based Architecting and Software 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
CPSC 608: L#2

18

Copyright © 1999 Hoh In

Contents
• • • • Prologue: Team Building and Operation Overview of the Current Issues Suggestions of Class Project Topics Epilogue and Feedback

CPSC 608: L#2

19

Copyright © 1999 Hoh In

Overview of Current Issues
• • • • Data Warehousing XML-based On-Line Transaction Systems Push-based Technologies Mobile Database

CPSC 608: L#2

20

Copyright © 1999 Hoh In

Data Warehousing
• Need: A collection of technologies aimed at improving decision making • Solution: a subject-oriented collection of data integrated from 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)
CPSC 608: L#2

21

Copyright © 1999 Hoh In

Architecture of a Data Warehouse

CPSC 608: L#2

22

Copyright © 1999 Hoh In

Centralized vs. Decentralized Data Warehouse

Fig. 16.3 Centralized

Fig. 16.4 Decentralized
CPSC 608: L#2

23

Copyright © 1999 Hoh In

XML-based On-Line Transaction Systems
• Needs:
– Searching of data with structure (like global SQL query result in internet) – 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., <director>Ed Wood</director>

• An Example of XML-based On-Line Transaction Systems:
http://www.microsoft.com/msj/0200/aspxml/aspxml.asp
CPSC 608: L#2

24

Copyright © 1999 Hoh In

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
25
Copyright © 1999 Hoh In

CPSC 608: L#2

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

CPSC 608: L#2

26

Copyright © 1999 Hoh In

Contents
• • • • Prologue: Team Building and Operation Overview of the Current Issues Suggestions of Class Project Topics Epilogue and Feedback

CPSC 608: L#2

27

Copyright © 1999 Hoh In

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

CPSC 608: L#2

28

Copyright © 1999 Hoh In

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 interface work – Using Shared Database among individual tools – Collecting information from various information sources (e.g., application, web sites)

• Customer: NASA JPL

CPSC 608: L#2

29

Copyright © 1999 Hoh In

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

CPSC 608: L#2

30

Copyright © 1999 Hoh In

Topic 3: Database Evolution Technique
• Problem: Applications demand customization of database (e.g., add/delete/change attributes, tables), but it degrades performance • 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

CPSC 608: L#2

31

Copyright © 1999 Hoh In

Topic 4: Migration of Legacy Database into New On-Line Transaction System
• How does newly-designed On-Line Transaction System cooperate with legacy database used in legacy applications? • E.g., EMS (Energy Management System) • Presentation (RFP)
– Qing Zhao, EE

CPSC 608: L#2

32

Copyright © 1999 Hoh In

Project Consideration
• Reliability
– Through Distributed Transactions

• • • • • •

Performance System Expandability Complexity Cost Distributed of Control Security

CPSC 608: L#2

33

Copyright © 1999 Hoh In

Contents
• • • • Prologue: Team Building and Operation Overview of the Current Issues Suggestions of Class Project Topics Epilogue and Feedback

CPSC 608: L#2

34

Copyright © 1999 Hoh In

Epilogue and Feedback
• Any suggestion or feedback?

CPSC 608: L#2

35

Copyright © 1999 Hoh In

Sign up to vote on this title
UsefulNot useful

Master Your Semester with Scribd & The New York Times

Special offer for students: Only $4.99/month.

Master Your Semester with a Special Offer from Scribd & The New York Times

Cancel anytime.