Requirements to Pass this Unit

To pass this unit you must:

• Pass the weekly contribution to the workshop hurdle.
• Attempt both assessments.
• Submit both the interm and final report.
• Take part in the exam.
• Achieve a total mark equal to or greater than 50%

Late Assessment Submission Penalty 

Unless a Special Consideration request has been submitted and approved, a 5% penalty (of the total possible mark) will be applied each day a written assessment is not submitted, up until the 7^th day (including weekends). After the 7^th day, a grade of '0' will be awarded even if the assessment is submitted. Submission time for all written assessments is set at 11:55 pm. A 1-hour grace period is provided to students who experience a technical concern. 

For missing any time-sensitive assessments, such as exams and practical assessments, students must submit a request for  Special Consideration. This has to be done within five working days of the due date using the application form on AskMQ. It's important to note that submitting a Special Consideration request does not guarantee an additional or alternative assessment. It's crucial to continue working on and completing assessments promptly.

Assessments where Late Submissions will be accepted 

• Assignment 1 – YES, Standard Late Penalty applies 
• Assignment 2 – YES, Standard Late Penalty applies 
• Working in teams on a substantial software engineering project:
  • Weekly contribution – NO, unless Special Consideration is granted
  • Interim report – YES, Standard Late Penalty applies 
  • Final report – YES, Standard Late Penalty applies 

Weekly Workshops (includes a hurdle task)

There are weekly workshops where you will be working on the assessment task Working in teams on a substantial software engineering project. You will need to conscientiously attend the workshops and engage with the work with your tutor and fellow students. Contribution to the workshop and the group project is a hurdle task meaning that you cannot complete COMP1050 satisfactorily without completing the hurdle task satisfactorily.  We expect you to be involved every week, but we know, of course, that you might be ill or something once or twice.  You need to be present and actively engaged in at least eight of the twelve sessions to be eligible to meet the hurdle, and if illness or anything else leads you to miss more than four sessions you should speak to the convenor.  

Contribution is assessed as follows:

• Weekly contribution to the workshop: This entails participation and completion of a weekly taks. It contributes for (10%) to your final grade. Your best 10 out of 12 weekly tasks will be used for your grade. IMPORTANT. This is a hurdle. If you complete fewer than 8 out of 12 weekly tasks, you will not pass the hurdle requirement. However, if you made a genuine effort on four weekly tasks but still failed to pass the hurdle, you have the option to take a viva examination in the week 13. The viva will cover the exercises completed during the workshops and the software engineering project.
• Interim report: Due in week 6. It contributes for (10%) to your final grade. It describes the first weeks of the software engineering project. This is a collaborative document.
• Final report: Due in week 12. It contributes for (20%) to your final grade. It builds on the interim report and describes the entire software engineering project. This is a collaborative document.

The "0 hours" estimated time required for that task arises because the task is completed during your scheduled workshop class (and class hours are recorded separately). 

Lectures

This course includes 2-hour weekly lectures. Attendance at these lectures is highly recommended as they introduce the concepts that will be used in the workshops and will be covered in the assessments for Assignment 1, Assignment 2 and the final exam.

Assignments

Assignments will play a crucial role in evaluating student understanding. They will be based on the lecture material, workshop activities, and weekly tutorial material and will require students to integrate what they have learned, think critically and creatively.

Exam

A written exam (held withing the university examination period) is designed to test your understanding of the course content and your application of the concepts to a number of scenarios or problem statements.

Unit Resources

Although there is no required textbook, we suggest that students read:

• David Farley, Modern Software Engineering: Doing What Works to Build Better Software Faster, Addison-Wesley Professional, 2021.

This is a valuable resource for understanding the day-to-day tasks of software engineers and is available in the library in both online and ebook formats. The workshop exercises and accompanying software engineering project are outlined in the workshop manual. Additionally, lecture notes and recordings will be made available after each lecture.

Tentative, and subject to adjustments.

The workshops and the software project.

While the software engineering content is the same as, the order in which topics are covered, the exercises, and the nature of the project changed.

Lectures

While the topics of the lectures remain the same, the order in which they are covered, and the application examples will change.

Repeating Students

Students who retake this unit are expected to fully participate in all learning activities, just as first-time students do. Previous participation in the unit does not exempt you from any requirements. Completing homework or assessments in a previous iteration of the unit will not exempt you from completing the assignments again this time around.