IS 2079 Database Management Systems II
I. Introduction
A. Course Requirements
- 1. DBMS I or experience
- 2. Programming Ability
- 3. VAX VMS/UNIX/PC Familiarity
- 4. Text Book
Toery, Database Modeling and Design.
- 5. Projects:
- a. Design and Implementation of a Data Dictionary System
- b. Design and implementation of a DBMS for LAN Components
- c. Presentation of a DBMS Topic such as
concurrency, security, recovery, backup, etc.
- 6. Reserve the right to give a Midterm and Final test
if reading of the textbook is not being done.
- 7. Class participation
B. Grades and grading
- Simple DBMS Design: 20%
- SLIS Database Design: 20%
- Data Dictionary: 20%
- DBMS Design: 20%
- Class Presentation: 05%
- Class Participation: 05%
Each project will be graded based upon a 100 point system. The grade
distribution will be as follows:
- 93 - 100: A- to A+
- 85 - 92: B- to B+
- 77 - 84: C- to C+
- 69 - 76: D- to D+
- 0 - 68: F
If it is necessary to give a midterm and a final they
will be graded on a straight percentage basis using the scale provided above.
II. A Review of DBMS Concepts
- A. Database environments
- B. Terms and concepts
- C. A little History
- D. Analysts, designers, programmers, systems, operators, end-users
- E. DBMS concerns
- User View Representation
- Controlling redundancy
- Sharing Data
- Data Integrity
- Controlling access
- Backup and recovery
- Enforcing Standards
- F. Schemas and Instances
- G. DBMS Components
- H. DBA and Data directory/dictionary/respository
- I. Physical System Concepts and Implementation Issues
III. Data Models and data modelling
- A. Enity-Relationship Models
- B. Entities, attributes, classes and subclasses
- C. Keys and uniqueness and integrity
- D. Sets
- E. Relationship types
- F. E-R Diagrams
- G. Degree of relationships
- H. Hierarchical Data Model
- I. Network Data Model
- J. Relational Data Model
- K. Object Oriented Data Model
- L. Comparisons
IV. The Database Design Process
- A. Life Cycle of Information System
- B. DB design Phases
- C. Database Analysis and Requirements Definition
- D. Conceptual, logical and physical design factors
- E. Statistics and performance models
- F. Implementation and evaluation of DB designs
V. Data Modeling and Conceptual Design
- A. Entity Formulation and Analysis
- B. Attribute Sysnthesis
- C. Object Oriented Analysis and Design
VI. DBA and Data Dictionary/Directory/Respository
- A. Role and Function
- B. Design Issues
VII. Logical Design
- A. Transforming a Data Model to a DBMS
- B. Normalization
- C. Fine Tuning the logical design
- D. ER model to SQL
VIII. Physical Design
- A. Hardware Issues
- B. Access Methods
- C. Performance Calculations
- D. Usage Refinements
IX. Distributed DB Design
- A. Global Schema and Fragmentation Design
- B. Redundant Data Allocation Methods
X. Other design and operational factors
- A. Codes and Coding
- B. Access optimization
- C. Query optimization
- D. Concurrency and lock management
- E. Recovery
- F. Security and Integrity
- G. Object Oriented Databases
XI. Class Presentations
Groups of no more than 4 students will make a presentation on a critical and current
topic on database management systems such as security, distributed databases, object
oriented databases, concurrency, query optimization, etc.
XII. Project Overview
A. Simple Database Design
This project will be used as a warmup for more complicated design [projects but will
highlight the issues involved in the design and implementation process. The specific
project is to design a database that will provide information on physical facilities owned or
leased by the University of Pittsburgh. Ideally this database would be available over
Pittnet by all authorized users. It will contain image data, textual descriptions as well as
traditional fixed field data. The specific data elements will be developed in class.
B. Data Dictionary Project
This project is a design and implementation project. A data dictionary system must
be designed and implemented as a database in its own right. The Data dictionary must be
capable of storing information about the DB files as well as the design decisions and
operational aspects of a Database system.
C. SLIS Database Design Project
You will be given design documents from a previous analysis and will use these
specifications to build a database design. This will not require an implementation simply a
documentation of the design using E-R diagrams and Normalization.
D. DBMS Design Project
This will require E-R diagrams, normalization procedures and implementation of a
network distributed database using one or more of the design techniques discusedin the
text and class. Requirements and data sources will be provided in class.