Assessment Due Times

All submissions in COMP4060 are due by 11:55pm on the date specified. You will be able to submit early drafts and there will be no cap on resubmissions before the assessment due date.

Late Submissions and Special Consideration

As with all software engineering, timely submission is essential.  Late submissions will not be accepted.  If you are seriously affected by unavoidable and unforeseeable circumstances, you should email the unit convenor as early as possible, and certainly before the due date of piece of work to discuss options.  In any case, be sure to submit by the due date whatever work you have available for submission.  If, after application for for Special Consideration as a result of unavoidable disruption to studies, the university deems you to be eligible to complete further work on the assessment item, you may be given an opportunity to add to your submission or you may be given a substitute task.

In order to pass the unit

Note that each student is expected to complete satisfactorily all three components of the assessment.  This is a highly integrated unit and attempts to merely accumulate marks in a component without utilising material from the others would be destined to fail.

This unit, like the workplace you will soon be in, requires active involvement and, like the workplace, you will be being judged throughout the semester.

There will be regular feedback during the semester, so students should have an idea of how they are progressing (and if you don't have a clear idea, be sure to ask!).

But it's really important to realise that this unit, the culminating unit in software engineering linking your degree to the workplace, is not like many (probably any) of the units you have studied before. You need to

• attend all classes and be actively involved.
• work between classes and prepare for the following week's classes.
• plan and manage your own individual tasks carefully, and
• take all components of the unit seriously and engage in a business-like and conscientious manner. Feedback / discussion on items that students have prepared will continue in following workshops to help build / refine / develop / use those submissions for other progressive learning activities that build toward assessment items.

It goes without saying, but we'll say it anyway, that there are no recorded lectures or web-based PowerPoint presentations for you to use if you miss things. The unit has lectures (badged as seminars), but the unit is about you and your participation is essential for success.

Written submissions

Software engineering frequently requires written reports, and such reports need to be, as far as possible, of professional quality.  Students need to strive to present work which is written clearly, with good grammar, correct word usage, correct punctuation and correct spelling.  Wherever required, all written work must be properly referenced and conform to standard stylistic conventions.

"Generative AI - and simmilar tools" are something that can be utelised in this unit to help in the creation / iteration of submissions, but must be declared in the assessment submission (how it was used and how much of the submission has been generated / assisted by such tools). This unit is about personal growth, and deep dives on your personal versions of Advanced Software Engineering - so be sure to read the assessment criteria carefully.

Classes

COMP4060 has been divided up into two separate streams.

• An all-cohort seminar (starting week 1)
• Breakout workshops (starting week 1)

Week 1: When do we meet?

This unit emphasises a dynamic combination of lecture, practical, tutorioal, discussion, laboratory work, group and individual assigned task work, and a high degree of self-learning.  The overall goal is to be a "finishing school" for software engineers, and the unit includes highly technical work as well as deep reflection on the nature of the discipline and its state in Australia and internationally. It is very important to attend your enrolled workshop and the all-cohort seminars each week. Be sure to look at eStudent for available classes and for your class schedule.

Research and Resources

Research "in the library" and other places (outside of scheduled sessions) as to the state of the art in software engineering will be required as the student develops their own understanding in identified areas as part of the assigned task work.

There are no set texts, but a wide range of sources will need to be consulted and reading lists developed.

This unit is different each year because the content is tailored to the individual experiences of each of the students that arise from their particular choices of electives in the software engineering program and any work experience, and it is also tailored to the students' medium term career goals.  The exact nature of the change from year to year depends of course upon the exact nature of the individual experiences and the goals of the enrolled students in each year.

Methods of Communication

Communication with students will be done in person during the weekly meetings. This may include action items, feedback, queries on progress, and any other topics that arise as part fo the weekly discussions. 

We will - where necessary - communicate with you via your university email and through announcements on iLearn. Queries to convenors can either be placed on the iLearn discussion board or sent to the unit convenor via the contact email on iLearn.

Teaching and Learning Activities

Seminars

Delivery of material not previously seen by the students or material which will be presented in a differenct context with regard to graduate capabilities. There may be some review material, but this is minimal.

Workshop

Develop skills based competencies in experimentation with overlap/application to theory and simulation.

Projects

Students plan and execute a combination of group and individual work to execute a project of substance, possibly with real world application. This activity leads to assessments that may be of both a group and individual nature as well as formal reports and a presentation

Class debates (in both seminars and workshops)

This activity is used widely in this unit to engage students and encourage deep learning. At this advanced level, as well as technical material there is a need for students to develop their own internalised understanding of matters such as ethics, the nature of the profession, their approach to professional development, and their career goals. There aren't simple answers, and there is a strong need for detailed student engagement with the issues.

COVID Information

For the latest information on the University’s response to COVID-19, please refer to the Coronavirus infection page on the Macquarie website: https://www.mq.edu.au/about/coronavirus-faqs. Remember to check this page regularly in case the information and requirements change during semester. If there are any changes to this unit in relation to COVID, these will be communicated priarilly via iLearn, but may include direct email communication through you student email.

Special Consideration

The Special Consideration Policy aims to support students who have been impacted by short-term circumstances or events that are serious, unavoidable and significantly disruptive, and which may affect their performance in assessment. If you experience circumstances or events that affect your ability to complete the assessments in this unit on time, please inform the convenor and submit a Special Consideration request through ask.mq.edu.au. More details are in the "General Assessment Information" for specific assessments.

The class runs on Thursday each teaching week of session 1 (except for public holidays - of which there are none impacting COMP4060 in 2026). Below is a tentative schedule for the unit, but a more definite scheudle will be discussed with students based on their self-evaluation against accreditation criteria.

** Please note that this is the initial plan for arranging unit content, but it is subject to change.  Our goal is to best serve student learning and depending on the distribution of Joint Board competencies and SWEBoK coverage already attained by the incoming students material may be rearranged and relative timings reallocated (in consultation with the enrolled students).

Individual projects will cover many areas including CASE tools, process methodologies, testability and formal verification as well as project specific technical material.  The precise combination will vary based on the nature of each individual project.

As noted above, COMP4060 is different every year because it is tailored to the varied experiences of the enrolled students.

As part of this process of a tailored experience for each student, we include a student reflection on their experiences in the unit which includes feedback and suggestions for future offerings.

In saying all of the above, there are two specific changes that have occured for the 2026 offering: 

1. The stated assessments have been changed to fall in line with the three assessment principles outlined by the DVC-A.
2. The timetable arrangements have changed. There are now explicit times scheduled in eStudent for seminars and workshops (rather than what has happened in previous years with block times being booked and cohorts managed internally).

While there are 2 macro-changes to the 2026 offering (details above)... there was a strong preference from previous cohorts on keeping more of the discussion in a face to face mode rather than using online forums to suppliment the discussions. There was also an overwhelmingly positive response to the tailored nature of the unit with the breakout discussion sessions which will remain for this offering as well.

As we've said, COMP4060 is a very different unit from the other kinds of units you will have studied in your software engineering (SE) program.  So, we want to be explicit about the unit's goals.  They are:

1. To fill the gaps in ICT knowledge that can arise from a curriculum for SE including a limited number of required specialist IT units.  Each student has different gaps, as they depend on the students' choices of electives and on their goals for future employment in software engineering (there are many different kinds of software engineers).
2. To provide a culminating experience in which students reflect upon their entire degree and contextualise it with respect to other software engineering degrees, SE curricula, and their own understanding of SE, as well as developing their own near-graduation perspective on SE as a field, on professionalism and on professional practice.

These are the goals that lie behind the learning outcomes.