Note: This unit is an archived version! See Overview tab for delivered versions.
INFO3404: Database Systems 2 (2017 - Semester 2)
Unit: | INFO3404: Database Systems 2 (6 CP) |
Mode: | Normal-Day |
On Offer: | Yes |
Level: | Senior |
Faculty/School: | School of Computer Science |
Unit Coordinator/s: |
A/Prof Roehm, Uwe
|
Session options: | Semester 2 |
Versions for this Unit: | |
Site(s) for this Unit: |
Campus: | Camperdown/Darlington |
Pre-Requisites: | None. |
Prohibitions: | INFO3504. |
Brief Handbook Description: | This unit of study provides a comprehensive overview of the internal mechanisms and algorithms of Database Management Systems (DBMS) and other systems that manage large data collections. These skills are needed for successful performance tuning and to understand the scalability challenges faced by the information age. This unit builds upon the second- year INFO2120 – 'Database Systems 1' and correspondingly assumes a sound understanding of SQL, schema design and transactional programs. The first part of this subject focuses on mechanisms for large-scale data management. It provides a deep understanding of the internal components of a database engine. Topics include: physical data organization and disk-based index structures, query processing and optimisation, locking and logging, and database tuning. The second part focuses on the large-scale management of textual data such as by an information retrieval system or with web search engines. Topics include: distributed and replicated databases, information retrieval, document management, text index structures, and web-scale data processing. The unit will be of interest to students seeking an introduction to database tuning, disk-based data structures and algorithms, and information retrieval. It will be valuable to those pursuing such careers as Software Engineers, Database Experts, Database Administrators, and e-Business Consultants. |
Assumed Knowledge: | This unit of study assumes that students have previous knowledge of database concepts including (1) ER modelling, (2) the relational data model and (3) SQL. The prerequisite material is covered in INFO 2120/2820. Familiarity with a programming language (e.g. Java or C) is also expected. |
Lecturer/s: |
Dr Jeffries, Bryn
A/Prof Roehm, Uwe |
|||||||||||||||||||||||||
Tutor/s: | cf. the unit's eLearning site | |||||||||||||||||||||||||
Timetable: | INFO3404 Timetable | |||||||||||||||||||||||||
Time Commitment: |
|
|||||||||||||||||||||||||
T&L Activities: |
|
Attributes listed here represent the key course goals (see Course Map tab) designated for this unit. The list below describes how these attributes are developed through practice in the unit. See Learning Outcomes and Assessment tabs for details of how these attributes are assessed.
Attribute Development Method | Attribute Developed |
In the practical assignment, students have to analyze and design an optimized physical database schema. | Design (Level 3) |
Students will learn several core techniques and algorithms for disk-based indexing, concurrency control, replication, distributed data processing and information retrieval. | Engineering/IT Specialisation (Level 3) |
Students will study the fundamental principles for efficient large-scale data management. | Maths/Science Methods and Tools (Level 3) |
Students are self-responsible for studying the documentation of the software used in the labs, as well as collecting background information for the pre-scribed readings and online quiz questions. | Information Seeking (Level 3) |
For explanation of attributes and levels see Engineering & IT Graduate Outcomes Table.
Learning outcomes are the key abilities and knowledge that will be assessed in this unit. They are listed according to the course goal supported by each. See Assessment Tab for details how each outcome is assessed.
Design (Level 3)Assessment Methods: |
|
||||||||||||||||||||||||||||||||||||
Assessment Description: |
Mid-Semester Quiz: online quiz to be solved in Wk9 by students and marked by tutors; includes electronic review questions on the concepts taught in this unit (Data Storage and Indexing, Query Processing and Optimization, Concurrency Control and Crash Recovery, Information Retrieval) Presentation of DB Concepts: create introductory video on a database concept that is shared with the tutorial class, to be done by pairs of students DB Programming Exercises (PASTA): weekly short programming exercises to implement selected database algorithms and data structures, submitted and auto-tested via PASTA (practical) Assignment: Database Performance Tuning and Programming Assignment (practical) Final Exam: Written Written examination reviewing the unit`s material (two hours) |
||||||||||||||||||||||||||||||||||||
Assessment Feedback: | Mid-Semester Feedback will be auto-graded and returned in subsequent weeks. Presentations will receive verbal or written feedback regarding correctness and peer review of instructiveness. Programming exercises will be assessed according to unit tests, with guidance on failing tests. Multiple submissions can be made. Assignment will receive written feedback according to marking rubric. |
||||||||||||||||||||||||||||||||||||
Grading: |
|
||||||||||||||||||||||||||||||||||||
Policies & Procedures: | IMPORTANT: School policy relating to Academic Dishonesty and Plagiarism. In assessing a piece of submitted work, the School of IT may reproduce it entirely, may provide a copy to another member of faculty, and/or to an external plagiarism checking service or in-house computer program and may also maintain a copy of the assignment for future checking purposes and/or allow an external service to do so. Other policies See the policies page of the faculty website at http://sydney.edu.au/engineering/student-policies/ for information regarding university policies and local provisions and procedures within the Faculty of Engineering and Information Technologies. |
Recommended Reference/s: |
Note: References are provided for guidance purposes only. Students are advised to consult these books in the university library. Purchase is not required.
|
Online Course Content: | USyd e-Learning |
Note on Resources: | Other material and prescribed readings may be specified through the unit of study web page in eLearning. |
Note that the "Weeks" referred to in this Schedule are those of the official university semester calendar https://web.timetable.usyd.edu.au/calendar.jsp
Week | Description |
Week 1 | Architecture of Database Systems |
Organisation and Administrativa | |
Week 2 | Physical Data Organisation |
Week 3 | Tree-based Index Structures |
Week 4 | Hash and Bitmap Indexes |
Week 5 | Text Indexing and Introduction to Information Retrieval |
Week 6 | Introduction to Query Processing and External Sorting |
Week 7 | Query Execution and Join Algorithms |
Week 8 | Query Optimization |
Week 9 | Crash Recovery |
Assessment Due: Mid-Semester Quiz | |
Week 10 | Transactions and Concurrency Control Schemes |
Week 11 | Distributed Databases |
Week 12 | Web Retrieval and Web Scale Data Management |
Assessment Due: Assignment | |
Week 13 | UoS Review |
Exam Period | Assessment Due: Final Exam |
Course Relations
The following is a list of courses which have added this Unit to their structure.
Course Goals
This unit contributes to the achievement of the following course goals:
Attribute | Practiced | Assessed |
Design (Level 3) | Yes | 28.25% |
Engineering/IT Specialisation (Level 3) | Yes | 46.26% |
Maths/Science Methods and Tools (Level 3) | Yes | 25.5% |
Information Seeking (Level 3) | Yes | 0% |
These goals are selected from Engineering & IT Graduate Outcomes Table which defines overall goals for courses where this unit is primarily offered. See Engineering & IT Graduate Outcomes Table for details of the attributes and levels to be developed in the course as a whole. Percentage figures alongside each course goal provide a rough indication of their relative weighting in assessment for this unit. Note that not all goals are necessarily part of assessment. Some may be more about practice activity. See Learning outcomes for details of what is assessed in relation to each goal and Assessment for details of how the outcome is assessed. See Attributes for details of practice provided for each goal.