CSE2132 , Unit Information Guide (Semester 1, 2006)

Chief Examiner R Redpath
Lecturers
Caulfield : R Redpath
Outline This is the students first database unit in the B Computing degree where they learn to design and implement a database.
Objectives

On the successful completion of this course students will:

            . have an understanding of database concepts

            . have an understanding of database definition and manipulation

             . be familiar with the use of SQL both interactive and with procedural extensions and the features of a commercial relational database system

            . be aware of the different models for the development of database systems
Prerequisites

It has a prerequisite of CSE1201. Knowledge of operating systems/file systems and a basic computer architecture is required to achieve the unit objectives

Unit relationships CSE2132 is a core unit in the Bachelor of Computing. It is a prerequisite for subsequent database elective units presented by the Caulfield School of Information Technology. It is a prohibition with other introductory database units in the faculty including FIT1004.
Texts and software

Required text(s)

Kifer M., Bernstein A. & Lewis P.M.; Database Systems: An Application-Oriented Approach 2nd Edn., Pearson/Addison-Wesley, 2005;

OR

Hoffer, J.A., Prescott, M.B. & McFadden,F.R.; Modern Database Management 7th Edn., Pearson Education Inc-Prentice-Hall, 2005     

 

 


 


Hoffer, J.A., Prescott, M.B. & McFadden,F.R.; Modern Database Management
7th Edn., Pearson Education Inc-Prentice-Hall, 2005     

Text books are available from the Monash University Book Shops. Availability from other suppliers cannot be assured. The Bookshop orders texts in specifically for this unit. You are advised to purchase your text book early.

Software requirements:

Oracle 10g (database; available in teh uni labs)

Gershwin (Entity/Relationship modelling software down load from MUSO website)

Software may be:

  • downloaded from

Hardware requirements:

 On-campus students, and those studying at supported study locations may use the facilities available in the computing labs. Information about computer use for students is available from the ITS Student Resource Guide in the Monash University Handbook. You will need to allocate up to 4 hours per week for use of a computer, including time for newsgroups/discussion groups.

Recommended reading

Morris-Murphy, Lannes L. Oracle9i: SQL : with an introduction to PL/SQL, Thomson Course Technology, 2003

Lorents, A.L. & Morgan, J.N.; Database Systems: Concepts, Management and Applications, Harcourt Brace, 1998

Rob, P. & Coronel, C; Database Systems: Design, Implementation, and Management, 4th Edn, Nelson 2000

Date, C.J.; An Introduction to Database Systems ,
            7th Edn., Addison-Wesley, 2000

Elmasri, R & Navathe, SD Fundamentals of Database
            Systems,  3rd Edition, Addison-Wesley, 2000

Library access You may need to access the Monash library either personally to be able to satisfactorily complete the subject.  Be sure to obtain a copy of the Library Guide, and if necessary, the instructions for remote access from the library website.
Study resources

Study resources for CSE2132 are:

A set of printed materials conatining syllabus, tutorial questions and assignments(The syllabus and assignment are also at teh web site); Obtainable from the lecturer

Structure and organisation

Week

Topics

Study Guide

References/Readings

1 Database Theory Motivation for DBMS K&B Ch1 1.1 to 1.3, H&P Ch1 all NB p.23-31 Ch12 NB p.516-525,
2 The database design lifecycle in the context of the System development lifecycle K&B Ch2.2, Ch 3,H&P Ch2 Ch5 p.188-190, L&M Ch4, R&C Ch6
3 SQL Data Manipulation K&B Ch5 H&P Ch7&8, L&M Ch6, R&C Ch3
4 Conceptual Data Modeling K&B Ch 4.1 to 4.3, H&P Ch3, L&M Ch2,R&C Ch2 p.58 Ch4 p.185-215
5 Logical Database Design K&B Ch 4.4 & Ch12 12.2, H&P Ch5 p.197-210 Ch6 p.245-249, L&M Ch7, R&C Ch4 p.216-237 Ch5 p.272
6 Normalization : K&B Ch 6.1 to 6.5, H&P Ch5 p.211-219, L&M Ch3,R&C Ch5 p.253-265
7 Relational Integrity Rules Domains K&B Ch 3.2.2, H&P Ch5 p.192-196 Ch8 p.346-349,R&C Ch3 p113-114, p150-156
Non-teaching
8 PL/SQL; A procedural SQL K&B Ch 7 ,H&P Ch8 p.346-349
9 The Cursor Concept Oracle Documentation
10 Physical Database Design; File Organizations,Tree data structures; Data Structures K&B Ch 9.1 to 9.3, H&P Ch6 p.238-244, p.251-261, L&M Ch11 p.442-463
11 Physical Database Design; Indexes K&B Ch 9.4 to 9.8, H&P Ch6 p.262-263,L&M Ch7 p287 R&C Ch8 p398-399
12 Distributed database H&P Ch13, L&M Ch12, R&C Ch10
13 Revision ( Preview Data Warehousing/Data mining)
Timetable

