Hi all,

The course will now be in an archive state. We will not be checking the forum anymore as a result. If you have any questions that would usually go on the forum, please email the class account instead: cs2511@cse.unsw.edu.au

A reminder the feedback form is still open if you would like to fill it in: COMP2511 25T3 Student Feedback

Hi all,

Assignment-ii marks have been released, you can find your marks on the course website here: ️📜 Grades | COMP2511 (25T3).

You can find your feedback on the branch feedback. If you do not have feedback, please email cs2511@cse.unsw.edu.au. If you have questions about your marking, please email your marker first, then contact the course if your question is not resolved.

Your pre_exam_mark has been released. This is the sum of all the assessments except for the exam.

Reminder that we are still looking for course feedback: COMP2511 25T3 Student Feedback

Hi all, we are looking for extra post-exam feedback similar to my experience. This includes all aspects of the course including the exam. You can submit anonymously here COMP2511 25T3 Student Feedback.

This form will be open until mid Week 14.

Edit: We have created this feedback medium as MyExperience does not allow you to comment on things post Week 10-11. We will also be reading MyExperience alongside with your feedback here!

The automarking results have been released. You can find it on the automark-results branch in your assignment-ii GitLab repository.

There will be 2 files, automark.csv and logs.md

automark.csv will contain the list of test IDs and if you failed or passed.

logs.md will list the test IDs, their short description and contains a short amount of logging to why you failed or if you passed.

Total automark mark

You can find your total automark on give or alternatively on the course website: ️📜 Grades | COMP2511 (25T3)

The fields are:

• ass2_automark_2a: Your automark for task 2 option 1 (after a penalty if it exists)
• ass2_automark_2b: Your automark for task 2 option 2(after a penalty if it exists)
• ass2_automark_2a_penalty: Your automark penalty
• ass2_automark_2b_penalty: Your automark penalty
• ass2_late_penalty_days: Your late penalty with your extensions factored in.

Rerun Penalty

The rerun penalty will be calculated per task you are requesting a re-run for.

For example, you are applying for a re-run of Task 2a), the 20% penalty will only apply for that task

How to apply for a rerun

If you are unsure why it is not compiling, you can make a private post on Discourse, and a staff member will look at it.

You can find the instructions on how to submit a re-run request in the form: https://forms.gle/JgyZbsZYT8FkvN6W7.

Hi all,

I have added all the special consideration average marks. Please check your marks on the course website and email cs2511@cse.unsw.edu.au if there are any issues.

Hi all,

We have released initial compilation results with our automarker. This is to give you ample time to fix your codebase and submit a re-run request if you have failed it. (more information below.)

The compilation.md file will tell you if your project has compiled. The file will showcase some information to why your project failed to compile. You can validate and determine why your submission did not compile by following 6.3 Dryrun in the spec.

You can find the compilation.md file in the compilation branch in your GitLab repository. It should be the only file in the branch.

Rerun Penalty

The rerun penalty will be calculated per task you are requesting a re-run for.

For example, you are applying for a re-run of Task 2a), the 20% penalty will only apply for that task

How to apply for a rerun

If you are unsure why it is not compiling, you can make a private post on Discourse, and a staff member will look at it.

You can find the instructions on how to submit a re-run request in the form: https://forms.gle/JgyZbsZYT8FkvN6W7.

Hi all, please be aware we have added a new setting into .vscode/settings.json which enables VSCode to auto-save files after 2 seconds of no edits.

If you wish to remove it, please delete the lines in the .vscode/settings.json file in exam-master.

"files.autoSave": "afterDelay",
"files.autoSaveDelay": 2000

If you are unsure, please ask an invigilator how to do it.

Another remind to tell your invigilator if you encounter any unexpected issues. If they do not address it, please go to the Ainsworth Lvl 3 help desk after the exam and let the Course Admins know.

Best of luck today!!!

Hi all,

The exam is Tomorrow (Friday). Here is some information you should read and know before hand.

It is highly recommended to know your exam time and location well before the exam day.

Afternoon exams require you to be corralled which means you must be at uni earlier then your exam time and at a specific location.

Extra Exam Reminders

Take care of yourself!

Please make sure you are taking care of yourself prior to your exam.

Remember to eat well and sleep well. If you are feeling unwell, please do not attempt the exam and apply for Special Consideration.

Exam Environment Reminder

Here is an exam environment demostration if you need a refresher on how to do things in the exam.

Finally

Other than that, some final words from us - exams are a stressful time for everyone, but you all have prepared for an entire term simply by doing the labs and assignments. You have the understanding and knowledge to complete the exam - keep calm during the exam, draw on that experience and focus on getting that across to the marker in your responses.

If there are any problems on the day, email cs2511@cse.unsw.edu.au as soon as it crops up - we will be monitoring it before, during and after the exam times. We will also have members of the admin team present at the help desk tomorrow, so feel free to go there and ask for help!

Best of luck, we’re sure you’ll do amazingly!

COMP2511 Course Team

Hi all,

We have posted a new schedule for week 11 help sessions. There are quite a few leading up to the exam, please take advantage of it and join early.

You can find the timetable here: 🧑‍🏫 Help Sessions | COMP2511 (25T3) (near the bottom)

There will strictly be no lab marking.

You can also find the lecture recording here: Exam Revision Lecture Recording

Hi all, you can find the exam revision lecture link here: 🎓 Lectures | COMP2511 (25T3)

A revision lecture will be held in-person at 11am at Old Main Building G31 (K-K15-G31) and will run for approximately 2 hours. It will be recorded and will be shared soon after.

There will be no help sessions this Monday. We aim to hold more help sessions everyday until the exam starting from Tuesday.

Revision Lecture Week 11 Monday 11am (24th November)

Course staff will be running a revision lecture this coming Monday 11am at Old Main Building G31 (K-K15-G31) and will run for approximately 2 hours.

The revision lecture will cover how to complete questions found in the sample-exam and revision-exercises.

It is a live event with a recording release shortly after.

Revision Exercises and Sample Exam repository

Two repositories have been created for you. You can find links to them here: 🧪 Labs | COMP2511 (25T3)

The sample-exam repository contains the exact same questions as the in-person W10 sample exam. The solutions are linked in the repository as well.

Revision-exercises are a compilation of exercises you can use to help study for the final exam. They are exam style questions.

Neither resources are representative of the difficulty of the final exam. For more information about the exam, see: 📝 Exam Information | COMP2511 (25T3)

Hey all! We’ve got one more week left in term, and a few quick announcements to cap off this term:

Assignment II

We’re almost at the end of assignment II - make sure to complete both parts of assignment II!

Please note that submission for part 1 is via Gitlab and part 2 is via Moodle. For part 2, submission file type is strictly a single file PDF submission with all your diagrams.

As a quick reminder, the assignment is due by next Wednesday at 3pm. No submissions will be accepted greater than 5 days after the assignment due date. Please see the spec for example penalties for late submissions.

myExperience

The myExperience feedback survey is now out! Please complete the questionnaire whenever you can - we read every bit of feedback we get every term and it directly leads to changes in how we run the course. Your feedback will be a critical source of information on how student’s enjoyed/benefited from the new content, and how we can better streamline the delivery of this content for future terms, so please fill in the survey with plenty of detail!

I’m also sure your tutors would massively appreciate any feedback you’ve got, regardless of if it’s nice comments or constructive criticism!

Sample Exam

As mentioned, we have a sample exam running this week in the in-person labs only. Online students are free to join any other lab for the sample exam. The sample exam and the actual exam are both held in a different environment to the default CSE environment, so using this opportunity to play around with it and see what resources are provided is a great idea! We’ll release the full sample exam paper for you to revise with in your own time at the end of the week. Do note that the sample exam paper has the same format and style of questions as the main exam, but the number and difficulty of questions may differ.

