UMGC CMIS 320: Relational Database Concepts
CMIS 320 covers relational database theory and practice: the relational model, entity-relationship modeling, normalization, and SQL. Projects walk you from a business scenario to a normalized design to an implemented, queried database, the full design-to-SQL arc in one 8-week session.
Fennie is independent and not affiliated with University of Maryland Global Campus. This is an unofficial study guide.
What makes it hard
Normalization is the consistent sticking point: the normal-form definitions read simply but applying them to a messy scenario takes practice the readings alone don't provide. SQL joins are the second hump, and the projects require both skills working together under session pacing.
What you'll cover
- • The relational model
- • Entity-relationship modeling
- • Normalization (1NF through 3NF)
- • SQL: queries, joins, and DDL
- • Keys and integrity constraints
- • Database design projects
The CMIS 320 study guide
How to study for UMGC CMIS 320, step by step.
- 1
Practice normalization on messy tables, not definitions
Take a deliberately bad table and walk it to 3NF, naming the violation at each step. That exercise, repeated, is the difference between recognizing the normal forms and being able to apply them on the project.
- 2
Sketch the ER diagram before any SQL
The projects reward designs that flow from the scenario's requirements. List the entities and rules first; the tables, keys, and relationships fall out of that analysis.
- 3
Run SQL hands-on from week 1
Reading queries doesn't build the skill; writing them against a real database does. Set up your environment early and write more queries than assigned, especially joins.
- 4
Draw the tables before writing each join
Join syntax is memorizable; deciding which tables to join and on what column is the skill. Sketching the linked tables on paper first makes multi-table queries routine.
Today
Today's CMIS 320 plan
What a Fennie Daily Plan looks like for CMIS 320. Yours is built from your own syllabus and adapts every day to your deadlines and progress.
First plan free, no card required. Fennie is independent and unaffiliated with your school.
FAQ
Is UMGC CMIS 320 hard?
Moderately. The theory is approachable but normalization and joins both take deliberate practice. Students who work extra examples beyond the assignments find the projects straightforward; readers-only struggle.
Does CMIS 320 teach SQL?
Yes. It covers queries, joins, and table creation, alongside the design theory. The course's arc runs from a business scenario through a normalized design to an implemented database you query.
Do I need programming before CMIS 320?
Prior programming helps with the mindset but SQL is its own kind of language, declarative rather than step-by-step. Attention to detail and practice volume matter more than which languages you already know.
More UMGC courses
CMIS 102: Introduction to Problem Solving and Algorithm Design
CMIS 102 is UMGC's entry point to programming, teaching problem decomposition, algorithm design, and basic coding in Python. It's the prerequisite gateway for the computer science and software development paths, and weekly work centers on small programming exercises that build from sequential logic to functions and loops.
CMIS 111: Social Networking and Cybersecurity Best Practices
CMIS 111 is a hands-on survey of social networking platforms and personal cybersecurity: how to use professional and personal networks while protecting yourself from common attacks. It's a popular general-education technology elective with projects built around real accounts and security tools rather than exams.
CMSC 115: Introductory Programming
CMSC 115 is the first programming course in UMGC's computer science major, teaching Java fundamentals (variables, control flow, methods, and arrays) through hands-on projects with professional tools. It's the gateway to the CMSC sequence and moves at a brisker, more engineering-minded pace than the CMIS introductory track.
CMIS 242: Intermediate Programming
CMIS 242 is UMGC's object-oriented Java course: classes, inheritance, polymorphism, exceptions, generics, and graphical interfaces, assessed through weekly programming projects. It follows the introductory Java course and is where programs stop being scripts and start being designed.