| Unit convenor and teaching staff |
Unit convenor and teaching staff
Convener and lecturer
Ansgar Fehnker
Lecturer
Michael Lay-Kujiraoka
Senior Teaching Assistant
Samantha Kuhn
Senior Sessional Assistant
Aaron Chakerian
|
|---|---|
| Credit points |
Credit points
10
|
| Prerequisites |
Prerequisites
|
| Corequisites |
Corequisites
|
| Co-badged status |
Co-badged status
|
| Unit description |
Unit description
This unit is an introductory computer science unit, providing a practical introduction to basic computing and programming concepts. Students gain an understanding of, and practical experience in, computer programming; practical experience in implementing informal prose descriptions of problem solutions using an high-level language; an understanding of, and practical experience in, designing, coding, testing and debugging simple algorithms; and an understanding of the principle of incremental development. Other topics include the concept of program correctness; the differences between high-level languages, assembly languages and machine languages; the role played by compilers; and the execution of programs by computer hardware. |
Information about important academic dates including deadlines for withdrawing from units are available at https://www.mq.edu.au/study/calendar-of-dates
On successful completion of this unit, you will be able to:
You will have to attend a live coding exercise demonstrating basic programming skills. It will carry 30 out of 100 marks. You will be asked to use the IDE to create, modify, change, extend, test, and debug a basic program. This is an in-person invigilated assessment, and the use of AI tools is not permitted. The assessment will take place during the workshops in week 6.
Please check iLearn for the exact dates, as dates may change if circumstances require it.
Before the Programming Skills Demonstration, there will be an online Diagnostic Test. It's highly recommended that you complete this formative assessment. If your Diagnostic Test mark is higher than your mark for the invigilated Programming Skills Demonstration, your final mark will be calculated using 10% of the Diagnostic Test mark and 90% of the mark for the Programming Skills Demonstration.
There is one summative programming exam worth 30 out of 100 marks, assessing your understanding and application of the programming concepts covered in the unit. This is an in-person invigilated assessment, and the use of AI tools is not permitted. The assessment will take place during the workshop in week 11. This is an in-person invigilated assessment, and the use of AI tools is not permitted.
Before the Programming Exam, there will be an online Practice Exam. It's highly recommended that you complete this formative assessment. If your Practice Exam mark is higher than your invigilated Programming Exam, your final mark will be calculated using 10% of the Practice Exam mark and 90% of the Programming Exam mark.
Each week during your scheduled SGTA sessions, a teaching assistant will guide you through exercises related to the lecture topics. In addition to these exercises, your SGTA will also support you with your Handover Project. You are encouraged to submit your work-in-progress regularly to receive formative feedback. In Week 7, you are expected to submit a program for the formative Mid-Session Checkpoint. We will provide written formative feedback on your project’s progress.
In Week 12, you will participate in an invigilated in-class Handover Review session. You will have to submit your Handover Project before this activity. The Handover Review is a closed-book, invigilated in-class activity. During this activity, you will complete a self-assessment of your submission against the minimum requirements. This self-assessment is intended to demonstrate your familiarity with the submitted Handover Project. It is an invigilated in-person assessment that will take place during your regular workshop hours.
Your grade for this assessment will be based on two components:
Together, these components will contribute 40 marks out of 100 for the course.
If you fail to achieve a passing mark in the handover, you will have the opportunity to complete a viva (oral examination), covering the same topics. Unless a special consideration applies, a cap of 20 marks will be applied to the mark of the viva.
The use of AI during the Handover Review or second‑chance vivas is not permitted. The use of AI tools to create the original submission is not explicitly prohibited. Students are, however, expected to be able to explain and answer questions on all aspects of their submission, including any parts that may have been generated with assistance.
The description of the project will be released before 27 April 2026.
It's highly recommended that you make a submission for the Week 7 formative Mid-session Checkpoint. If your mark for the Mid-Session Checkpoint is higher than the mark for the Handover Project and Review, your final mark will be calculated using 10% of the mark for the Mid-Session Checkpoint and 90% of the mark for the Handover Project and Review.
In this unit, all assessments are in-person and in class. There are no separate submissions or submission deadlines.
As such, the following applies with respect to late submissions:
Short extensions are not offered for any assessments in this unit.
The programming project must be submitted before or at the start of your in-class handover. You will not be permitted to participate in the handover review unless your program has been submitted beforehand.
All assessments in this unit are conducted in person during scheduled class sessions. There are no standalone take‑home submissions and no separate submission deadlines. Accordingly, late submission penalties do not apply.
If you need extra time for an assessment due to serious or unexpected circumstances, you can apply for Special Consideration. Please keep the following in mind:
| Name | Weighting | Hurdle | Due | Groupwork/Individual | Short Extension | AI Approach |
|---|---|---|---|---|---|---|
| Project Handover and Review | 40% | No | In week 12, during the registered SGTA | Individual | No | Observed |
| Programming Exam | 30% | No | In week 11, during the registered SGTA | Individual | No | Observed |
| Programming Skills Demonstration | 30% | No | In week 6, during the registered SGTA | Individual | No | Observed |
Assessment Type 1: Reflection task
Indicative Time on Task 2: 28 hours
Due: In week 12, during the registered SGTA
Weighting: 40%
Groupwork/Individual: Individual
Short extension 3: No
AI Approach: Observed
Formative programming tasks during the session will contribute to a final programming project, submitted during an invigilated in-class handover. Students must demonstrate their understanding of and familiarity with the project. Both the quality of the submitted program and the student's performance during the handover will be assessed. Students who do not pass the handover will have the opportunity to complete a viva, covering the same topics as the handover, for a passing mark.
Assessment Type 1: Examination
Indicative Time on Task 2: 24 hours
Due: In week 11, during the registered SGTA
Weighting: 30%
Groupwork/Individual: Individual
Short extension 3: No
AI Approach: Observed
This is a summative assessment of the unit's content. Students will have an opportunity to retake the assessment to improve their marks.
Assessment Type 1: Experiential task
Indicative Time on Task 2: 20 hours
Due: In week 6, during the registered SGTA
Weighting: 30%
Groupwork/Individual: Individual
Short extension 3: No
AI Approach: Observed
Weekly tasks during the SGTAs prepare students for an in-lab exercise where they must demonstrate programming skills, such as using standard software engineering tools to create, modify, debug, test, and manage programs. Students will have an opportunity to retake this task to improve their mark.
1 If you need help with your assignment, please contact:
2 Indicative time-on-task is an estimate of the time required for completion of the assessment task and is subject to individual variation.
3 An automatic short extension is available for some assessments. Apply through the Service Connect Portal.
Note that lectures commence in week 1. Workshops scheduled on Monday after the lecture and from Tuesday to Friday will also commence in week 1. Workshops scheduled before the lecture on Monday will commence in week 2.
Each week you should attend
For details of days, times and rooms, consult the timetables webpage.
You should have selected a practical class during enrolment. You should attend the workshop in which you are enrolled. You won't always get the class of your choice. Check availabilities via eStudent regularly. If ALL workshops are full, only then, contact the convenor.
Textbook:
Technology
The unit makes use of forums hosted within iLearn. Please post questions there, they are monitored by the unit staff. For personal questions regarding the unit, please contact the super tutors or unit conveners.
Note, that dates and deadlines may change if circumstance requires. Please check iLearn for the latest updates.
|
Week |
Topic |
Assessment Activity |
|
1 |
Getting Started in Processing |
|
|
2 |
Variables and arithmetic |
|
|
3 |
Decisions: Ifs, booleans, and boolean algebra |
|
|
4 |
Iteration: While and for-loops |
Formative Feedback: Diagnostic Test |
|
5 |
Loops and Ifs |
|
|
6 |
Functions |
Summative Assessment: Programming Skills Demonstration |
| - | Two Week Session Break | |
|
7 |
Objects and Classes | Formative Feedback: Mid-project Checkpoint |
|
8 |
Arrays and array algorithms | |
|
9 |
Understanding Data Passing: Value vs. Reference |
|
|
10 |
Program Design and Problem Solving |
Formative Assessment: Practice Exam |
|
11 |
Theory, Physics, and Processing Goodies. |
Summative Programming Exam |
|
12 |
Beyond Processing |
Summative Assessment: Project Handover and Review |
|
13 |
Revision |
Summative Assessment: Project Handover and Review - Vivas |
Macquarie University policies and procedures are accessible from Policy Central (https://policies.mq.edu.au). Students should be aware of the following policies in particular with regard to Learning and Teaching:
Students seeking more policy resources can visit Student Policies (https://students.mq.edu.au/support/study/policies). It is your one-stop-shop for the key policies you need to know about throughout your undergraduate student journey.
To find other policies relating to Teaching and Learning, visit Policy Central (https://policies.mq.edu.au) and use the search tool.
Macquarie University students have a responsibility to be familiar with the Student Code of Conduct: https://students.mq.edu.au/admin/other-resources/student-conduct
Results published on platform other than eStudent, (eg. iLearn, Coursera etc.) or released directly by your Unit Convenor, are not confirmed as they are subject to final approval by the University. Once approved, final results will be sent to your student email address and will be made available in eStudent. For more information visit connect.mq.edu.au or if you are a Global MBA student contact globalmba.support@mq.edu.au
At Macquarie, we believe academic integrity – honesty, respect, trust, responsibility, fairness and courage – is at the core of learning, teaching and research. We recognise that meeting the expectations required to complete your assessments can be challenging. So, we offer you a range of resources and services to help you reach your potential, including free online writing and maths support, academic skills development and wellbeing consultations.
Academic Integrity
Using the work or ideas of another person, whether intentionally or not, and presenting them as your own without clear acknowledgement of the source is called Plagiarism.
Macquarie University promotes awareness of information ethics through its Academic Integrity Policy. This means that:
All breaches of the Academic Integrity Policy are serious and penalties apply. Students should be aware that they may fail an assessment task, a unit or even be excluded from the University for breaching the Academic Integrity Policy.
Assessment Policy
Students should familiarise themselves with their responsibilities under the Assessment Policy, and notably the Final Examination Procedure.
Grade Appeals
A student who has been awarded a final grade for a unit has the right to appeal that grade as outlined in the Assessment Policy. Grade appeals apply to the final mark and the grade a student receives for a unit of study. They do not apply to results received for individual assessment tasks.
Grade appeals must be submitted via ask.mq.edu.au within 15 working days from the published result date for the relevant unit. Before submitting a Grade Appeal, please ensure that you read the Assessment Policy and note valid grounds for appeals.
Students are expected to seek feedback on individual assessment tasks prior to the award of a final grade. Students also have the right to request generic feedback from the teaching staff on their overall performance in the unit, including in a final examination. This can be done at any time in the six-month period starting from the day on which the final grade of the relevant unit is published.
Macquarie University provides a range of support services for students. For details, visit http://students.mq.edu.au/support/
Academic Success provides resources to develop your English language proficiency, academic writing, and communication skills.
The Library provides online and face to face support to help you find and use relevant information resources.
Macquarie University offers a range of Student Support Services including:
Got a question? Ask us via the Service Connect Portal, or contact Service Connect.
For help with University computer systems and technology, visit http://www.mq.edu.au/about_us/offices_and_units/information_technology/help/.
When using the University's IT, you must adhere to the Acceptable Use of IT Resources Policy. The policy applies to all who connect to the MQ network including students.
We value student feedback to be able to improve the way we offer our units continually. As such, we encourage students to provide constructive feedback via student surveys, to the teaching staff directly, or via the FSE Student Experience & Feedback link on the iLearn page.
To encourage early engagement, formative assessment is now available for all three assessments and can help improve your mark. Previously, this was only available for the final exam. Note, special consideration is not available for formative assessment tasks. If you miss the formative assessment, you can achieve full marks in the summative assessment.
Unit information based on version 2026.02 of the Handbook