Overview
In this unit, you will develop the skills to design and develop GUI-based object-oriented applications using a subset of the Java programming language and its libraries. Defensive programming – an integral component of secure programming – will be introduced and practiced. A focus of the unit will be an emphasis on current best practice in Java application development as it applies to processes, environments, design, coding, testing and documentation.
Details
Pre-requisites or Co-requisites
Pre-requisite: COIT20245 Introduction to Programming
Important note: Students enrolled in a subsequent unit who failed their pre-requisite unit, should drop the subsequent unit before the census date or within 10 working days of Fail grade notification. Students who do not drop the unit in this timeframe cannot later drop the unit without academic and financial liability. See details in the Assessment Policy and Procedure (Higher Education Coursework).
Offerings For Term 2 - 2024
Attendance Requirements
All on-campus students are expected to attend scheduled classes - in some units, these classes are identified as a mandatory (pass/fail) component and attendance is compulsory. International students, on a student visa, must maintain a full time study load and meet both attendance and academic progress requirements in each study period (satisfactory attendance for International students is defined as maintaining at least an 80% attendance record).
Recommended Student Time Commitment
Each 6-credit Postgraduate unit at CQUniversity requires an overall time commitment of an average of 12.5 hours of study per week, making a total of 150 hours for the unit.
Class Timetable
Assessment Overview
Assessment Grading
This is a graded unit: your overall grade will be calculated from the marks or grades for each assessment task, based on the relative weightings shown in the table above. You must obtain an overall mark for the unit of at least 50%, or an overall grade of 'pass' in order to pass the unit. If any 'pass/fail' tasks are shown in the table above they must also be completed successfully ('pass' grade). You must also meet any minimum mark requirements specified for a particular assessment task, as detailed in the 'assessment task' section (note that in some instances, the minimum mark for a task may be greater than 50%). Consult the University's Grades and Results Policy for more details of interim results and final grades.
All University policies are available on the CQUniversity Policy site.
You may wish to view these policies:
- Grades and Results Policy
- Assessment Policy and Procedure (Higher Education Coursework)
- Review of Grade Procedure
- Student Academic Integrity Policy and Procedure
- Monitoring Academic Progress (MAP) Policy and Procedure - Domestic Students
- Monitoring Academic Progress (MAP) Policy and Procedure - International Students
- Student Refund and Credit Balance Policy and Procedure
- Student Feedback - Compliments and Complaints Policy and Procedure
- Information and Communications Technology Acceptable Use Policy and Procedure
This list is not an exhaustive list of all University policies. The full list of University policies are available on the CQUniversity Policy site.
Feedback, Recommendations and Responses
Every unit is reviewed for enhancement each year. At the most recent review, the following staff and student feedback items were identified and recommendations were made.
Feedback from Head of Course
The prerequisite unit has been modified. As from term 2, 2024, COIT20256 will become the first Java programming unit.
Change the name of the unit from Data Structures and Algorithms to Object Oriented Development. Change the learning outcomes for the unit. Change the content to match the new learning outcomes.
Feedback from Feedback from students and the teaching team
Program assignments and tutorial exercises were engaging and helped students to understand the concepts being taught.
New tutorials and programming assessments will be developed to assess the new learning outcomes. However, the types of tasks and breakdown of marks will remain the same.
Feedback from Feedback from students
Some students found that there was a lot of new content (and a large number of slides presented each week). They found the content, pace and concepts quite challenging.
The materials are to be redeveloped as a result of the changes to the prerequisite unit. Investigate options for providing additional support for students who find the unit challenging.
Feedback from Feedback from students and the teaching team
The unit learning materials are useful and help the student learning.
While the positive feedback was pleasing this unit will have to undergo significant changes due to the changes to the prerequisite unit. From term 2 2024 this unit will become the first Java programming unit so its starting point and end point in terms of content will be different to the current unit. As a consequence, the learning outcomes have been modified for term 2 2024.
- Apply procedural concepts (methods, iteration, selection) to the realisation of object behaviour
- Apply the fundamental practices of defensive programming (encapsulation, testing, input validation), documentation and version control to software development
- Develop GUI based applications that employ inheritance, interfaces, polymorphism, exceptions, lambdas and sequential file processing
- Implement standard algorithms such as searching, sorting, and sequential processing for arrays and generic collections of objects
- Demonstrate command of the subset of the programming language presented in this unit, including its syntax, type system, data representations, scope rules, and libraries.
The Australian Computer Society (ACS), the professional association for Australia's ICT sector, recognises the Skills Framework for the Information Age (SFIA). SFIA is adopted by organisations, governments, and individuals in many countries and provides a widely used and consistent definition of ICT skills. SFIA is increasingly being used when developing job descriptions and role profiles. ACS members can use the tool MySFIA to build a skills profile.
This unit contributes to the following workplace skills as defined by SFIA 8 (the SFIA code is included):
- Software Design (SWDN)
- System Integration and Build (SINT)
- Programming/Software Development (PROG)
- Data modelling and design (DTAN)
- Database Design (DBDS)
- Testing (TEST)
- User experience analysis (UNAN)
- User experience design (HCEV).
Alignment of Assessment Tasks to Learning Outcomes
| Assessment Tasks | Learning Outcomes | ||||
|---|---|---|---|---|---|
| 1 | 2 | 3 | 4 | 5 | |
| 1 - Practical Assessment - 20% | |||||
| 2 - Practical Assessment - 10% | |||||
| 3 - Practical Assessment - 20% | |||||
| 4 - Examination - 50% | |||||
Alignment of Graduate Attributes to Learning Outcomes
| Graduate Attributes | Learning Outcomes | ||||
|---|---|---|---|---|---|
| 1 | 2 | 3 | 4 | 5 | |
| 1 - Knowledge | |||||
| 2 - Communication | |||||
| 3 - Cognitive, technical and creative skills | |||||
| 4 - Research | |||||
| 5 - Self-management | |||||
| 6 - Ethical and Professional Responsibility | |||||
| 7 - Leadership | |||||
| 8 - Aboriginal and Torres Strait Islander Cultures | |||||
Textbooks
Java How to Program, Early Objects, Global Edition
11th Edition (2018)
Authors: Paul Deitel and Harvey Deitel
Pearson Education
ISBN: 9780134743356
Binding: Paperback
IT Resources
- CQUniversity Student Email
- Internet
- Unit Website (Moodle)
- JDK 21 (available from https://www.oracle.com/java/technologies/downloads or https://jdk.java.net/21/)
- JavaFX (downloaded in NetBeans when use JavaFX Maven archetype)
- SceneBuilder 21 (or higher) (available from https://gluonhq.com/products/scene-builder, current version 21.0)
- Apache NetBeans IDE 20 (https://netbeans.apache.org/download/index.html)
All submissions for this unit must use the referencing styles below:
For further information, see the Assessment Tasks.
j.jarvis@cqu.edu.au
Module/Topic
Java input/output, Arithmetic Operators, Introduction to String class
Chapter
1, 2 and online resources.
Events and Submissions/Topic
Module/Topic
Control Statements and More About Operators
Chapter
4, 5 and online resources
Events and Submissions/Topic
Module/Topic
Classes, Objects, Methods
Chapter
3, 6 and online resources
Events and Submissions/Topic
Tutorial assessment: Part 1 - due in week 3 tutorial class
(Assessment item 2 / Tutorial assessment commences: this work is to be developed and submitted in weekly tutorial classes from week 3 -12)
Module/Topic
Arrays and ArrayLists; Introduction to Searching and Sorting.
Chapter
7, 19 and online resources
Events and Submissions/Topic
Tutorial assessment: Part 2 - due in week 4 tutorial class
Module/Topic
Classes and Objects: A Deeper Look
Chapter
8
Events and Submissions/Topic
Tutorial assessment: Part 3 - due in week 5 tutorial class
Programming Assignment 1 - phase 1 due Monday 9:00am (AEST) (Submission of completed assignment due in week 6)
Module/Topic
Chapter
Events and Submissions/Topic
Module/Topic
Inheritance
Chapter
9
Events and Submissions/Topic
Tutorial assessment: Part 4 - due in week 6 tutorial class
Programming Assignment 1 Due: Week 6 Friday (23 Aug 2024) 5:00 pm AEST
Module/Topic
Polymorphism and Interfaces
Chapter
10
Events and Submissions/Topic
Tutorial assessment: Part 5 - due in week 7 tutorial class
Module/Topic
Introduction to JavaFX GUI and Event-Driven Programming
Chapter
12 and online resources
Events and Submissions/Topic
Tutorial assessment: Part 6 - due in week 8 tutorial class
Module/Topic
Generic Collections
Chapter
16
Events and Submissions/Topic
Tutorial assessment: Part 7 - due in week 9 tutorial class
Programming Assignment 2: Phase 1 (GUI) due Tuesday 9:00am (AEST) (submission of completed assignment due in week 12)
Module/Topic
Exception Handling, Files
Chapter
11 and 15
Events and Submissions/Topic
Tutorial assessment: Part 8 - due in week 10 tutorial class
Module/Topic
Strings, Characters and Regular Expressions
Chapter
14 and online resources
Events and Submissions/Topic
Tutorial assessment: Part 9 - due in week 11 tutorial class
Module/Topic
Introduction to Version Control; Review
Chapter
Online resources.
Events and Submissions/Topic
Tutorial assessment: Part 10 - due in week 12 tutorial class
Programming Assignment 2 Due: Week 12 Friday (4 Oct 2024) 5:00 pm AEST
Module/Topic
Chapter
Events and Submissions/Topic
Module/Topic
Chapter
Events and Submissions/Topic
1 Practical Assessment
Re-attempts are not allowed for the final submission of this assessment item.
This is an individual assignment. In this assignment you will develop and test a software application in which you use procedural concepts (methods, iteration, selection) to achieve the realisation of object behaviour.
Note that:
- A separate phase 1 submission is required early in the development period for this assignment.
- You may be asked to demonstrate your understanding of the assignment to the unit coordinator before marks can be awarded.
Further details are in the Programming Assignment 1 specification document available on the Moodle unit website.
Week 6 Friday (23 Aug 2024) 5:00 pm AEST
Note: Phase 1 is due Monday at 9:00am (AEST) in week 5 (see Moodle for the exact date). The final submission is due Friday of week 6.
Two weeks after submission
- Design and Implementation (and functionality achieved).
- Language Use (Correct use of programming constructs and good programming practices).
- Documentation
- Testing
- Apply procedural concepts (methods, iteration, selection) to the realisation of object behaviour
2 Practical Assessment
Re-attempts are not allowed for this assessment item. (See conditions below.)
This assessment item is to be developed and submitted as part of your weekly tutorial sessions. It consists of a series of 10 practical tutorial submissions where the tutorial/lab work is to be developed and submitted in the tutorial class in weeks 3 – 12 (inclusive). For on campus students this work is due in the weekly tutorial, NOT the due date shown in Moodle. Moodle cannot have multiple due dates to cater for different tutorial times so the date specified in Moodle is to allow for tutorials held at the end of the week or on weekends. For on campus students no marks will be awarded for work submitted outside the tutorial class or for late submissions unless there are special circumstances (approved by the unit coordinator). If you have special circumstances that prevent you from attending a specific class, please contact your tutor and unit coordinator as soon as you are aware of an issue.
On-campus students
- This assessment task must be developed and submitted in your weekly tutorial as and when you are directed to do so by your tutor.
- Marks may be deducted if your tutor is not satisfied with your progress or understanding of the work. Marks are not only awarded for the sample of work submitted during the class. Satisfactory participation in all tutorial class activities is also required to be awarded marks for this assessment item.
Online students
- Submit the sample of your weekly work requested by the unit coordinator by the due date shown on the unit website for the corresponding week. Late submissions will be awarded 0 marks (unless you have been given approval for an alternative late submission due to special circumstances).
- The unit coordinator is your tutor and may make arrangements to discuss aspects of the weekly work with you before marks can be awarded.
This task commences with an "in-class" submission of work in week 3 and continues with "in-class" weekly submissions until the end of week 12. There is a total of 10 weekly submissions. On-campus students must complete and submit the scheduled work in their weekly tutorial.
The marks will be returned to you within a week after the date of submission.
Practical questions in the weekly tutorial will be used to assess your understanding of the topics covered in that week.
To be awarded marks, on campus students are required to participate in all activities in the tutorial and submit the sample of work requested when instructed to do so during the class. The tutor will monitor student progress in class.
To be awarded marks, online students are required to submit their sample of work (i.e. answers to the questions specified by the unit coordinator) by the due date. Online students should contact the unit coordinator if they have any questions about the weekly work and may also be asked to make arrangements to discuss their work before marks can be awarded.
Note that although your are only required to submit answers to selected tutorial questions as part of this assessment item, all the tutorial exercises should be attempted each week. They are all important for your learning and understanding, not only those questions selected for submission.
Each week's work is worth 1 mark. Total for this assessment item is 10%.
- Apply procedural concepts (methods, iteration, selection) to the realisation of object behaviour
- Apply the fundamental practices of defensive programming (encapsulation, testing, input validation), documentation and version control to software development
- Develop GUI based applications that employ inheritance, interfaces, polymorphism, exceptions, lambdas and sequential file processing
- Implement standard algorithms such as searching, sorting, and sequential processing for arrays and generic collections of objects
3 Practical Assessment
Re-attempts are not allowed for the final submission of this assessment item.
This is an individual assignment. In this assignment you will use the key constructs and concepts introduced in weeks 1- 10 to develop and test a software application that employs a Graphical User Interface (GUI) and uses inheritance, interfaces, polymorphism, exceptions, generic collections and sequential file processing.
Note that:
- A separate phase 1 submission is required early in the development period for this assignment.
- You may be asked to demonstrate your understanding of the assignment to the unit coordinator before marks can be awarded.
Further details are in the detailed Programming Assignment 2 specification available on the Moodle unit website.
Week 12 Friday (4 Oct 2024) 5:00 pm AEST
Note: Phase 1 is due on Tuesday of week 9 at 9:00am (AEST) (See Moodle for the exact date). The final submission is due on Friday of week 12.
Two weeks after submission
- Design and Implementation (and functionality achieved).
- Language Use (including correct application of classes, inheritance, polymorphism, exception handling and good programming practices).
- Documentation
- Testing
- Apply the fundamental practices of defensive programming (encapsulation, testing, input validation), documentation and version control to software development
- Develop GUI based applications that employ inheritance, interfaces, polymorphism, exceptions, lambdas and sequential file processing
- Implement standard algorithms such as searching, sorting, and sequential processing for arrays and generic collections of objects
Examination
Calculator - non-programmable, no text retrieval, silent only
As a CQUniversity student you are expected to act honestly in all aspects of your academic work.
Any assessable work undertaken or submitted for review or assessment must be your own work. Assessable work is any type of work you do to meet the assessment requirements in the unit, including draft work submitted for review and feedback and final work to be assessed.
When you use the ideas, words or data of others in your assessment, you must thoroughly and clearly acknowledge the source of this information by using the correct referencing style for your unit. Using others’ work without proper acknowledgement may be considered a form of intellectual dishonesty.
Participating honestly, respectfully, responsibly, and fairly in your university study ensures the CQUniversity qualification you earn will be valued as a true indication of your individual academic achievement and will continue to receive the respect and recognition it deserves.
As a student, you are responsible for reading and following CQUniversity’s policies, including the Student Academic Integrity Policy and Procedure. This policy sets out CQUniversity’s expectations of you to act with integrity, examples of academic integrity breaches to avoid, the processes used to address alleged breaches of academic integrity, and potential penalties.
What is a breach of academic integrity?
A breach of academic integrity includes but is not limited to plagiarism, self-plagiarism, collusion, cheating, contract cheating, and academic misconduct. The Student Academic Integrity Policy and Procedure defines what these terms mean and gives examples.
Why is academic integrity important?
A breach of academic integrity may result in one or more penalties, including suspension or even expulsion from the University. It can also have negative implications for student visas and future enrolment at CQUniversity or elsewhere. Students who engage in contract cheating also risk being blackmailed by contract cheating services.
Where can I get assistance?
For academic advice and guidance, the Academic Learning Centre (ALC) can support you in becoming confident in completing assessments with integrity and of high standard.
What can you do to act with integrity?
