Unit Outline

This unit is designed to introduce students to the fundamental concepts necessary for the analysis, design, use and implementation of a database management system for the management of data in modern organisations. Students will develop skills in planning, designing, and implementing a data model using an enterprise-scale database system. This unit is designed for students to extend their programming abilities in developing relatively large database applications. Topics covered include the principal aspects of database development and applications, advanced queries to populate, retrieve, and update data, database programming with triggers, procedures and functions. This unit also introduces students to the principles and practice of administering enterprise-level database systems. Topics include database architecture; DBMS installation and configuration issues; user management and DBA tools.

Intended Learning Outcomes

As per the Assessment and Results Policy 1.3, your results will reflect your achievement against specified learning outcomes.

On completion of this unit, you will be able to:


1.	Evaluate, critically analyse and compare alternative techniques and data models for designing databases
2.	Adapt and apply techniques and processes for designing, implementing and administering an enterprise level relational database
3.	Design sophisticated SQL queries to efficiently retrieve information from relational databases
4.	Identify data storage and retrieval issues with current trends and advances in database technologies

Requisites


REQUISITE TYPE	REQUISITES
Pre-requisite	KIT502 OR KIT506

Alterations as a result of student feedback

Additional videos and documentation will be added to help students in understanding the content.

Teaching arrangements


ATTENDANCE MODE	TEACHING TYPE	LEARNING ACTIVITY	CONTACT HOURS	FREQUENCY
On Campus	Lecture (On Campus)	A real-time (i.e. synchronous) interactive activity involving the whole class whose primary purpose is the presentation and structuring of information/ideas/skills to facilitate student learning. All students are expected to attend.	2	Weekly
	Computer Laboratory	A structured real-time (i.e. synchronous) computer-based activity in a small-group setting where the primary purpose is the clarification, exploration or reinforcement of subject content presented or accessed at another time or place (e.g. lecture, preparatory work). It is teacher supported and may involve student-teacher and/or student-student interaction and dialogue for achievement of its learning outcomes. The students enrolled in the class are expected to attend	2	Weekly
	Independent Learning	Involving reading, listening to audio, watching video, and/or completing exercises and/or quizzes, self-study is individual work undertaken when the student chooses (i.e. asynchronous), most likely through engagement with MyLO. The content is examinable, and may need to be completed prior to attending classes and/or attempting assessment tasks.	2	Weekly

Attendance / engagement expectations

If your unit is offered On campus, it is expected that you will attend all on-campus and onsite learning activities. This is to support your own learning and the development of a learning community within the unit. If you are unable to attend regularly, please discuss the situation with your course coordinator and/or our UConnect support team.

If your unit is offered Online, it is expected you will engage in all those activities as indicated in the Unit Outline, including any self-directed learning.

If you miss a learning activity for a legitimate reason (e.g., illness, carer responsibilities) teaching staff will attempt to provide alternative activities (e.g., make up readings) where it is possible.

How will I be Assessed?

For more detailed assessment information please see MyLO.

Assessment schedule


ASSESSMENT TASK #	ASSESSMENT TASK NAME	DATE DUE	WEIGHT	LINKS TO INTENDED LEARNING OUTCOMES
Assessment Task 1:	Test 1	Week 6	20 %	LO1, LO2, LO3, LO4
Assessment Task 2:	Test 2	Week 13	25 %	LO1, LO2, LO3, LO4
Assessment Task 3:	Database Design and Implementation	Week 14	35 %	LO1, LO2, LO3, LO4
Assessment Task 4:	Tutorial Quiz	Refer to Assessment Description	20 %	LO1, LO2, LO3, LO4

Assessment details

Assessment Task 1: Test 1

Task Description:

This practical test will be conducted during the tutorials and will assess students' skill in designing databases and SQL statements.

Task Length:

1 Hour

Due Date:

Week 6

Weight:

20 %

CRITERION #

CRITERION

MEASURES INTENDED

LEARNING OUTCOME(S)


1	Correctly design and implement an SQL database	LO1, LO2
2	Correctly design SQL queries based on user requirements	LO3
3	Correctly identify issues in a given SQL query	LO3, LO4

Assessment Task 2: Test 2

Task Description:

This test will evaluate students understanding of practical PL/SQL coding and database administrative skills.

Task Length:

1 Hour 20 Minutes

Due Date:

Week 13

