Skip to content | Change text size

M O N A T A R

InfoTech Unit Avatar

CSE9002 Database Technology

Chief Examiner

This field records the Chief Examiner for unit approval purposes. It does not publish, and can only be edited by Faculty Office staff

To update the published Chief Examiner, you will need to update the Faculty Information/Contact Person field below.

NB: This view restricted to entries modified on or after 19990401000000

Unit Code, Name, Abbreviation

CSE9002 Database Technology (26 Apr 2004, 10:44am) []

Reasons for Introduction

Reasons for Introduction (26 Apr 2004, 11:13am)

This unit is a core unit for students studying the Graduate Diploma in Computing (course code 0360). It is a core unit in Group 1 of On-Campus study for the Master of Applied Information Technology, (Course Code 3309), and is a Foundation unit in the Master of Information Technology (Course Code 2402)

Role of Unit (27 Apr 2004, 10:16am)

The unit provides materials, both theoretical and practical, to students studying the Graduate Diploma in Computing, the Master of Applied Information Technology and the Master of Information Technology, to enable students to understand the basis of Relational Database concepts. This complements other units and the unit is designed such that assignment work in the conceptual, logical and physical stages of development of a database amalgamates skills developed in preceding units and also current units being studied.

Objectives

Unit Content

Summary (27 Apr 2004, 10:29am)

  • Database Definition. Advantages / Disadvantages. Ansi/Spark 3 level model. Database Terminology
  • Relations, Attributes, Domains, Base and Derived tables, Views. Relational Algebra
  • Database design cycle, E-R Modelling. Keys - Candidate, Super, Master, Foreign, Access
  • Local and Global Models. COnstrains. Integrity
  • Normalisation. Functional Dependencies. Normal Forms (1, 2, 3 and Boyce Codd)
  • SQL commands, functions and clauses.
  • Physical data storage. File organisations. Indexing
  • Data Administration, Data Base Administration and the Data Dictionary
  • Other non-relational database models
  • Trends in Relational Database - SQLX, Architectue, Inteligent Database SOftware

    • Recommended Reading (27 Apr 2004, 10:53am)

  • Connolly, T. and Begg, C. 'Database Systems - A Practical Approach to Design, Implementation and Management' (3rd Edition)
  • Other Readings : Date C.J 'An Introduction to Database Systems' (8th Edition). Hoffer, J.A., Prescott M.B., and McFadden, F.R. 'Modern Database Management'. 6th Edition

    • Teaching Methods

    Mode (27 Apr 2004, 11:03am)

  • One 2 hour lecture per week for 13 weeks
  • One 2 hour tutorial per week for 12 weeks. The tutorials are a mixture of 'problem discussion' in groups of 3 to 4 students, with presentation of a solution, hands on DBMS (Oracle)software problem solution, some advanced hands of using DBMS (Oracle), and one tutorial focussed on the use of Microsoft Access.
  • A 2 part assignment : Part 1 is the theoretical solution of a database design problem and Part 2 is the development of the Physical Design in a demonstrable solution.

    • Strategies of Teaching (27 Apr 2004, 11:10am)

  • The majority odf students in this unit do not have database experience
  • The teaching strategy is to advance from the understanding of the need for managed data as a basis for Information development and then to introduce database as the means by which this can be achieved.
  • Aspects of the use of SQL as the software medium are formally presented
  • Other support such as Integrity Constraints, Business Rules, Transaction Management and Security are also presented
  • The assignment is a practical manner in which students can mimic many of the above features

    • Teaching Methods Relationship to Objectives (27 Apr 2004, 11:17am)

  • The lectures are organised such that there is a flow and continuity over the 13 weeks.
  • Students are welcome to raise questions during lectures, and the tutorials are designed to both supplement the lecture materials and to give students the opportunity of collaboraton with other students +The Teaching objective is to ensure that each student develops, and can exhibit, a strong conversancy with many of the aspects of the design, development and use of database.

    • Assessment

    Strategies of Assessment (27 Apr 2004, 11:23am)

  • There is a 2 hour written theoretical examination.
  • Each tutorial session is based on theory or practice and discussion of a topic or topics
  • The assignment provides the opportunity for students to display their development of understanding of the many aspects of analysis, design and development of a working model to satisfy the design requirements.
  • The examination provides 65% of the marks for this unit, and the Assignment provides 35% of the unit marks.

    • Assessment Relationship to Objectives (27 Apr 2004, 11:54am)

  • The examination provides assessment of each student's understanding of the unit content. It is a 3 part paper with multichoice selection, short answer questions and some development questions.
  • The assignment provides the practical illustration of a student's capabilities.

    • Workloads

    Credit Points (27 Apr 2004, 11:55am)

    6

    Workload Requirement (27 Apr 2004, 12:00pm)

  • A 2 hour lecture for 13 weeks
  • A 2 hour tutorial for 12 weeks
  • An anticipated average of an additional 8 hours per week for the duration of the unit

    • Resource Requirements

    Lecture Requirements (27 Apr 2004, 12:03pm)

  • 1 lecturer for 13 weeks
  • A tutor for each 16 students for 12 weeks
  • A high technology lecture theatre for 13 weeks
  • Computer laboratories with access to Oracle DBMS and Microsoft Access for each of the tutorial sessions.
  • Access to these facilities on a out-of-hours basis

    • Tutorial Requirements (27 Apr 2004, 12:06pm)

  • Computer laboratories with access to Oracle DBMS and Microsoft Access
  • Each laboratory equipped with a whiteboard
  • A competent tutor for each group of 16 students

    • Laboratory Requirements (27 Apr 2004, 12:09pm)

  • Capability to connect to Oracle DBMS via Client devices
  • Capability to connect to Microsoft Access
  • Cabilility to connect to Microsoft Word

    • Staff Requirements (27 Apr 2004, 12:24pm)

  • 1 Lecturer for 13 weeks
  • 1 competent tutor for each 16 students for 12 weeks (includes Interviews)

    • Software Requirements (21 Oct 2005, 1:04pm)

  • Client access from Laboratories to the Oracle DBMS
  • Microsoft Office software

    • Library Requirements (27 Apr 2004, 12:33pm)

    Availability of Texts

  • 8th Edition An Introduction to Database Systems. Date C.J.
  • 3rd Edition Database Systems - A Practical Approach to Design, Implementation and Management 3rd edition
  • 6th Edition Modern Database Management - Hoffer J. A, Prescott M.B., and McFadden F. R.
  • No other resources required.

    • Teaching Responsibility (Callista Entry) (27 Apr 2004, 12:40pm)

    School of Computer Science and Software Engineering, (SCSSE), Faculty of Information Technology

    Implications for CASPA (27 Apr 2004, 12:41pm)

    No

    Interfaculty Involvement (27 Apr 2004, 12:41pm)

    None

    Interschool Involvement (27 Apr 2004, 12:43pm)

    None

    Prerequisites

    Prerequisite Units (27 Apr 2004, 12:46pm)

    None

    Corequisites (27 Apr 2004, 12:48pm)

    None

    Prohibitions (21 Feb 2007, 10:20am)

    BUS2112, CFR2132, CFR2201, COT2132, COT2138, COT2180, COT3180, CSE2132, CSE2138, CSE2180, CSE3180, CSC3161, COT7710, IMS9003

    Frequency of Offering (27 Apr 2004, 12:55pm)

    First Semester. Second Semester.

    Enrolment (27 Apr 2004, 1:05pm)

    Approximately 100 - 120 students per semester.

    Location of Offering (27 Apr 2004, 1:05pm)

    Caulfield Campus

    Faculty Information

    Proposer

    Rodney Simpson

    Approvals

    School: 26 Mar 2007 (Geraldine DCosta)
    Faculty Education Committee: 26 Mar 2007 (Geraldine DCosta)
    Faculty Board: 26 Mar 2007 (Geraldine DCosta)
    ADT:
    Faculty Manager:
    Dean's Advisory Council:
    Other:

    Version History

    26 Apr 2004 Rodney Simpson Initial Draft; modified UnitName; modified ReasonsForIntroduction/RIntro
    27 Apr 2004 Rodney Simpson modified ReasonsForIntroduction/RRole; modified UnitContent/Summary; modified UnitContent/RecommendedReading; modified Teaching/Mode; modified Teaching/Strategies; modified Classification; modified Teaching/Objectives; modified Assessment/Strategies; modified Assessment/Objectives; modified Assessment/Objectives; modified Workload/CreditPoints; modified Workload/WorkHours; modified ResourceReqs/LectureReqs; modified ResourceReqs/TutorialReqs; modified ResourceReqs/LabReqs; modified ResourceReqs/StaffReqs; modified ResourceReqs/SoftwareReqs; modified ResourceReqs/LibraryReqs; modified ResourceReqs/SchoolReqs; modified ResourceReqs/CaspaImpact; modified ResourceReqs/InterFaculty; modified ResourceReqs/IntraFaculty; modified ResourceReqs/OtherReqs; modified ResourceReqs/OtherReqs; modified ResourceReqs/OtherReqs; modified Prerequisites/PreReqUnits; modified Prerequisites/PreReqKnowledge; modified Corequisites; modified Prohibitions; modified Prohibitions; modified Frequency; modified Enrolment; modified LocationOfOffering; modified FacultyInformation/FICoordinator; modified FacultyInformation/FIContact
    27 Apr 2004 Rodney Simpson
    17 Oct 2005 David Sole Added Software requrirements template
    21 Oct 2005 David Sole Updated requirements template to new format
    21 Feb 2007 Kerry Tanner modified Prohibitions
    26 Mar 2007 Geraldine DCosta CSE School Approval, Approved by Graduate Postgraduate Programs Committee on 8/3/07
    26 Mar 2007 Geraldine DCosta FEC Approval
    26 Mar 2007 Geraldine DCosta FacultyBoard Approval - The Graduate Postgraduate Programs Committee now has authority to formally approve minor unit amendments. The GPG Programs Committee has approved this version on 8/3/07. Faculty Board approval has been added to aid administration in Monatar.

    This version: