DOK 322 DBMS Database Design Hacettepe University Department

“DOK 322 DBMS” Database Design Hacettepe University Department of Information Management DOK 322: Database Management Systems Y. T.

“DOK 322 DBMS” Last Time F File Management Systems vs. DBMSs F Advantages and Disadvatages of DBMS F Components of DBMS F MS Access 2000 (Lab) Y. T.

“DOK 322 DBMS” DBMS Benefits Minimal Data Redundancy Consistency of Data Integration of Data Sharing of Data Ease of Application Development Uniform Security, Privacy, and Integrity Controls F Data Accessibility and Responsiveness F Data Independence F Reduced Program Maintenance F F F Y. T.

“DOK 322 DBMS” Database Environment Y. T. CASE Tools User Interface Repository DBMS Application Programs Database

“DOK 322 DBMS” Database Components DBMS ======== Design tools Database contains: User’s Data Metadata Indexes Application Metadata Y. T. Table Creation Form Creation Query Creation Report Creation Procedural language compiler (4 GL) ======= Run time Form processor Query processor Report Writer Language Run time Application Programs User Interface Applications Kroenke, Database Processing

“DOK 322 DBMS” Terms and Concepts F Database: – A self-describing collection of integrated records (Kroenke). – A collection of similar records with relationships between the records. (Rowley) – A collection of stored operational data used by the application systems of some particular enterprise. (C. J. Date) Y. T.

“DOK 322 DBMS” Terms and Concepts F Enterprise – Organization F Entity – Person, Place, Thing, Event, Concept. . . F Attributes – Data elements (facts) about some entity – Also sometimes called fields or items or domains F Data values – instances of a particular attribute for a particular entity Y. T.

“DOK 322 DBMS” Terms and Concepts F Key – an attribute or set of attributes used to identify or locate records in a file F Primary Key – an attribute or set of attributes that uniquely identifies each record in a file Y. T.

“DOK 322 DBMS” Terms and Concepts F Models – (1) Levels or views of the Database u Conceptual, logical, physical – (2) DBMS types u Relational, Hierarchic, Network, Object. Oriented, Object-Relational Y. T.

“DOK 322 DBMS” Models (1) Application 1 External Model Application 2 Application 3 Application 4 External Model Application 1 Conceptual requirements Application 2 Conceptual requirements Application 3 Conceptual requirements Application 4 Conceptual requirements Y. T. Conceptual Model Logical Model Internal Model

“DOK 322 DBMS” Database System Life Cycle Physical Creation 2 Conversion 3 Design 1 Growth, Change, & Maintenance 6 Integration 4 Operations 5 Y. T.

“DOK 322 DBMS” Another View of the Life Cycle Integration 4 Operations 5 Design Physical 1 Creation Conversion Growth, 2 Change 3 6 Y. T.

“DOK 322 DBMS” Database Models F Models(2): DBMS types – Hierarchical – Network – Relational – Object-Oriented Y. T.

“DOK 322 DBMS” Database Data Models F Hierarchical Model – Similar to data structures in programming languages. Books (id, title) Authors (first, last) Y. T. Publisher Subjects

“DOK 322 DBMS” Database Data Models F Network Model – Provides for single entries of data and navigational “links” through chains of data. Authors Subjects Books Publishers Y. T.

“DOK 322 DBMS” Database Data Models F Relational Model – Provides a conceptually simple model for data as relations (typically considered “tables”) with all data visible. Y. T.

“DOK 322 DBMS” Database Data Models F Object Oriented Data Model – Encapsulates data and operations as “Objects” Books (id, title) Authors (first, last) Y. T. Publisher Subjects

“DOK 322 DBMS” Database Design Process Application 1 External Model Application 2 Application 3 Application 4 External Model Application 1 Conceptual requirements Application 2 Conceptual requirements Application 3 Conceptual requirements Application 4 Conceptual requirements Y. T. Conceptual Model Logical Model Internal Model

“DOK 322 DBMS” Database Design Process F Conceptual Requirements – Systems Analysis Process Examine all of the information sources used in existing applications u Identify the characteristics of each data element u – – numeric text date/time etc. Examine the tasks carried out using the information u Examine results or reports created using the information u Y. T.

“DOK 322 DBMS” Database Design Process F Conceptual Model – Merge the collective needs of all applications – Determine what Entities are being used u Some object about which information is to maintained – What are the Attributes of those entities? Properties or characteristics of the entity u What attributes uniquely identify the entity u – What are the Relationships between entities u Y. T. How the entities interact with each other?

“DOK 322 DBMS” Database Design Process F Logical Model – How is each entity and relationship represented in the Data Model of the DBMS u Hierarchic? u Network? u Relational? u Object-Oriented? Y. T.

“DOK 322 DBMS” Database Design Process F Internal Model – Choices of index file structure – Choices of data storage formats – Choices of disk layout Y. T.

“DOK 322 DBMS” Database Design Process F External Model – User views of the integrated database – Making the old (or updated) applications work with the new database design Y. T.

“DOK 322 DBMS” Developing a Conceptual Model Overall view of the database that integrates all the needed information discovered during the requirements analysis. F Elements of the Conceptual Model are represented by diagrams, Entity-Relationship or ER Diagrams, that show the meanings and relationships of those elements independent of any particular database systems or implementation details. F Y. T.