A reminder that by the end of Week 10, you should have all your labs marked.

With that, enjoy your final week of term!

Hi all, there has been some issues with the lecture recording on echo360.

We have uploaded the Teams recording on to the course website. You can find them here: 🎓 Lectures | COMP2511 (25T3)

Hi all,

We are aware of a screen sharing/recording issue on echo360 for the Week 9 Monday lecture.

I have uploaded the Teams recording seperately. You can find the link on the course website under 🎓 Lectures | COMP2511 (25T3)

Hi all,

We have recently amended an autotest (B-2-7) in assignment-i due to an issue with its correctness. We have since rerun the automarker with the correct test, and uploaded the updated results to the automark-results branch to your assignment-i repository.

If you had previously passed the test and failed the amended test, we will still grant you the marks for the test (i.e.: your mark will not go down). If you had previously failed the test, and now pass the amended test (~8% of students), your mark will be automatically updated in our records, so there is no action required for you.

If you have any concerns or questions about your own automarking for this test, please create a private forum post, do not respond to this post.

Hey all,

We’re slowly approaching the end of term! Just two more weeks to go! Here are the announcements for this week.

Assignment II

A reminder that Assignment II is due Week 10 Wednesday 3pm. The late penalty for the submission is the standard UNSW late penalty of a 5% per day reduction of the on-time assignment mark. This is calculated per-hour to the next hour. No submissions will be accepted greater than 5 days after the assignment due date. Please see the spec for example penalties for late submissions.

There is, as always, plenty of help sessions and forum support this week and next week, so feel free to join a help session or post a question on the forum for any help you need!

Sample Exam

In the week 10 lab, there will be a sample exam loaded on all lab computers so that you can gain some experience with the exam environment. This isn’t worth any marks, but it’s a nice way to become familiar with the system so you don’t get surprised on exam day. There will also be some questions that mimic the type of questions you might see (number and difficulty of questions may differ).

The environment is only accessible on CSE computers, so students in online tutorials will want to attend any one of the in person labs to see the environment. You will also gain access to the actual paper itself via Gitlab soon after Week 10.

Assignment I

All assignment I marks have now been released! We also have completed all assignment I reruns - if your automark hasn’t updated after the rerun, either your rerun mark would’ve been lower than your old mark so we took the old mark, or your rerun wasn’t accepted.

And with that, we’ll leave you to it - all the best with assignment 2!

Hi all,

Assingment-i marks have been released. You can view them on the course website or on give.

If you have a question about your marking, please email your marker first. If you are unable to reach a conclusion, please forward the email to cs2511@cse.unsw.edu.au.

I will process the last rerun requests later today.

Hi all, a reminder is no lecture today (Monday).

Hey all! Hopefully everyone’s well underway with assignment II! Here are this week’s announcements

Lecture Cancelled

The lecture for this coming Monday (3rd November) has been cancelled as Jesse is required at a conference.

Assignment I Marks

Assignment I marking is nearly done, and we’ll be releasing the marks by the end of next week. As you already know, automarks have been released for a couple of days now under an automarking branch, with logs you can review. On top of that, manual feedback should also be released by your tutors soon as well - unless your tutor indicates they gave feedback differently, it should be present on Gitlab either as comments on a merge request in your repo, an issue on your repo or on a new branch. Please note that all submissions are subject to plagiarism checks which may change your mark.

As announced before, rerun requests close Week 8 Thursday 10am. If your automarking didn’t compile due to your code, or a small issue caused a large loss of marks, you may request a rerun, including a patch with less than 20 lines changed (this includes both additions and deletions, though an addition and deletion on the same line will count as 1 changed line). Note that we don’t count changes to your tests, as well as imports, to that 20 line limit. The instructions for submitting a rerun are here.

When manual marking releases, if you have questions about your manual marking, email your marker (who should be the person who provided your feedback) for clarifications.

