DATABASE MANAGMENTSYSTEM

Course Syllabus

Prepared By:

GENERAL DATA

SUBJECT CODE

Credit Hours

PUBLICATION DATE

DEGREE IN WHICH IT IS
TAUGHT
CONTEXT OF THE SUBJECT

RESPONSIBLE TEACHER
Name

LIST OF TEACHERS
THEORY

PRACTICE WITH PC AND MENTORS

COMPETENCES AND LEARNING OUTCOMES

Upon successful completion of this course, students should be able to:

LEARNING OUTCOMES
1. Describe DBMS structure.
2. Demonstrate awareness of the importance of database management systems.
3. Demonstrate knowledge of business and functional requirement writing and spec’s.
 TECHNICAL COMPETENCES
1. Ability to carry out conceptual modelling using EER
2. Ability to carry out logical modelling using relational model
3. Ability to work with SQL to create data structures and to query them to solve
information needs.

TRANSVERSAL COMPETENCES T
1. Acquire abilities to creatively solve database-related problems based on an
autonomous decision-making.
2. Acquire abilities to communicate and transmit knowledge on database design
issues.
3. Acquire abilities to work effectively in groups to successfully design a database.

CONTENT

GENERAL DESCRIPTION
This course provides a solid background in the theory, design, and programming of database
systems, with a focus on relational databases. The relational data model and entity-
relationship diagrams will be covered. The course introduces database query languages,
including an in-depth coverage of the Structured Query Language (SQL). Other database
topics include storage and indexing techniques, transaction management, and database
interface with application programs. Prerequisite: ( ) This course is valuable to analysts,
engineers, designers and developers.
THEORETICAL CONTENT
Theoretical contents
1- Database concepts
a. Why Databases?
b. Data vs. Information
c. Introducing the Database
d. Why Database Design is Important
e. Evolution of File System Data Processing
f. Problems with File System Data Processing
g. Database Systems
a. Data Modeling and Data Models
b. The Importance of Data Models
c. Data Model Basic Building Blocks
d. Business Rules
e. The Evolution of Data Models
f. Degrees of Data Abstraction
g. A Logical View of Data
h. Keys
i. Integrity Rules
j. Relational Set Operators
k. The Data Dictionary and the System Catalog
l. Relationships within the Relational Database
m. Data Redundancy Revisited
n. Indexes
o. Codd’s Relational Database Rules
2. Entity Relationship (ER) Modeling
a. The Entity Relationship Model (ERM)
b. Developing an ER Diagram
c. Database Design Challenges: Conflicting Goals Advanced Data Modeling
d. The Extended Entity Relationship Model
e. Entity Clustering
 f. Entity Integrity: Selecting Primary Keys
g. Design Cases: Learning Flexible Database Design
h. Database Tables and Normalization
i. The Need for Normalization
j. The Normalization Process
k. Improving the Design
l. Surrogate Key Considerations
m. Higher-Level Normal Forms
n. Normalization and Database Design
o. Denormalization
p. Data-Modeling Checklist
3. Introduction to Structured Query Language (SQL)
a. Introduction to SQL
b. Data Definition Commands
c. Data Manipulation Commands
d. SELECT Queries
e. Additional Data Definition Commands
f. Additional SELECT Query Keywords
g. Virtual Tables: Creating a View
h. Joining Database Tables
i. Relational Set Operators
j. SQL Join Operators
k. Subqueries and Correlated Queries
l. SQL Functions
4. Advanced topics
a. Semi-structured models
i. XML
ii. Query in semi-structured models
b. NoSQL*
c. Object-relational database*
d. Data warehouse*
e. Spatial databases*

LEARNING PLAN

TEACHING METHODOLOGY FACE-TO-FACE SELF STUDY