The timetable for on-campus classes for this unit can be viewed in Allocate+

Assessment

Students must attend at least 10 tutorials as a hurdle requirement unless documentation for absences is provided.
           
Assessment will consist of one examination primarily designed to test theoretical knowledge, and three practical assignments; all of which must be attempted. It is better to hand in an incomplete assignment than no assignment at all.

 

In order to pass this unit, you must score at least 40% of the total marks for the tests and the exam (the theory component) and at least 40% of the total marks for the assignments (the practical component), as well as obtaining at least 50% overall.  If you do not pass the 40% rule for either the theory or the practical component, your final mark for the unit will be no more than 44%.
            For all practical assignments your submission must be uniquely your own work. None should be completed in association with other students. The full weight of university regulations will be brought to bear on any students detected cheating and those students who allow others to use their work will be treated with equal severity. At a minimum the students involved will receive no credit for the assignment and may be awarded an automatic fail for the unit overall.

 

Assignment                                                                             Due Date
1. Conceptual and Logical Database Design (20%)    Week 8           
2. Database Implementation using SQL (20%)           Week 12

Assessment Policy

To pass this unit you must:

Obtain at least 40% for assignement work and at least 40% for the examination and at least 50% overall.

Your score for the unit will be calculated by:

Assignment 1 : 20%

Assignment 2 : 20%

Examination : 60%

Assessment Requirements

Assessment

Due Date

Weighting

1. Conceptual and Logical Database Design 26/4/2006 20 %
2. Database Implementation using SQL 24/5/2006 20 %
Examination 2 hour(s), closed book Exam period starts 5th June. 60 %

Assignment specifications will be made available . Information about assignments will be published on the Unit's Notices Newsgroup.

Assignment Submission Methods

Assignment 1 will be submitted by paper submission to your tutor in the tutorial you attend.

Assignment 2 will be submitted electronically via MUSO.

Extensions and late submissions

Late submission of assignments

Assignments received after the due date will be subject to a penalty of 10% for each day they are overdue up to 3 days. Assignments received later than three days after the due date will not normally be accepted.

This policy is strict because comments or guidance will be given on assignments as they are returned, and sample solutions may also be published and distributed, after assignment marking or with the returned assignment. 

Extensions

It is your responsibility to structure your study program around assignment deadlines, family, work and other commitments. Factors such as normal work pressures, vacations, etc. are seldom regarded as appropriate reasons for granting extensions. 

Requests for extensions must be made by filling the form avaiulable at reception 6th level H building at least two days before the due date. You will be asked to forward original medical certificates in cases of illness, and may be asked to provide other forms of documentation where necessary. A copy of the written communication of an extension must be submitted to your tutor.

Grading of assessment

Assignments, and the unit, will be marked and allocated a grade according to the following scale:

HD High Distinction - very high levels of achievement, demonstrated knowledge and understanding, skills in application and high standards of work encompassing all aspects of the tasks.
In the 80+% range of marks for the assignment.
D Distinction - high levels of achievement, but not of the same standards. May have a weakness in one particular aspect, or overall standards may not be quite as high.
In the 70-79% range.
C Credit - sound pass displaying good knowledge or application skills, but some weaknesses in the quality, range or demonstration of understanding.
In the 60-69% range.
P Pass - acceptable standard, showing an adequate basic knowledge, understanding or skills, but with definite limitations on the extent of such understanding or application. Some parts may be incomplete.
In the 50-59% range.
N Not satisfactory -  failure to meet the basic requirements of the assessment.
Below 50%.

