Skip to syllabus
  • Fall 2026
  • Graduate
  • 3 credit hours
  • Online · Synchronous
  • Tue / Thu · 5:05–6:20 pm ET

INSC 584

Database Management Systems

A graduate introduction to how organizations store, model, and retrieve data — from entity-relationship design and SQL to a working prototype you build yourself.

A note from your instructor

Welcome to INSC 584

Humans generate a staggering amount of data every day. From medical records to course enrollments, new data arrives faster than ever. How is it stored? In many cases, the answer is a database.

Databases sit at the center of modern infrastructure. They keep data intact and make it available when we need it. This course covers the principles behind those systems, then asks you to apply them in a project that looks like work you might do after the degree.

We meet live on Zoom. Email me when something is unclear. I reply within 24 hours on weekdays and 48 hours on weekends, and I will tell you if I will be away. Write to jiangen@utk.edu.

At a glance

Course information

Class meetings

Fall 2026 · 3 credit hours · graduate standing required

Days
Tuesday and Thursday
Time
5:05–6:20 pm Eastern
Place
Zoom · link in Canvas
Recordings
Posted after class if you have to miss a session
Mode
Online, synchronous on Zoom · Tuesday and Thursday, 5:05–6:20 pm ET
SIS office
444 Communications Bldg.
865.974.2148
Required text
Hoffer, Venkataraman, and Topi, Modern Database Management, 13th ed. Pearson, 2019. ISBN 978-0134773650.
Office hours
By appointment · tiny.utk.edu/heoffice584

Catalog description

Defining data needs, data structures, the role of operating systems in data management, file organization, database management systems, logical data models, internal data models, database administration, and evaluation. Design and implementation of applications using database management systems. Graduate standing required.

How the course runs

Lectures, in-class exercises, and discussion happen live on Zoom. Slides go up in Canvas after class. You will complete a database design and prototyping project that stands in for a real-world scenario. The project can demonstrate MSIS program outcomes 6, 7, 8, and 9.

By the end of the term

Student learning outcomes

After this course you should be able to do the following.

Organizational data

Explain information needs in organizations and the environment in which databases operate.

Development process

Describe the database development process and the technology that supports it.

Language of the field

Use database terminology precisely enough to work with developers, analysts, and clients.

Conceptual design

Design data models with entity-relationship diagrams.

Logical design

Map ER diagrams onto relational models and normalize the result.

Physical design

Implement a prototype application in a relational DBMS.

SQL

Retrieve and modify data with Structured Query Language.

Operations

Identify issues that matter once a database is in production.

Week by week

Course schedule

Dates can shift. Use Canvas for current readings, due dates, and Zoom links. Week dates below are Mondays.

Week 1 · Aug 17

Welcome and introduction

  • Chapter 1
  • Quiz 1 assigned
  • Course overview

Week 2 · Aug 24

Introduction and modeling data

  • Chapter 1
  • Quiz 1 — due Wed Aug 26
  • In-class: University System (group)

Week 3 · Aug 31

Modeling data

  • Chapter 2
  • Quiz 2 assigned
  • University System — due Wed Sep 2; discussion Thursday
  • Lab: database design begins

Week 4 · Sep 7

Relational model

  • Chapter 2
  • Quiz 2 — due Wed Sep 9
  • In-class: Hotel Reservation System (group)
  • Lab: database design

Week 5 · Sep 14

Enhanced E-R model

  • Chapters 3 and 4
  • Quiz 3 assigned
  • Hotel Reservation System — due Wed Sep 16; discussion Thursday
  • Database design lab — due Thu Sep 17

Week 6 · Sep 21

Normalization

  • Chapters 3 and 4
  • Quiz 3 — due Wed Sep 23
  • In-class: Library Management System (group)
  • Lab: database implementation begins

Week 7 · Sep 28

Introduction to SQL

  • Chapters 5 and 6
  • Quiz 4 assigned
  • Library Management System — due Wed Sep 30; discussion Thursday
  • Lab: database implementation

Week 8 · Oct 5

Fall break

  • No class Tuesday (fall break, Oct 5–6)
  • Chapters 5 and 6
  • Quiz 4 — due Wed Oct 7
  • In-class: Intro to SQL and Oracle (individual)

Week 9 · Oct 12

Advanced SQL

  • Chapters 7, 8, and 11 (selected sections)
  • Quiz 5 assigned
  • Intro to SQL and Oracle — due Wed Oct 14
  • Database implementation lab — due Tue Oct 27

Week 10 · Oct 19

Advanced SQL

  • Chapters 7, 8, and 11 (selected sections)
  • In-class: SQL (group)
  • Lab: database use begins

Week 11 · Oct 26

Physical database design

  • Chapters 7, 8, and 11 (selected sections)
  • Quiz 5 — due Wed Nov 4
  • SQL group exercise — due Wed Oct 28; discussion Thursday
  • Lab: database use

Week 12 · Nov 2

Big data and NoSQL

  • No class Tuesday
  • Database use lab — due Thu Nov 19

