INFO90002 Database Systems and Data Modelling
The Complete Exam Bible · S2 2026INFO90002 Overview
- The University of Melbourne
- Semester 2, 2026
- 12 subject-derived chapters
- 33 paid study pages
INFO90002 Database Systems and Data Modelling is organised here from the current Semester 2, 2026 evidence rather than from a fixed house chapter count.
- Core method move from user requirements to a constrained data model, implement it in SQL and test integrity, concurrency and security consequences
- Evidence boundary the current Semester 2 administration source publishes 20/10/15/5/50 and two hurdles; proprietary retrieval is rich for administration and week one but thin later, so later teaching is explicitly standard database canon aligned to the published schedule
- Architecture Higher-load chapters receive a third teaching page; the remainder use two
- Live control Confirm current dates and operational instructions in the institutional learning system
What INFO90002 covers
The 12-chapter map follows the subject-supported sequence and varies chapter length with conceptual and evidence-control load.
Assessment, Evidence and Database Lifecycle
20/10/15/5/50 structure · database lifecycle · two-hurdle control · map requirements, design, implementation and validation to the assessed workflow02Requirements and Conceptual Modelling
business rules · entities and attributes · relationships · translate stakeholder language into testable data requirements03ER Diagrams and Cardinality
keys and identifiers · cardinality and participation · associative entities · justify every relationship constraint with a business rule04Logical Design and Normalisation
functional dependency · normal forms · lossless decomposition · remove update anomalies while preserving meaning and joinability05Relational Algebra and SQL Foundations
selection and projection · joins · set and bag behaviour · predict a query result from relational operations before running SQL06SQL DDL, DML and Integrity
table definition · constraints · insert update delete · encode business rules at the strongest appropriate database boundary07SQL Aggregation, Subqueries and Views
grouping and HAVING · nested query · view abstraction · choose a query shape that preserves the intended row and group grain08Transactions, Concurrency and Recovery
ACID properties · locking and isolation · logging and recovery · trace an interleaving to the anomaly and isolation control09Architecture, Administration and Distribution
three-tier architecture · catalogue and administration · distributed data · place responsibility across client, service and database layers10Data Warehousing and Analytical Models
operational versus analytical data · fact and dimension · ETL and lineage · design an analytical grain and preserve the transformation trail11NoSQL, JSON and Semi-Structured Data
document model · schema flexibility · consistency trade-off · select a data model from access pattern, integrity and evolution needs12Security, Backup and Integrated Exam Reasoning
least privilege · backup and restore · integrated design trade-off · combine modelling, SQL and operational controls in one defensible database decisionThe resulting 12-chapter map follows the subject-supported progression: Assessment, Evidence and Database Lifecycle, Requirements and Conceptual Modelling, ER Diagrams and Cardinality, Logical Design and Normalisation, then Relational Algebra and SQL Foundations, SQL DDL, DML and Integrity, SQL Aggregation, Subqueries and Views, and finally Transactions, Concurrency and Recovery, Architecture, Administration and Distribution, Data Warehousing and Analytical Models, NoSQL, JSON and Semi-Structured Data, Security, Backup and Integrated Exam Reasoning.
Each chapter is a teaching unit with a concept map, worked application, evidence control and transfer practice.
The guide uses one recurring intellectual method: move from user requirements to a constrained data model, implement it in SQL and test integrity, concurrency and security consequences. That method prevents two common forms of weak study.
The first is term collecting, where a student can reproduce definitions but cannot decide which one changes the case.
The second is answer collecting, where a familiar model is memorised without preserving the assumptions, evidence and boundary that made it defensible.
The published assessment architecture is Assignment 1: Data Modelling 20%, Assignment 2: SQL 10%, Quiz 1 15%, Quiz 2 5%, End-of-Semester Examination 50%, Coursework Hurdle 25/50 minimum, Examination Hurdle 25/50 minimum.
These values are kept in one source-controlled table and sum only the numeric weighted components. Mandatory or hurdle requirements are shown separately because adding them to the percentages would misrepresent the subject. Dates, submission settings and operational details not present in the retrieved source are left as boundaries and must be checked in the live learning system.
Source discipline is part of the product.
the current Semester 2 administration source publishes 20/10/15/5/50 and two hurdles; proprietary retrieval is rich for administration and week one but thin later, so later teaching is explicitly standard database canon aligned to the published schedule.
University-derived pages establish subject facts; independently authored explanations teach the reasoning; and original practice is labelled so it cannot be mistaken for an official question, solution or rubric. A retrieved source being silent about a rule is recorded as silence, not converted into a reassuring negative.
The paid study pages are deliberately varied in length and visual structure.
Chapters with a larger boundary-control burden receive a third page, while the others use two dense pages. Figures rotate through process, matrix, target, layers, cycle, bridge, spectrum, tree, funnel, radar, comparison and timeline structures. The visual is useful only when its labels expose a relationship the prose then explains.
Use the free layer as a diagnostic map.
Read the chapter overview, reconstruct the three linked concepts and attempt the four-point practice drill without notes. If the mechanism cannot be stated in plain language, return to the source-supported definition. If the conclusion feels obvious, deliberately create a counter-case.
This approach turns review into retrieval and transfer rather than passive rereading.
For written work, start from the instruction verb and evidence boundary. Give every paragraph one job: define, explain, apply, compare, evaluate or recommend. For a calculation or coded procedure, keep inputs, assumptions, transformations and interpretation visible.
For a case or policy task, name the affected stakeholder and the decision. For an oral response, preserve the same chain but make the transitions explicit.
The final control is accuracy under pressure. Before submitting or sitting a secure task, compare the current learning-system instructions with the assessment ledger, verify the task identity, and remove any claim whose source or mechanism cannot be named.
The guide supports subject reasoning; it does not replace live institutional instructions, professional advice or the student’s own assessed work.
How INFO90002 is assessed
| Component | Weight | Format |
|---|---|---|
| Assignment 1: Data Modelling | 20% | Group assignment |
| Assignment 2: SQL | 10% | Individual assignment |
| Quiz 1 | 15% | Individual timed closed-book quiz in the retrieved notice |
| Quiz 2 | 5% | Individual timed open-book quiz in the retrieved notice |
| End-of-Semester Examination | 50% | Two-hour on-campus examination in the retrieved notice |
| Coursework Hurdle · hurdle | 25/50 minimum | Combined A1, A2, Quiz 1 and Quiz 2 |
| Examination Hurdle · hurdle | 25/50 minimum | End-of-semester examination |
The five components total 100%. Hurdle 1 requires at least 25 marks from the 50-mark coursework group (A1, A2 and both quizzes); Hurdle 2 requires at least 25 marks from the 50-mark exam. Later canonical explanations are not presented as University questions or unpublished task content.
AskSia-authored integrated reasoning drill
- 1Identify the decision and source boundary.
- 1Select and define the relevant concept.
- 1Explain the mechanism with evidence.
- 1State a qualified action and review signal.
Key terms
- Source boundary
- The line between a published fact, scenario evidence and the guide's inference.
- Mechanism
- The process that explains how a condition produces or changes an outcome.
- Transfer
- Applying a concept accurately when the actor, setting, evidence or constraint changes.
INFO90002 FAQ
Is this an official University guide?
No. It is an independent study resource grounded in university-derived materials.
Are practice prompts official?
No. Every practice prompt and model response is independently authored.
Where should dates and submission settings be checked?
Use the current institutional learning system and official timetable.
Why are chapter lengths different?
The material and evidence-control burden determine whether a chapter needs two or three pages.
How to study for the exam
Retrieve the subject map, practise the recurring method—move from user requirements to a constrained data model, implement it in SQL and test integrity, concurrency and security consequences—on changed scenarios, and verify every operational assessment detail in the live institutional system.
Your AI Information Technology tutor for INFO90002
Stuck on a hard INFO90002 question? Sia is AskSia’s AI Information Technology tutor — ask any INFO90002 Database Systems and Data Modelling 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.
