Subject Outline

Subject Aim

 The aim of this subject is to introduce students to computers, object-oriented concepts and programming using Java. Students also gain a working knowledge of the Unix operating system. Topics covered include classes and objects, primitive data types, flow of control, methods, basic input/output and arrays. Software engineering principles are introduced, including coding standards, class design and testing strategies. Students are introduced to a framework for identifying and analysing ethical problems associated with software development. Here is the official outline (pdf) for this subject.

Content
  • Introduction to problem solving and programming
  • Introduction to Java
  • Operators and expressions
  • Input/output
  • Selection: if-else, switch
  • Iteration: while, for, for-each, do-while
  • Methods & parameter passing
  • Classes and objects
  • Arrays
  • Sorting & searching
  • Documentation & Testing

Lecturer, Tutor

 Mary Martin (Bendigo), x7273, m.martin@latrobe.edu.au

Prescribed Text

 Malik D.S., " Java Programming: From Problem Analysis To Program Design", (2nd or 3rd ed.) Thomson Course Technology, 2006/2007. ISBN 0-619-21608-5 (2nd ed.), 1-4239-0135-5 (3rd. ed.)

Class Requirements

 two 1-hour lectures, one 2-hour laboratory class and one 1-hour practice class per week for 13 weeks

Assessment

 Computer programming assignments equiv to 1,500-words (40%), and one two and a half hour examination at the end of the semester worth 60%. In order to pass the subject, students will obtain an overall pass grade, obtain at least 45% in the examination and pass the combined non-examination components.
Assessment Type %
five tutorial exercises (2% each)
10
two assignments (15% each)
30
one 2.5 -hour examination
60
TOTAL
100

Assessable Tutorial Exercises

 Submissions There are five (5) tutorial exercises that are assessable. Each is a single question taken from the laboratory sessions in weeks 2 to 6, clearly identified on the tutorial sheet. Each will take the form of a small Java program. The only submission required is that on the day specified, you email the Java code to your lecturer, as an attachment . (No hardcopy documentation is expected). These are not "marked" as such, but provide the tutor with evidence that you are progressing through the material. You will receive a response if there are major errors in your code (Java or logic errors).
Dates due
No. 1 to be emailed Tuesday 4/08/09
No. 2 to be emailed Tuesday 11/08/09
No. 3 to be emailed Tuesday 18/08/09
No. 4 to be emailed Tuesday 25/08/09
No. 5 to be emailed Tuesday 1/09/09

Assignments
  • Assignments must conform to the guidelines laid out in Chapter 2 of the La Trobe University, Bendigo Assignment Manual under the Section Heading TYPES OF ASSIGNMENTS: Computer Programming (p. 16) or as indicated by your lecturer.
  • All assignments must be firmly bound into a manilla or A4 size folder. Make sure that your name, the subject name, tutorial group number and assignment number are clearly written on the folder and title page.
  • It should be possible to read every page without undoing any fastenings or removing pages from plastic sleeving.
  • Output from printers must be clear and of good quality.
  • Plagiarism (ie. cheating) - IMPORTANT!!! (See Chapter 2 of your Assignment Manual)
    • The University's plagiarism policy states... "There are many forms of plagiarism, including the following: 1. (a) direct copying of sentences, paragraphs or other extracts from someone else's published work (including on the Internet and in software) without acknowledging the source; 2. (b) paraphrasing someone else's words without acknowledging the source; 3. (c) using facts and information derived from a source without acknowledging it; 4. (d) using ideas directly derived from an identifiable author without acknowledging the source; 5. (e) producing assignments which should be the student's own, independent work in collaboration with and/or using the work of other people (e.g. a student or tutor)."
    • Assignments are to be your own work. Group efforts will not be tolerated. Remember that the exam is designed to test your understanding of the work, thus it is important that you do not rely on other students to fill in gaps for you. In other words, programming is a "creative" task and you must "create" the solution to a problem (to which there are usually an infinite number of possibilities), NOT with the help of others (lecturer/tutors excepted). The solution you submit as an assignment MUST BE YOUR OWN CREATION. You may initially discuss the problem and possible solution with other students, but then go away and write YOUR OWN LOGICAL SOLUTION and YOUR OWN PROGRAM CODE. (Unfortunately, in academia, plagiarism occurs more often in programming assignments than any other form of assessment.)
    • NEVER give another student your logic, pseudo code or Java code. The University's plagiarism policy is clear on this matter and also states... "Assisting another person to plagiarise material may be punished as severely as is plagiarism itself. Assisting plagiarism may involve a student lending work (or by posting it on the Internet for sale) which is intended for submission for assessment, or which has already been submitted, so that it can be copied and handed in by another student as that student's own work."
    • PenaltiesThe University's policy conveys some leniency for first year students committing a first offence, but other cases (second offence or not a first-year student) it is highly likely that the student will be suspended from the institution. Depending on the situation, even "lenient" penalties include...
      • reduced marks
      • zero marks for piece of assessment
      • zero marks for subject
      • possible suspension
    • For the full policy, please refer to the University's Academic Policies page... http://www.latrobe.edu.au/policies/ ... where you will find a .pdf document describing the Academic Misconduct policy in full.
  • Each assignment must be accompanied by a signed "Statement of Authorship".
  • The assessment requires the examiner to view web pages and the source code submitted in assignments. It is a requirement that the location of any source code, images, javascript and css files together with the URL for the main page are included in the submission.

General Information
  • The security of your computer account, data and programs is your responsibility. Deleted programs or data will not be valid grounds for assignment extension.
  • Home computers can be used for developing your assignments but assignments submitted must be accompanied by proof that the program developed runs using your account on the University system.
  • As due dates for assignments draw nearer, the resources you require (staff, access time, references, workstations, data preparation) tend to become more difficult to obtain. The advantage of an early start to an assignment cannot be over-emphasised.
  • Misreading of the timetable for assignment and examination dates will not be accepted as reason for late submission of an assignment or absence from an examination.
  • Your subject tutor is your primary contact and should be consulted during tutorial sessions or during the available times as indicated by their respective timetables.
  • Please ensure that mobile phones are switched off or otherwise silenced in lectures and tutorials.
  • Please be aware that every student who attends lectures is entitled to listen or participate in an uninterrupted manner.