Unit Outline

This unit takes student database skills beyond an elementary knowledge of the SQL (Structured Query Language) database language to a level where they can undertake significant database systems development using both SQL and Oracle's procedural extension to SQL, PL/SQL. This unit seeks to develop knowledge and skills in: The SQL*Plus programming environment Developing and debugging SQL scripts Developing and debugging PL/SQL scripts Generating formatted reports using the appropriate SQL*Plus environment variables

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.	Apply SQL and related technologies to access and maintain a relational database
2.	Use SQL, PL/SQL and related technologies in creating a relational database
3.	Explore issues involved in database design, implementation and management

Requisites


REQUISITE TYPE	REQUISITES
Pre-requisite	KXO131 or KIT102

Alterations as a result of student feedback

Teaching arrangements


ATTENDANCE MODE	TEACHING TYPE	LEARNING ACTIVITY	CONTACT HOURS	FREQUENCY
On Campus	Lecture (On Campus)	A structured real-time (i.e. synchronous) activity that involves a mix of presentation of new information/ideas/skills and guided activities related to that information/ideas/skills. All students are expected to attend	2	Weekly
On Campus	Workshop	A structured real-time (i.e. synchronous) activity that involves a mix of presentation of new information/ideas/skills and guided activities related to that information/ideas/skills. All students are expected to attend.	1	Weekly
Online	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.	1	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:	Database Maintenance Report	Week 8	25 %	LO1, LO2
Assessment Task 2:	In-Workshop SQL Test	Week 9	25 %	LO1, LO2
Assessment Task 3:	Database Creation Report	Week 13	35 %	LO2, LO3
Assessment Task 4:	Weekly Quizzes	Refer to Assessment Description	15 %	LO3

Assessment details

Assessment Task 1: Database Maintenance Report

Task Description:

Develop additional functionality for an existing database by revising and writing scripts to extend the base SQL provided.

Type: In-Semester - individual assignment

Task Length:

Not applicable

Due Date:

Week 8

Weight:

25 %

CRITERION #

CRITERION

MEASURES INTENDED

LEARNING OUTCOME(S)


1	The required functionality has been added to the database	LO1
2	Correct SQL and PL/SQL have been applied	LO2

Assessment Task 2: In-Workshop SQL Test

Task Description:

Students are to complete a practical test during their assigned Workshop times. During the Workshop students will be required to complete database exercises using SQL, as outlined in the assessment sheet, and to complete the work before the end of their Workshop.

Task Length:

40 minute test, conducted during the Module 9 Workshop

Due Date:

Week 9

Weight:

25 %

CRITERION #

CRITERION

MEASURES INTENDED

LEARNING OUTCOME(S)


1	Apply SQL correctly to adapt an existing relational database	LO1
2	Use SQL correctly to create relational database	LO2
3	Apply SQL correctly to manipulate the properties of an existing relational database	LO1

Assessment Task 3: Database Creation Report

Task Description:

Students will create a relational database by writing SQL scripts to create appropriate tables, and SQL and PL/SQL scripts to process data and create reports. Students will also describe issues involved in database design, implementation and management.

Type: In-Semester - group assignment

Task Length:

Not applicable

Due Date:

Week 13

Weight:

35 %

CRITERION #

CRITERION

MEASURES INTENDED

LEARNING OUTCOME(S)


1	A working database has been created that meets the minimum requirements	LO2
2	Issues related to database design, implementation and management have been listed	LO3

Assessment Task 4: Weekly Quizzes

Task Description:

Students will complete a series of 20 multiple-choice questions that relate to material covered by the textbook chapter/s for each module. This assessment item allows students to apply their knowledge of the topics covered in the corresponding module, and to familiarise themselves with Database Management Systems (DBMS) concepts, terms, syntax, and semantics.

Quizzes are due weekly on Friday at 9pm.

Task Length:

20 online quiz questions in 45 minutes

Due Date:

Refer to Assessment Description

Weight:

15 %

CRITERION #

CRITERION

MEASURES INTENDED

LEARNING OUTCOME(S)


1	Identify issues in table creation and management	LO3
2	Identify issues in data manipulation	LO3

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.