And that’s about it for assignment I - regardless of your marks, we hope you have gained something from this assignment and have a better understanding of design principles and how to apply them!

Lab08

Lab08 has been released on the course website. No GitLab repository will be created.

Please be aware for this lab, you must submit your work on Moodle and before the deadline.

Lab09

The specification for Lab09 will also be release on the course website next week.

Please note that lab09 is an attendance lab. You must attend the lab and participate in order to receive marks.

Assignment II

A quick reminder that assignment II has a dryrun you can (and probably should) be using to ensure that your code will run with our tests. I also wanted to highlight that Part 2 of the assignment is submitted on Moodle, similar to lab08.

We also still have the forums and help sessions available for you to make full use of in getting help with things you’re unsure of!

Other than that, we hope you enjoy the new system architecture content!

Hey Everyone,

Some of you might have noticed the Java testing extension in VSCode has broken - this is due to an update of the RedHat Java extension yesterday. You should still be able to run your tests via command line (gradle test or 2511 gradle test on cse), but if you want to be able to run your tests from VSCode again, you can downgrade to a previous version by doing the following:

First, find the extension in your list, and click the settings icon - there should be an entry “Install Specific Version”

This should create a popup where you can select which version of the extension you would like to install - since 1.47 is broken, you can select 1.46

After installing, restart your extensions with this button

After Java restarts, you should see your tests being runnable from VSCode again

If this still doesn’t fix the issue, please make a new forum post and we will get to you ASAP. Happy coding : )

Hi all,

The lecture for this coming Monday (3rd November) has been cancelled as Jesse is required at a conference.

We will communicate more if anything changes.

Hi all,

The automarking results have been released. You can find it on the automark-results branch in your assignment-i GitLab repository.

There will be 2 files, automark.csv and logs.md

automark.csv will contain the list of test IDs and if you failed or passed.

logs.md will list the test IDs, their short description and contains a short amount of logging to why you failed or if you passed.

Total automark mark

You can find your total automark on give or alternatively on the course website: ️📜 Grades | COMP2511 (25T3)

ass1_automark will include the automark penalty. ass1_automark_penalty is a % (i.e., 0.2/1 means a 20% penalty has been applied to calculate ass1_automark)

Re-run requests (Failed compilation)

You can submit a re-run request at a 20% penalty off your automark if your project has failed to compile. To determine why it has failed to compile, you should run the dryrun by following instructions 7.1 Dryrun in the spec.

If you are unsure why it is not compiling, you can make a private post on Discourse, and a staff member will look at it.

You can find the instructions on how to submit a re-run request in the form: https://forms.gle/2QbGspMioaKAont16.

Re-run requests (Short 20 line fix)

You can request a re-run with a maximum of 20 lines changed in your merge request if small issue caused a large loss of marks. Note that we don’t count changes to your tests, as well as imports to that 20 line limit.

You can find the instructions on how to submit a re-run request in the form: https://forms.gle/2QbGspMioaKAont16.

Questions

For any other questions, please create a private post on the forum and we will address it within a few days.

Hi all,

Lab08

Lab08 has been released on the course website, 🧪 Lab 08 | COMP2511 (25T3). No GitLab repository will be created.

Please be aware for this lab, you must submit your work on Moodle and before the deadline.

Lab09

The specification for Lab09 will also be release on the course website next week.

Please note that lab09 is an attendence lab. You must attend the lab and participate in order to recieve marks.

Hey all,

Welcome back to term! Hopefully you all had a relaxing and/or productive flex week! Not too many announcements this week:

Software Architecture Resources

As we move into the second half of the course about Software Architecture, the course has created a bunch of extra resources on topics such as:

• Mermaid Sequence Diagrams Docs
• C4 Diagrams
• Sequence Diagrams
• Architecture Dictionary

These resources will be really helpful as you work through assignment II and prepare for the final exam, so make sure to check them out!

