The University of Sydney · S2 2026 · FACULTY OF INFORMATION TECHNOLOGY

ISYS2120 Data and Information Management

- one subject, every graph, every model, every mark
5 Chapters70-page Bible
Our own words - no uploaded lecturer files
Built to mirror S2 2026 · updated this semester
The Complete Exam Bible · S2 2026

ISYS2120 Overview

Data and Information Management
— Build database models and SQL queries from meaning, then verify every constraint, intermediate relation and result.
  • The University of Sydney
  • Semester 2 2026
  • Level 2
  • Closed book final exam

Data and Information Management develops the reasoning needed to represent organisational data and retrieve it reliably. The available University teaching material begins with the purpose of database management systems and the separation between user views, conceptual structure and physical storage.

  • Assessed by SQL tasks, quizzes, modelling and a final exam
  • Core method Model meaning before syntax
  • How to prepare Predict, test and explain each result
ISYS2120 · The University of Sydney
An independent, AskSia-authored study guide. AskSia is not affiliated with, endorsed by, or sponsored by The University of Sydney; the course code and name are used for identification only.
Assessment

How ISYS2120 is assessed

ComponentWeightFormat
Final Exam · hurdle50%Two-hour in-person handwritten paper in the formal examination period
weekly quizzes21%Secure online quizzes completed in tutorial classes
SQL tasks6%Online tasks that produce SQL queries for given output
Early feedback quiz3%Multiple-choice quiz completed in a tutorial class
Conceptual Model Assignment10%Group production of a conceptual model for a domain
SQL Online Quiz10%Fifty-minute task producing SQL queries for information needs

The six weighted assessment rows total 100%. The Final Exam is a hurdle task: the unit materials state that students must achieve at least 40% in the final examination and an overall final mark of 50 or more. The official unit outline also lists a zero-weight Exam practice assignment, which is not included in the numeric total.

Contents · every chapter, one map

What ISYS2120 covers

The available teaching sequence moves from database systems and relational structure into conceptual modelling, SQL querying and definition, schema mapping, relational algebra and advanced query patterns. Each module pairs formal vocabulary with fresh domains, counterexamples and result checks.

It then develops the relational model through relations, tuples, attributes, domains and keys. Conceptual modelling turns domain statements into entities, relationships, attributes, participation and cardinality constraints. SQL work connects information needs to selection, projection, joins, aggregation, nested queries and result testing.

Definition work uses types, primary keys, foreign keys and other constraints to reject invalid states. Relational algebra provides an independent way to expose query structure and reason about selection, projection, joins, set operators and division. The study method throughout this guide is consistent: model meaning before syntax, write assumptions, predict the smallest result, and test a counterexample.

Start every task by separating the domain fact from its representation. A customer, booking or workshop is not a table merely because it appears as a noun; identity and relationships determine the model. Likewise, an English request is not a query until its required inputs, predicates and output are explicit.

After drafting an answer, create a tiny dataset that includes an ordinary match, an unmatched row, a duplicate and a missing value where relevant. Predict the result by hand. This turns testing into evidence about meaning rather than a search for syntax that happens to run. For modelling questions, read cardinality and participation in both directions and state assumptions where the requirement is silent.

For definition questions, explain which invalid state each constraint rejects. For algebra and SQL, show intermediate relations so that an accidental product, misplaced filter or reversed universal condition becomes visible. The available material for this edition covers these foundations through conceptual modelling and advanced SQL.

Later areas named by the unit introduction are identified as a teaching-material gap and are not reconstructed from general database knowledge.

Worked example · free

Diagnose a query before running it

Q [4 marks]. A community tool library needs a report listing every depot and its number of open loans, including depots with none. Explain the join and grouping choices, and identify a test case that reveals an incorrect inner join. The four marks shown are an AskSia practice allocation, not a University mark scheme.
  • +1Start from every depot because all depots must remain visible.
  • +1Use a left join to matching open loans so unmatched depots survive with NULL on the loan side.
  • +1Group by the depot identifier and count a loan-side key, not every joined row.
  • +1Test one empty depot: it must appear with a count of zero.
