Rutgers catalogResearched guideSIRS history36 section records

01:198:336

Principles Of Information And Data Management

COMPUTER SCIENCE

School 01 — New Brunswick School of Arts and Sciences
credits
4
Core
None listed
Typical seasons
Fall, Spring, Summer
Fall 2026 sections
7
Open snapshot
5 open in snapshot

Course guide

AI-generated overview

Course fingerprint 10 AI-generated signals

Difficulty

3/5
Why

Officially CS336 covers a broad set of database and information-management topics, while public student discussion usually describes it as manageable rather than trivial.

Workload

3/5
Why

The Rutgers materials show homework, exams, and a project, but student discussion generally frames the total workload as moderate unless the end-of-term project piles up.

Pacing

3/5
Why

The official topic list spans SQL, XML, transactions, inference, mining, and integration, so the course moves steadily without the same compression signal seen in systems-heavy classes.

Projects

4/5
Why

Both the historical Rutgers course page and public student threads point to a meaningful project that makes the class feel more real than a query-only survey.

Exams

3/5
Why

The Rutgers-hosted historical page assigns a midterm and cumulative final a majority share of the grade, but project and homework work also clearly matter.

Math

2/5
Why

The official focus is on modeling, SQL, transactions, and information systems rather than on sustained formal math or proof work.

Memorization

2/5
Why

Students seem to benefit more from understanding schema design, joins, and application structure than from rote recall alone.

Abstraction

3/5
Why

The class mixes concrete SQL and project work with more conceptual topics such as schema design, inference, and transaction services.

Prerequisites

3/5
Why

Students can usually enter without extreme theory preparation, but staying organized in querying and project integration still depends on solid general CS habits.

Reading

3/5
Why

The official materials point to a substantial topic spread and textbook-backed course structure, so there is likely a moderate reading and notes burden even if the class is not reading-dominant.

What students tend to say

Public r/rutgers discussion usually describes CS336 as more manageable than Rutgers's low-level systems courses, but still easier to underestimate than the title suggests because attendance, participation, and the final group project can matter a lot.

Students usually describe SQL as the center of the class

When students answer workload questions, they often point first to SQL as the language they remember using most clearly, even if projects involve extra tooling or web-facing pieces.

The project is where the course feels most real

Public discussion repeatedly mentions a larger project as the most complicated part of the class, especially because it pushes the material beyond short isolated query exercises.

Attendance and participation can affect the experience

Recent threads suggest that some offerings use participation exercises or recitation expectations enough that simply showing up steadily makes the course feel much lighter.

The class is often seen as manageable, not trivial

Students frequently call CS336 doable, but the more useful reading is that it feels approachable when you stay current on queries and project work, not that the content is disposable.

Topic breakdown

A practical chapter-by-chapter view from foundations to applications.

6 modules

Module 1

Why information management exists

CS336 starts with the basic question a database course is trying to answer: why not just keep data in ordinary files and ad hoc code? Rutgers materials frame the answer around scale, data independence, integrity, security, and the need to query information in ways that remain useful as systems grow.

database management systemsdata independenceintegritysecurityrecoveryinformation value

Basic concept overview

Data shape determines what questions are easy

CS336 teaches that schema design is not paperwork; it changes whether later querying, reporting, and application code stay clean or become awkward and error-prone.

A DBMS is valuable because it handles tedious guarantees

Integrity, security, efficient access, concurrent use, and recovery are all services that become painful to reinvent manually once data matters to more than one user or script.

SQL is a way of thinking, not just a syntax list

Students do better when they read a query as a transformation of sets and relationships instead of a string of clauses memorized in order.

Information management is broader than classic tables

The course deliberately widens from relational databases into web, XML, text, inference, mining, and integration topics so students can see how many forms useful information can take.

Things to watch for

Writing SQL before clarifying the relationship structure

Identify keys, join paths, and the grain of each table before you try to compose the final query.

Treating normalization and schema design as busywork

Use modeling rules as a way to prevent duplicated facts, inconsistent updates, and ambiguous queries later.

Thinking transaction topics are only for database implementers

Remember that even user-facing applications depend on atomicity, consistency, and failure recovery to keep data trustworthy.

Underestimating the final project until the integration step

Prototype the database, sample queries, and interface assumptions early so the project does not become a last-minute pileup of unrelated moving parts.

Fall 2026 sections

5 open · Busch

SectionStatusInstructorMeetingCampus
0111584OpenGale, AbrahamMonday 5:40 PM-7:00 PM at HLL 114; Wednesday 5:40 PM-7:00 PM at HLL 114; Tuesday 9:35 PM-10:30 PM at SEC 202HLL 114SEC 202Busch
0211585ClosedGale, AbrahamMonday 5:40 PM-7:00 PM at HLL 114; Wednesday 5:40 PM-7:00 PM at HLL 114; Tuesday 7:45 PM-8:40 PM at SEC 203HLL 114SEC 203Busch
0311586ClosedGale, AbrahamMonday 5:40 PM-7:00 PM at HLL 114; Wednesday 5:40 PM-7:00 PM at HLL 114; Tuesday 5:55 PM-6:50 PM at SEC 203HLL 114SEC 203Busch
0411587OpenGale, AbrahamMonday 5:40 PM-7:00 PM at HLL 114; Wednesday 5:40 PM-7:00 PM at HLL 114; Tuesday 12:25 PM-1:20 PM at SEC 205HLL 114SEC 205Busch
0711589OpenGale, AbrahamMonday 9:20 PM-10:40 PM at ARC 103; Wednesday 9:20 PM-10:40 PM at ARC 103; Tuesday 9:35 PM-10:30 PM at SEC 203ARC 103SEC 203Busch
0811590OpenGale, AbrahamMonday 9:20 PM-10:40 PM at ARC 103; Wednesday 9:20 PM-10:40 PM at ARC 103; Friday 5:55 PM-6:50 PM at ARC 105ARC 103ARC 105Busch
0911591OpenGale, AbrahamMonday 9:20 PM-10:40 PM at ARC 103; Wednesday 9:20 PM-10:40 PM at ARC 103; Friday 2:15 PM-3:10 PM at SEC 207ARC 103SEC 207Busch
cachedSource: Checked-in Rutgers Schedule of Classes snapshotsUpdated when term datasets are refreshedMay be stale

SIRS teaching signals

Historical student surveys

Teaching

3.82

Course quality

3.79

Response rate

30.0%

Coverage

48 offerings · 2016–2025

InstructorOfferingsTeachingQuality
Miranda Garcia, Antonio213.813.77
Imielinski54.224.24
Imielinski T34.103.97
Gale, Abraham33.333.43
Kalokyri Varvara Valia24.554.60
Miranda A23.903.85

Course stats

Catalog and planning context

Credits

4

Current campuses

Busch

Current availability

5 open of 7

Catalog terms

Fall, Spring, Summer

Core codes

None listed

Loaded terms

5

Prerequisites

(01:198:205 and 01:198:112 and 01:640:152 and 01:640:152) <em> OR </em> (01:198:205 and 01:198:112 and 01:640:192 and 01:640:192) <em> OR </em> (14:332:312 and 01:198:112 and 01:640:152 and 01:640:152) <em> OR </em> (14:332:312 and 14:332:351 and 01:640:152 and 01:640:152) <em> OR </em> (01:198:205 and 14:332:351 and 01:640:152 and 01:640:152) <em> OR </em> (01:198:205 and 14:332:351 and 01:640:192 and 01:640:192)

Degree requirement lists

No direct degree-list membership appears in the checked-in requirement index.

Loading grade outcomes…

Related COMPUTER SCIENCE courses