ACTIVITY HOURS HOURS
Theory The teaching approaches 15 weeks per semester, Each student supposed
and methods of learning 45 hours in total. 3 per to spend 2 self-study
used on the course will week. The last week hoursfor each one-hour
include traditional lecturing. (No. 16) will be lecture. 6 hours per
Seminars, tutorials, general reserved to the final week.
and case studies discussion examinations.
will also be used.
Practice with Student teams will work on Each team supposed to Each studentsupposed
PC completing the development meet with the tutor to work practically on
of an authentic software from the private sector the assignments for
project to be provided from face-to-face at least two hours per week. In
the industry by the private one time for two hours addition of two hours
company partner. In per week. per week on their
addition, students will work projects.
on different practical
assignments to be applied on
the case studies given during
the course.
TOTAL 75 hours 150 hours

Weekly detail

*****(T)for theoretical, (P) for practical

 Face-to- Work
Due Self Lab.
WEEK TYPE UNIT text pages Face with
dates study Work
Hours Mentor
1-2 T Database concepts pp. 3-58 6 0 6 0
Company tutor will visit class to
introduce the project (project
2 P 0 1 0 0
orientation)

Database design: Entity relationship

3 T pp. 99-140 6 0 6 0
modeling (ER)
Company tutor will work with
students on ER diagram for the
4 P 0 2 0 0
project

5 T Relational database model pp. 58-92 3 0 3 0

6 P Advanced data modeling (EER) pp.147-168 3 0 3 0
During week 6 company tutor will
6 T work on DDL for project with 0 2 0 3
student teams.
pp. 174-
7 P Normalization of database tables 3 0 3 0
208
28-
8 T Midterm exam pp.3-208 1 0 0 0
10/2014
Student teams work with company
8 P 2 2 0 0
tutor on Normalization.
Assignment 1: Schema on open
9 T 1 0 6 0
data
pp.220-
9-10 P Database implementation 5 0 6 3
369
Problem-based sessions with
company tutor: Posing problems
11 T 3 2 0 3
related team SQL and working with
students teams on tuned queries.
Assignment 2: Converting
12 P 0 0 2 0
information need(s) to SQL
Advanced topics
 Semi-structured models
i. XML
ii. Query in semi-structured
12-13 T models pp515-566 6 0 0 0
 NoSQL* pp351-361
 Object-relational database*
 Data warehouse*
 Spatial databases*
Team project presentations and
defense. Company tutor and course
14-15 P teacher will assess project quality 6 6 0 0
and team performance according to
a pre-designed rubric.
16 T Final exam 2 0 0 0
Total hours 47 15 35 9

EVALUATION SYSTEM

Since this course is project- and industry-based, a significant portion of the course grade will go for the project tasks, and the
industry will be part of the evaluation process. The grade distribution is as follows:

1. First exam
2. Two problem based assignments
 Schema on open data
  Converting information need to SQL and lab. attendance

Rubric for problem assessment is attached.

3. Term project

Rubric for project assessment is attached.

4. Final Exam

Tools and Criteria for the evaluation

TYPE CRITERION DESCRIPTION WEIGHT

CONTINOUS Exam First written exam for one and a half hour. 20
EVAL. Given in the class room and covers all the
theoretical part of the course up to week
seven.
CONTINOUS Problem/team Practical assignment (No.1 ) given in the 10
EVAL. based sixth week. Students on a team-based
assignment asked to solve specific software
engineering problem on one of the case
studies discussed in the class. Rubric for
assessment is attached.
CONTINOUS Problem/team Practical assignment (No.2) given in the 10
EVAL. based eleventh week. Students on a team-based
assignment asked to solve specific software
engineering problem on one of the case
studies discussed in the class. Rubric for
assessment is attached.
CONTINOUS Term project Students will be divided into six teams with 30
EVAL. five students in each one. Each team will
work on completing the development of
an authentic software project to be
provided from the industry by the private
company partner. Rubric for assessment is
attached.
CONTINOUS Exam Final written exam for two hours. Given in 30
EVAL. the class room and covers all the
theoretical part of the course.
TOTAL 100

BIBLIOGRAPHYDatabase Systems: Design, Implementation, and Management

TITLE DATABASE SYSTEMS: DESIGN,

IMPLEMENTATION, AND MANAGMENT
(Main Text Book)
AUTHOR(s) Carlos Coronel, Steven Morris, and
Peter Rob
EDITION Ninth Edition
ISBN
RECOMMENDED BY -
Access to the resource