Week 13 · Nov 9

Final project and special topic

  • Project studio
  • Special topic as announced in Canvas

Week 14 · Nov 16

SQL exam

  • SQL exam — Wed Nov 18, due 8:00 pm ET, remotely proctored
  • Optional project proposal and design — due Wed Nov 18

Week 15 · Nov 23

Project presentations

  • No class Thursday (Thanksgiving, Nov 25–27)
  • Presentations as assigned

Week 16 · Nov 30

Project presentations

  • Last day of classes: Tuesday, Dec 1
  • No class Thursday
  • Presentations as assigned

Week 17 · Dec 7

Finals week

  • No class (finals, Dec 3–9)
  • Final project report — due Mon Dec 7, 11:59 pm ET

How you are evaluated

Assignments and grades

The course is worth 1,000 points. I mark individual work with comments and points, not letter grades. Your letter grade comes from total points at the end of the term.

30% In-class exercises 5 exercises · 300 points
25% Labs 3 labs · 250 points
20% Project Design and prototype · 200 points
10% Practice exercises Instant feedback · 100 points
10% SQL exam Nov 18 · 100 points
5% Participation Attendance and discussion · 50 points

In-class exercises · 300

Most database work is team work. About half of our meetings are studio sessions: one class to do the exercise, the next to present and discuss.

  • University System (group) · 65
  • Library Management System (group) · 65
  • Hotel Reservation System (group) · 70
  • Intro to SQL and Oracle (individual) · 35
  • SQL (group) · 65

Labs · 250

Hands-on practice with data structures and SQL. Advanced skill comes from exploring the software and fixing what breaks.

  • Lab 1 · Create data structure · 85
  • Lab 2 · Implementation and SQL · 90
  • Lab 3 · Advanced queries · 75

Project · 200

Work alone or in a group. Choose a real setting, run a needs analysis, draw a conceptual design, and build a prototype. The focus is the back end: structure, integrity, and queries. Scope should match the size of your group.

Late work

Unless we arrange otherwise in advance, late work loses 10% of the points for each day past the due date. If you will miss a deadline, write before it passes. When the situation warrants it, we will set a new date together.

Grading scale

Letter Points Performance
A 93–100 Superior performance (4.0 quality points)
A− 90–92.99 Intermediate superior performance (3.7)
B+ 88–89.99 Very good performance (3.3)
B 83–87.99 Good performance (3.0)
B− 80–82.99 Intermediate good performance (2.7)
C+ 78–79.99 Fair performance (2.3)
C 73–77.99 Satisfactory performance (2.0)
C− 70–72.99 Unsatisfactory performance (1.7)
D+ 68–69.99 Unsatisfactory performance (1.3)
D 63–67.99 Unsatisfactory performance (1.0)
D− 60–62.99 Unsatisfactory performance (0.7)
F 0–59.99 Failure (0.0)

Other marks

  • S — Satisfactory. Assigned only for C or better work on an S/NC basis. No quality points.
  • NC — No credit. Assigned for C− or worse work on an S/NC basis. No quality points.
  • I — Incomplete. Reserved for emergencies that prevent finishing the course on time, and only under unusual circumstances at the instructor’s discretion. If you disappear without contacting the instructor or completing the required form, an F is submitted. An I that is not removed within one calendar year, or upon graduation, becomes an F.
  • W — Official withdrawal from the course or the university. No quality points.

Expectations

Policies

Academic integrity

Know the Hilltopics Student Handbook and follow UT academic policy, including the Honor Statement and the Academic Integrity Policy.

“As a student of the University, I pledge that I will neither knowingly give nor receive any inappropriate assistance in academic work, thus affirming my own personal commitment to honor and integrity.”

Study, preparation, and presentation should be your own work unless a team effort is clearly specified. When you use other scholars’ work, cite the source. Infractions are penalized according to severity and may include a course grade of F.

Plagiarism

Plagiarism in any form is not tolerated. Claiming you did not understand the rules is not an excuse. Examples include:

  1. Copying written or spoken words without quotation marks and a citation.
  2. Summarizing another source’s ideas without a citation, unless the information is common knowledge.
  3. Borrowing facts, statistics, graphs, images, or phrases without acknowledgment, unless they are common knowledge.
  4. Collaborating on a graded assignment without the instructor’s approval.
  5. Submitting work created by a professional service, in whole or in part, without attribution.

If you are unsure, ask. The University Libraries maintain a citing sources guide.

Absence

Acceptable reasons include illness, serious family emergencies, special curricular or job requirements, military obligation, severe weather, religious holidays, official university activities, and court-imposed legal obligations. Others are at the instructor’s discretion. Tell me as soon as you can.

University of Tennessee, Knoxville

Campus syllabus

The campus syllabus collects policies and resources that apply to every UTK course. Please read them and use the support listed below. At UT we are committed to a high-quality learning experience.

— Dr. John Zomchick, Provost and Senior Vice Chancellor