FIT9132 Introduction to Databases
The Complete Study & Assessment Guide · S2 2026FIT9132 Overview
- Monash Faculty of Information Technology
- Semester 2, 2026
- a postgraduate introductory database unit
- 6 credit points
- a gateway data-management unit
FIT9132 covers database purpose, conceptual and logical design, the relational model, normalisation, DDL, DML, transactions, SQL querying, NoSQL and ethical database use. It is taught within Monash Faculty of Information Technology. It is a postgraduate introductory database unit. It carries 6 credit points.
- Grain before tables State what one row represents before choosing columns or keys.
- Keys enforce identity A primary key is a business and integrity decision, not decorative syntax.
- Normalisation tests dependencies Split relations because of functional structure, then preserve joins and constraints.
- Queries need expected sets Verify duplicates, nulls and missing rows, not only SQL syntax.
How FIT9132 is assessed
| Component | Weight | Format |
|---|---|---|
| Class Test 1 | 15% | Database design test; current Allocate+/Moodle controls scheduled sitting |
| Assignment 1 - Database Design | 35% | Includes applied tasks and a 30% design submission due 16 September 2026 |
| Class Test 2 | 15% | SQL queries and transactions; current Allocate+/Moodle controls scheduled sitting |
| Assignment 2 - Creating, Populating and Manipulating Databases | 35% | Includes applied tasks and a 30% submission due 2 November 2026 |
S2 2026 consists of Class Test 1 15%, Assignment 1 Database Design 35%, Class Test 2 15%, and Assignment 2 Creating, Populating and Manipulating Databases 35%. The current Handbook publishes no course-specific hurdle or final examination.
Current FIT9132 dates
| Date | Item | Control |
|---|---|---|
| 16 September 2026 at 11:55 pm | Assignment 1 Database Design submission | 30% core submission inside the 35% stream. |
| 2 November 2026 at 11:55 pm | Assignment 2 database implementation submission | 30% core submission inside the 35% stream. |
Current-offering dates captured in the course materials. Confirm changes and exact submission settings in the live LMS.
What FIT9132 covers
Start with Database Systems, Data Grain and Integrity; use Logical Design and Mapping as the turning point; finish by bringing the course together in NoSQL, Big Data and Ethical Database Use.
Database Systems, Data Grain and Integrity
database management system · data grain · integrity constraint · define the data object, users and integrity rules before design02Entity-Relationship Modelling
entity type · relationship · identifier · translate narrative rules into entities, identifiers, cardinalities and participation03Relational Model, Keys and Constraints
relation · candidate key · foreign key · map a conceptual design into relations with enforceable identity and references04Functional Dependencies and Normalisation
functional dependency · normal form · lossless decomposition · use dependencies to remove anomalies while retaining correct reconstruction05Logical Design and Mapping
associative relation · weak entity · schema mapping · map complex ER structures without losing cardinality or existence rules06DDL, DML and Transaction Control
data definition language · data manipulation language · transaction · implement schema constraints and multi-step changes that succeed or fail together07SQL Querying and Aggregation
join · aggregation · null · write queries whose joins, filters, groups and null handling match the user question08NoSQL, Big Data and Ethical Database Use
non-relational model · schema flexibility · data ethics · compare relational and NoSQL designs while controlling governance effectsIt is positioned as a gateway data-management unit.
Assessment deliberately pairs design and implementation: a correct query cannot rescue a model that failed to represent business rules and integrity.
Assessment in fit9132 is distributed as follows: two 15% class tests and two 35% assignment streams covering database design and implementation
The operational assessment conditions matter here.
No final examination appears in the current S2 structure.
What makes fit9132 demanding is concrete: keeping business rules, keys, dependencies and SQL behaviour consistent across conceptual design, normalisation and implementation rather than treating them as separate exercises
Treat the fit9132 hurdle status as unconfirmed.
Check the current Monash Handbook and learning site for any component-level pass rule before relying on the overall mark.
For enrolment planning, Confirm current course-map and prohibition rules in the Handbook; the retrieved current unit record is authoritative.
Start with Database Systems, Data Grain and Integrity; use Logical Design and Mapping as the turning point; finish by bringing the course together in NoSQL, Big Data and Ethical Database Use.
Repair an order database
- 1Declare the row grain as one order line.
- 1Identify order, customer and product identifiers and dependencies.
- 1Separate customer, product, order and order-line relations.
- 1Place foreign keys and business constraints.
- 1Test reconstruction and a transaction that adds a new line.
Key terms
- database management system
- Software that defines, stores, queries, controls and recovers shared data. This chapter uses the concept when students define the data object, users and integrity rules before design.
- data grain
- The real-world meaning represented by one record or row. It helps explain the reasoning required to define the data object, users and integrity rules before design.
- integrity constraint
- Rule that prevents a database state inconsistent with the model. Its limit matters because a fast system can still be wrong when row meaning or business rules are ambiguous.
- entity type
- Category of distinguishable things about which data is stored. This chapter uses the concept when students translate narrative rules into entities, identifiers, cardinalities and participation.
- relationship
- Association among entity instances with stated cardinality and participation. It helps explain the reasoning required to translate narrative rules into entities, identifiers, cardinalities and participation.
- identifier
- Attribute or attribute set that uniquely distinguishes an entity instance. Its limit matters because a diagram is only correct relative to explicit business rules and time scope.
- relation
- Set of tuples sharing the same named attributes under the relational model. This chapter uses the concept when students map a conceptual design into relations with enforceable identity and references.
- candidate key
- Minimal attribute set that uniquely identifies every tuple in a relation. It helps explain the reasoning required to map a conceptual design into relations with enforceable identity and references.
- foreign key
- Attribute set constrained to match a candidate key in a referenced relation or be null when allowed. Its limit matters because surrogate keys do not remove the need to protect real business uniqueness.
- functional dependency
- Constraint where one attribute set determines another in every valid relation state. This chapter uses the concept when students use dependencies to remove anomalies while retaining correct reconstruction.
- normal form
- Structural condition limiting redundancy and update anomalies according to dependencies. It helps explain the reasoning required to use dependencies to remove anomalies while retaining correct reconstruction.
FIT9132 FAQ
How is fit9132 assessed?
two 15% class tests and two 35% assignment streams covering database design and implementation
What is the fit9132 final assessed-task format?
No final examination appears in the current S2 structure.
Which offering does this fit9132 guide cover?
It is aligned to Semester 2, 2026; confirm your enrolled class and timetable in the current institutional system.
Does fit9132 have a hurdle or component-level pass rule?
Treat the fit9132 hurdle status as unconfirmed. Check the current Monash Handbook and learning site for any component-level pass rule before relying on the overall mark.
Is this fit9132 resource an official university guide?
No. It is an independent fit9132 study resource; current institutional instructions remain authoritative for assessment operation.
How should database management system be used in FIT9132?
Software that defines, stores, queries, controls and recovers shared data. This chapter uses the concept when students define the data object, users and integrity rules before design. Use it to define the data object, users and integrity rules before design; remember that a fast system can still be wrong when row meaning or business rules are ambiguous.
How to prepare for the assessments
Retrieve the course map, practise the recurring method—translate business rules into entities, relationships and identifiers, map them to relations, test dependencies and normal forms, implement constraints and transactions in SQL, then verify query results and relational versus non-relational fit—on changed scenarios, and verify every operational assessment detail in the live institutional system.
Your AI Information Technology tutor for FIT9132
Stuck on a hard FIT9132 question? Sia is AskSia’s AI Information Technology tutor — ask any FIT9132 Introduction to Databases 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.