Weight:

25 %

CRITERION #

CRITERION

MEASURES INTENDED

LEARNING OUTCOME(S)


1	Correctly identify the issues in PL/SQL code	LO2, LO3
2	Correctly write PL/SQL blocks	LO2, LO3
3	Correctly administer a database for a set of users	LO1, LO2, LO4

Assessment Task 3: Database Design and Implementation

Task Description:

Complete Database Design & Implementation - This assessment is designed in such a way that students demonstrate their understanding in a practical manner on all database management principles. This assignment has multiple stages of submission with each stage having feedback. In the first stage, students need to first collect business rules by understanding how an organisation works and what data it needs to store for different processes. Business rules need to be submitted to the tutor within one week from time the assignment is announced. For other stages, lecturer/tutor may either advise you to modify these rules or may give new business rules. If the tutor asks you to modify your business rules, you need to update them based on the comments. From these updated or new business rules, you will be asked to model the situation using Entity Relationship Modelling (as taught in the unit) [Stage 2]. The design will then be used to generate a relational schema to create appropriate tables under Enterprise system. In final stage [Stage 3], students need to submit the ER Diagram and relational model with database tables. Students need to also implement all constraints stated in business rules.

Task Length:

5 pages of documentation and a set of SQL files

Due Date:

Week 14

Weight:

35 %

CRITERION #

CRITERION

MEASURES INTENDED

LEARNING OUTCOME(S)


1	Design an optimised ER Diagram that captures Entity, Relationships, cardinality, attributes and participation correctly based on business rules ER Diagram captures correct type and number of Entity and Relationships	LO1, LO2, LO4
2	Apply correctly the algorithm for ER Diagram to Relational Model Conversion	LO2
3	Correct implementation of Database tables based on Relational Model and Business rules using appropriate enterprise level relational database technology	LO2, LO3
4	Correct design and implementation of advanced & optimised queries and triggers using SQL & PL/SQL	LO2, LO3, LO4

Assessment Task 4: Tutorial Quiz

Task Description:

At the start of every tutorial there will be short quiz. Quiz will be based on the lecture that covered the topic of the tutorial.

Task Length:

10 Minutes

Due Date:

Refer to Assessment Description

Weight:

20 %

CRITERION #

CRITERION

MEASURES INTENDED

LEARNING OUTCOME(S)


1	Describe techniques and data models for designing databases	LO1, LO2, LO3, LO4
2	Explain how techniques and processes can be used for designing, implementing and administering an enterprise level database	LO1, LO2, LO3, LO4
3	Design optimized SQL queries to retrieve information from relational databases	LO1, LO2, LO3, LO4
4	Identify data storage and retrieval issues in databases	LO1, LO2, LO3, LO4

How your final result is determined

To pass this unit, you need to demonstrate your attainment of each of the Intended Learning Outcomes, achieve a final unit grade of 50% or greater, and pass any hurdle tasks.

Submission of assignments

Where practicable, assignments should be submitted to an assignment submission folder in MYLO. You must submit assignments by the due date or receive a penalty (unless an extension of time has been approved by the Unit Coordinator). Students submitting any assignment in hard copy, or because of a practicum finalisation, must attach a student cover sheet and signed declaration for the submission to be accepted for marking.

Requests for extensions

If you are unable to submit an assessment task by the due date, you should apply for an extension.

A request for an extension should first be discussed with your Unit Coordinator or teaching support team where possible. A request for an extension must be submitted by the assessment due date, except where you can provide evidence it was not possible to do so. Typically, an application for an extension will be supported by documentary evidence: however, where it is not possible for you to provide evidence please contact your Unit Coordinator.

The Unit Coordinator must notify you of the outcome of an extension request within 3 working days of receiving the request.

Late penalties

Assignments submitted after the deadline will receive a late penalty of 5% of the original available mark for each calendar day (or part day) that the assignment is late. Late submissions will not be accepted more than 10 calendar days after the due date, or after assignments have been returned to other students on a scheduled date, whichever occurs first. Further information on Late Penalties can be found on the Assessments and Results Procedure.

Review of results and appeals

You are entitled to ask for a review of the marking and grading of your assessment task if there is an irregularity in the marking standards or an error in the process for determining the outcome of an assessment. Details on how to request a review of a mark for an assignment are outlined in the Review and Appeal of Academic Decisions Procedure.