Assignment II

Now that we’re exiting flex week and entering week 7, it’s a good time for everyone to begin reading over the spec and begin coding for part 1 of the assignment! To help with better understanding the assignment, we will be having a discussion of the assignment in a Week 7 lecture. Please come along with any questions you’d like to get answered!

I’ll also quickly shout out that assignment II part 1 has a dryrun similar to assignment I - the spec has instructions on how to run it, but the instructions will be similar to assignment I. However, there are differences in what the dryruns test, outlined in the spec.

Finally, as always, we have tutors on the forums and a ton of help sessions over the coming 4 weeks! The spec also has an FAQ with a list of approved assumptions, which you can use to quickly check if your question has already been answered! As the term goes on, we’ll keep this up to date as questions are asked on the forum.

And with that, we’re done with announcements! We’ll see you back in classes starting from Monday as finalise design patterns and move into software architecture

Hi all,

We have released initial compilation results with our automarker. This is to give you ample time to fix your codebase and submit a re-run request if you have failed it. (more information below.)

The compilation.md file will tell you if your project has compiled. The file will showcase some information to why your project failed to compile. You can validate and determine why your submission did not compile by following 7.1 Dryrun in the spec.

You can find the compilation.md file in the compilation branch in your GitLab repository. It should be the only file in the branch.

How to apply for a rerun

You can submit a re-run request at a 20% penalty off your automark if your project has failed to compile. To determine why it has failed to compile, you should run the dryrun by following instructions 7.1 Dryrun in the spec.

If you are unsure why it is not compiling, you can make a private post on Discourse, and a staff member will look at it.

You can find the instructions on how to submit a re-run request in the form: https://forms.gle/2QbGspMioaKAont16.

Heya!

We’re at the halfway point of the term! Next week is flex week, so make good use of the break to rest up, catch up on any course content you’re behind on (for COMP2511 or otherwise) and take it easy

Lecture Recordings on Echo360, not Teams

You can access all lecture recordings through Echo360. The Teams recordings are only used as backups and are not available to students, so please do not request access to them.

To find recordings, Go to the Moodle Course page and click “Lecture Recordings” for Echo360 recordings.

Week 4, Monday was a public holiday, and that lecture is available at: COMP2511 25T3 Week 4 Monday Lecture (Public Holiday)

Assignment I

The heartiest of congratulations on completing assignment I! Regardless of how easy or difficult you found it, how long it took you or how you feel you went, you all did amazingly in getting it done and demonstrating your understanding of OO principles!

For anyone working this weekend and into flex week on assignment I, please note that there is a hard cutoff for accepting submissions one week after the original due date i.e. Week 6 Wednesday 3pm. This is only for ELP and special consideration cases

Our spectacular tutor team will be marking your assignments over the next couple of weeks - we should hopefully have marking finalised sometime in late week 7/early week 8. In the meantime…

Assignment II

The assignment II spec has been released on the course website, and repos will release over the weekend! We recommend taking a look at the spec and the existing codebase sometime over this week to begin getting adjusted to a novel codebase. If you’re feeling especially adventurous, you can even begin some of the tasks as well! Developing a good design for each task takes time as I’m sure everyone is familiar with after assignment I, and this fact is especially true when working on new codebases. Even small bits and pieces of work will help save you some strife later in the term.

Help during Flex Week

Even though it’s flex week, we still have a few help sessions scheduled, and the forum will still be regularly maintained, so if you have any questions at all, feel free to drop into a help sesh or post a question on the forum!

And with that, enjoy your well earned break, and we’ll see your refreshed faces in week 7

Hi all,

The assignment-i spec and repositories have been released since last night. You can find the links on the course website here: 💻 Assignments | COMP2511 (25T3)

If there are any issues, please make a forum post in the Assignment-i category.

Announcement category for the course. Important weekly information will be posted here. We recommend reading the announcements as soon as possible.