We will aim to have assignment results made available to you within two weeks after assignment receipt.

Feedback Feedback to you

You will receive feedback on your work and progress in this unit. This feedback may be provided through your participation in tutorials and class discussions, as well as through your assignment submissions. It may come in the form of individual advice, marks and comments, or it may be provided as comment or reflection targeted at the group. It may be provided through personal interactions, such as interviews and on-line forums, or through other mechanisms such as on-line self-tests and publication of grade distributions.

Feedback from you

You will be asked to provide feedback to the Faculty through a Unit Evaluation survey at the end of the semester. You may also be asked to complete surveys to help teaching staff improve the unit and unit delivery. Your input to such surveys is very important to the faculty and the teaching staff in maintaining relevant and high quality learning experiences for our students.

And if you are having problems

It is essential that you take action immediately if you realise that you have a problem with your study. The semester is short, so we can help you best if you let us know as soon as problems arise. Regardless of whether the problem is related directly to your progress in the unit, if it is likely to interfere with your progress you should discuss it with your lecturer or a Community Service counsellor as soon as possible.

Plagiarism and cheating

Plagiarism and cheating are regarded as very serious offences. In cases where cheating  has been confirmed, students have been severely penalised, from losing all marks for an assignment, to facing disciplinary action at the Faculty level. While we would wish that all our students adhere to sound ethical conduct and honesty, I will ask you to acquaint yourself with Student Rights and Responsibilities and the Faculty regulations that apply to students detected cheating as these will be applied in all detected cases.

In this University, cheating means seeking to obtain an unfair advantage in any examination or any other written or practical work to be submitted or completed by a student for assessment. It includes the use, or attempted use, of any means to gain an unfair advantage for any assessable work in the unit, where the means is contrary to the instructions for such work. 

When you submit an individual assessment item, such as a program, a report, an essay, assignment or other piece of work, under your name you are understood to be stating that this is your own work. If a submission is identical with, or similar to, someone else's work, an assumption of cheating may arise. If you are planning on working with another student, it is acceptable to undertake research together, and discuss problems, but it is not acceptable to jointly develop or share solutions unless this is specified by your lecturer. 

Intentionally providing students with your solutions to assignments is classified as "assisting to cheat" and students who do this may be subject to disciplinary action. You should take reasonable care that your solution is not accidentally or deliberately obtained by other students. For example, do not leave copies of your work in progress on the hard drives of shared computers, and do not show your work to other students. If you believe this may have happened, please be sure to contact your lecturer as soon as possible.

Cheating also includes taking into an examination any material contrary to the regulations, including any bilingual dictionary, whether or not with the intention of using it to obtain an advantage.

Plagiarism involves the false representation of another person's ideas, or findings, as your own by either copying material or paraphrasing without citing sources. It is both professional and ethical to reference clearly the ideas and information that you have used from another writer. If the source is not identified, then you have plagiarised work of the other author. Plagiarism is a form of dishonesty that is insulting to the reader and grossly unfair to your student colleagues.

Communication

Notices

Notices related to the unit during the semester will be placed on the Notices Newsgroup in the Unit Website. Check this regularly. Failure to read the Notices newsgroup is not regarded as grounds for special consideration.

Consultation Times

Consultation is available Mon 3pm to 5pm and Tue 2pm to 4pm and at other times if the lecturer is in his office(H5.33).

If direct communication with your unit adviser/lecturer or tutor outside of consultation periods is needed you may contact the lecturer and/or tutors at:

This person's profile is not available.Image of this person is not available.

This person's profile is not available.Image of this person is not available.

This person's profile is not available.Image of this person is not available.

This person's profile is not available.Image of this person is not available.

All email communication to you from your lecturer will occur through your Monash student email address. Please ensure that you read it regularly, or forward your email to your main address. Also check that your contact information registered with the University is up to date in My.Monash.

Last updated: Mar 24, 2006