CityUHK IS5413: Database Management Systems — course overview with AskSia
IS5413 Database Management Systems is a 3-credit-unit postgraduate course from the Department of Information Systems at City University of Hong Kong, offered in both Semester A and Semester B of 2026/27. It is a core course of the MSc Business and Data Analytics (Information Analytics Management stream) for the 2026/27 cohort and an elective in the department's other master's programmes.
Sia generates IS5413 practice questions, walks through database environments and database development step by step, and quizzes you on the material the exam weights most heavily.
Worked example
A table stores OrderID, CustomerID, CustomerName, ProductID, ProductName and Quantity, one row per order line. Which statement about its normal form is correct?
The key of an order-line table is (OrderID, ProductID).
Third normal form requires every non-key attribute to depend on the key, the whole key and nothing but the key.
Decompose into Customer, Product, Order and OrderLine tables; that is the logical-design step the syllabus calls normalisation.
The trap: Uniqueness of rows is first normal form territory; it says nothing about dependencies. classic slip!
One exam decides 70% of your grade. 2 hours; minimum 35%; must be passed. This whole page is built around that.
Overview
What IS5413 is, and where it sits
IS5413 Database Management Systems is a 3-credit-unit postgraduate course from the Department of Information Systems at City University of Hong Kong, offered in both Semester A and Semester B of 2026/27. It is a core course of the MSc Business and Data Analytics (Information Analytics Management stream) for the 2026/27 cohort and an elective in the department's other master's programmes.
The syllabus introduces the basic concepts of database systems: the methods and tools for the conceptual and logical design of database applications, and relational database models and languages for physical design and implementation. Lectures cover database concepts and users, DBMS architecture, record storage, file organisation and index structures; demonstrations apply the extended entity-relationship method, functional dependencies, normalisation and relational design; lab workshops build hands-on skills with the relational model and SQL.
Assessment is a 30% group project (report and presentation) and a 70% two-hour written examination. Students must pass both parts, with the catalogue stating minimum passing requirements of 15% for the coursework and 35% for the examination. The compulsory text is Hoffer, Venkataraman and Topi, Modern Database Management, 13th edition.
Always treat your own course outline and the exam timetable as authoritative.
Difficulty & time commitment
Is IS5413 hard, and how much time does it take?
IS5413 is manageable if you keep a weekly rhythm and treat the back half as the main event. The pattern is consistent: it starts gently and steepens, and the heaviest assessment is the part that separates grades.
The difficulty curve and the assessment weighting point the same way: the back half is harder and worth more. Front-loading effort there is the highest-return decision in the course.
Is this course for you
Who tends to do well, and who tends to struggle
You will likely do well if
- You can draw an ER diagram from a paragraph of business rules and defend each cardinality.
- You are prepared to write SQL by hand in an exam, not only run it in a lab.
- You keep a project on schedule with a group.
You may struggle if
- You treat the group project as the course; it is 30%, and the exam has its own pass floor.
- You learn SQL by copying and never trace what a query returns.
- You skip normalisation because the lab tool 'handles it'.
- Work every demonstration example twice: once with the slides, once from the business rules alone.
- Write the SQL for your group project's schema by hand before touching the DBMS.
- In the final fortnight, sit one full two-hour paper from the keyword syllabus under time.
Syllabus
The 10 topics, topic by topic
Topics from the public source. Their order is a content map, not an official weekly timetable or published exam weighting.
T1 · Database environments and architectures
Keyword syllabus 1; CILO 1Basic concepts, definitions and approaches; the components and architecture of a database system.
T2 · Database development and conceptual design with EER
Keyword syllabus 2; CILO 2The development process and conceptual design with the Enhanced Entity-Relationship approach.
T3 · The relational model and its languages
Keyword syllabus 3; CILO 1Three-layer relational architecture and the business benefits of the relational model.
T4 · Logical design and normalisation
Keyword syllabus 4; CILO 2Normalisation of relations and the business considerations behind it.
T5 · Physical design
Keyword syllabus 5Physical records, de-normalisation, file organisations, indexes and performance improvement.
T6 · SQL: data definition and manipulation
Keyword syllabus 6; CILO 3Writing SQL statements; choosing an RDBMS from the user's perspective.
T7 · Advanced SQL
Keyword syllabus 7; CILO 3Triggers, stored procedures, embedded and dynamic SQL, and XML.
T8 · Functional dependencies
LTA 2: demonstrationsThe theory behind normalisation, applied in the demonstrations.
T9 · Lab workshops: building the relational model
LTA 3: lab workshopsHands-on development of a relational database and its SQL.
T10 · Group project: report and presentation
AT1Applying the modelling concepts and database programming to a practical problem.
How it's assessed
Assessment structure
| Component | Weight | Format & timing |
|---|---|---|
| Coursework: group project with report and presentation, applying modelling and database programming to a practical problem | 30% | Group project with a written report and a presentation, applying entity-relationship modelling and database programming to a practical problem; GenAI allowed. Across the semester. Group; must be passed (minimum 15%). |
| Examination (2 hours) | 70% | Written examination assessing competence in the taught subjects. Examination period. 2 hours; minimum 35%; must be passed. |
- 30% coursework (group project) + 70% examination (2 hours). Students must pass BOTH coursework and examination; the catalogue states minimum passing requirements of 15% for continuous assessment and 35% for the examination. GenAI is allowed on the coursework.
- A two-hour written examination worth 70%, developed to assess competence in the taught subjects, with rubric criteria on explaining database concepts and architecture, designing a small database with ER modelling and relational theory, and implementing it in SQL with integrity constraints. A minimum examination mark of 35% is required.
This is an exam-cram course. With the exams at 70% of the grade and the examination (2 hours) alone at 70%, your result is overwhelmingly decided by how well you perform under time pressure. 2 hours; minimum 35%; must be passed.
Final exam timing: Written examination, 2 hours, in the examination period. Confirm the exact date and venue on your exam timetable.
How to actually pass it
A weekly rhythm, two checklists, and the traps to avoid
The course rewards consistency over cramming, and practice over re-reading. Here is the loop that works, then what to have nailed before each exam.
The weekly loop
The mistakes that cost marks
Formula & concept sheet
The vocabulary and formulas you must own
- Entity-relationship model
- A conceptual model of entities, attributes and relationships used to design a database.
- Normalisation
- Decomposing relations to remove redundancy and update anomalies.
- Functional dependency
- A constraint that one attribute's value determines another's.
- Primary key
- The attribute or set of attributes that uniquely identifies a row.
- Integrity constraint
- A rule the DBMS enforces to keep data valid.
- SQL
- The standard language for defining and manipulating relational data.
- Index
- A structure that speeds retrieval of rows by a column's values.
- Stored procedure
- SQL logic stored in the database and executed on demand.
Set texts
The prescribed reading
The syllabus references map straight onto these.
Hoffer, Venkataraman & Topi, Modern Database Management, 13th ed., Pearson, 2019
.
Where it fits
Prerequisites, related courses & why it matters
No prerequisites; 3 credit units, P5/P6; offered in Semester A and Semester B 2026/27. Core for the MSc BDA (IAM stream) 2026/27 cohort.
Your IS5413 study toolkit
Study the course with Sia, not just read about it
Use your permitted course notes with these study tools. Follow your course’s rules for AI and assessed work.
FAQ
Frequently asked questions
Is IS5413 hard?
Moderate to hard on the six-factor rubric, above the HK anchor: 70% rides on one two-hour exam with a 35% floor, and both components must be passed.
What is the assessment breakdown?
Coursework 30% (a group project with report and presentation) and examination 70% (2 hours), per the 2026/27 CityU catalogue. Minimum passing requirements: 15% coursework, 35% examination.
When is it offered?
Semester A and Semester B of 2026/27 according to the catalogue; the MSc BDA programme page places it in Semester B for its cohort.
Which programmes use it?
Core of the MSc Business and Data Analytics (IAM stream) for the 2026/27 cohort; elective in the MSc AI in Business, MSc Business Information Systems and MSc Digital Transformation and Technological Innovation.
Is there a textbook?
Yes: Hoffer, Venkataraman and Topi, Modern Database Management, 13th edition (Pearson, 2019) is compulsory; Elmasri and Navathe and Silberschatz and Korth are additional.
Can I use GenAI?
The syllabus allows GenAI on the coursework; the examination is a written paper.
Study IS5413 with Sia
Practise explaining the course concepts and check your reasoning. Confirm assessed-work requirements in your current outline.
Start studying with Sia