Begin with Depot, left join open Loan rows on the depot key, group by the depot identifier and count a non-null Loan key. An inner join fails the diagnostic case because it removes a depot with no matching loan before grouping.
Sia tip — Put one depot with no loans in your test data. If it disappears, inspect the join before changing the count. The four marks are an AskSia practice allocation, not a University mark scheme.
Glossary

Key terms

Database management system
A database management system coordinates persistent data, metadata, queries, integrity, concurrency, recovery and controlled access.
Relation
A relation is a set of tuples described by a relation schema of named attributes and domains.
Candidate key
A candidate key is any attribute combination that can distinguish each tuple.
Foreign key
A foreign key is an attribute set whose values reference a candidate key in a target relation.
Entity type
An entity type groups distinguishable domain objects that share attributes and identity rules.
Cardinality constraint
A cardinality constraint limits how many relationship counterparts an entity may have.
Selection
Selection is the relational algebra operator that keeps tuples satisfying a predicate.
Projection
Projection is the relational algebra operator that retains named attributes.
FAQ

ISYS2120 FAQ

How is the unit assessed?

Assessment combines SQL tasks, tutorial quizzes, an early feedback quiz, a conceptual model group assignment, an SQL online quiz and a paper-based final examination. The weighted rows total 100%, and the final examination carries a stated hurdle.

What is the best way to learn SQL?

Translate each request into required inputs, predicates and output columns before typing. Predict a small result by hand, include duplicates and NULLs in test data, then compare intermediate rows rather than judging only the final table.

How should I practise conceptual modelling?

Use short domain statements and justify each entity, relationship, attribute, cardinality and participation choice. Test the diagram with a valid story and a counterexample, and write down any assumption the requirements do not settle.

Why learn relational algebra alongside SQL?

Relational algebra makes query structure explicit. Selection, projection, joins, set operators and division provide a second representation that helps reveal accidental products, incompatible inputs and universal conditions hidden inside SQL syntax.

What should I revise before the final examination?

Prioritise precise vocabulary, ER constraint reading, SQL result prediction, key and foreign-key behaviour, mapping decisions, relational operators and nested universal queries. Practise explaining assumptions and boundary tests without relying on software.

Study strategy

How to study for the exam

Study by alternating construction and refutation. Build a model or query from a small requirement, then attack it with an empty input, an unmatched row, a duplicate, a NULL or an invalid reference as appropriate. Keep a notebook of minimal counterexamples and the rule each one tests. For SQL, write the expected intermediate relation before execution. For ER diagrams, verbalise cardinality and participation in both directions.

For relational algebra, check operator inputs and headings. This routine prepares you for secure tutorial tasks as well as the closed-book final examination because it makes the reasoning portable instead of tying it to one familiar example. End each session by explaining one correction aloud in domain language and formal database language.

If those explanations disagree, revisit the assumption before practising another problem.

Study ISYS2120 with AI

Your AI Information Technology tutor for ISYS2120

Stuck on a hard ISYS2120 question? Sia is AskSia’s AI Information Technology tutor — ask any ISYS2120 Data and Information Management question and get a clear, step-by-step explanation grounded in how the course is actually taught and assessed. Read this whole study guide free, then take your hardest questions to Sia.

A+Everything unlocked
Unlocks this Bible + all 64 of your The University of Sydney subjects - and 1,000+ Bibles across every Australian university.
Sia - your ISYS2120 tutor, unlimited, worked the way the exam marks it
The full 70-page Bible + practice bank with worked solutions
Chrome extension - sync your LMS so Sia knows your deadlines
Bilingual EN / Chinese on every Bible and every Sia answer
$0.99 Trial
30-day money-back · cancel in one tap · how it works
Unlock the full ISYS2120 Bible + 64 The University of Sydney subjects
$0.99 Trial