1 / 8

Session - 21 DISTRIBUTED DATABASE DESIGN AND ADMINISTRATION

Matakuliah : M0184 / Pengolahan Data Distribusi Tahun : 2005 Versi :. Session - 21 DISTRIBUTED DATABASE DESIGN AND ADMINISTRATION. DISTRIBUTED DATABASE DESIGN. OBJECTIVES. Software life cycle The design of the global conceptual schema Logical design for distributed database.

matana
Télécharger la présentation

Session - 21 DISTRIBUTED DATABASE DESIGN AND ADMINISTRATION

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Matakuliah : M0184 / Pengolahan Data Distribusi Tahun : 2005 Versi : Session - 21DISTRIBUTED DATABASE DESIGN AND ADMINISTRATION DISTRIBUTED DATABASE DESIGN

  2. OBJECTIVES • Software life cycle • The design of the global conceptual schema • Logical design for distributed database

  3. Software Life Cycle • Careful analysis of the feasibility and potential of the proposed software system is carried out • Requirement collection and analysis phase involves extensive discussion between designer and end-user • The design phase involves the detailed design of the system • During the implementation phase, the system is fully implemented and tested • Evaluating the newly developed system against those requirements • Operational phase

  4. Logical Design for Distributed database Global Enterprise Model Global Conceptual Schema Schema Integrator Local Participant Schema

  5. Schema Integration • Schema integration is relatively recent concept, relating specifically to the problems associated with DDBs • The integration of a set of pre-existing local schema into single global schema • Requires a semantically rich data model  using subset of another entity (Example : patient is of outpatient) • The ability of define subset called Generalization

  6. Subset Entity Test Result Out Patient Consultant Referral Name Number Address Person CName CNumber Diagnosis Married Children Patient

  7. Interoperability Without using Global Schema • In Heterogeneous environment, construction of global schema can be too onerous task • A global schema essential for tight integration between DB, where loosely-constructed federation may not be worthwhile. • Logical DDB design effort goes to export schema • The export schema represent view defined over part of the DDB only • User define their own views at run-time using powerful query language

  8. Object Oriented approach to schema Integration • Object oriented is semantically rich data model • Method can be used to provide powerful integration functions • Provides the possibility of reuse by global user of local application program • The integration of multimedia DB • Equally applicable whether or not a global schema is used

More Related