Note that each student is expected to complete satisfactorily all four 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 project (part 2) in software engineering, is not like many (probably any) of the units you have studied before.  You need to attend all classes and be actively involved.  You need to work independently, and commit the required time and discipline.  You need to plan and manage carefully your own individual tasks.  And you need to take all this seriously and complete it in a business like and conscientious manner.

It goes without saying, but I'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, but the unit is about you and your participation is essential.

Late Submissions

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 the piece of work.  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.)

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.  All written work must be properly referenced and conform to standard stylistic conventions.

A thesis is an especially significant formal document that represents both academic research, and in this case a substantial individual software engineering project.  It takes a very significant amount of time and multiple drafts to properly prepare such a document.

There is only one lecture per week in this unit as the bulk of the work is on preparation for your thesis.

The lecture is compulsory, and is currently scheduled for Wednesday at 9am.  It is very important that you attend as the special nature of project finalisation and final thesis writing requires special skills, study and guidance.

The thesis is now a hurdle requirement and the lectures are compulsory.  These changes are in response to difficulties that some students had in finalising their thesis work in a timely and satisfactory manner in previous years.   More about this will be explained in the first lecture.

From now until 2022 (inclusive), most students enrolling in COMP4093 will enrol concurrently in ENGG4093.  This is so that students can complete "double sized" project units (20 credit points) as required in the programs that students originally entered.  This will be further explained in the first lecture.