Hey all! Hope you're enjoying your long weekend! We've got one (shorter) week left in term, and a few big announcements this week as a result:

Assignment Announcements 📢

A massive congratulations for making it to the end of assignment II 🤩. Marking for the assignment is now underway, and marks should release around the end of Week 11.

Assignment III is available for everyone to complete. If you choose to work on it, there's still plenty of support in the form of help sessions and forums. That being said, it is a bonus assignment, meaning if you don't complete it, you don't lose further marks. As such, definitely feel free to prioritise other work if you're feeling a bit swamped at the end of term.

Assignment II Reruns

A couple of announcements have been made regarding assignment II reruns - we are aware there was an issue with the dryrun, so reruns regarding issues which would have been picked up by the dryrun will have no penalty applied but other reruns will have the standard 20% penalty applied to all tasks applied for. We will also waive the 20 line rule only for issues which would've been caught by dryrun.

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. 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 and any students in Monday lab 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

With that, have a great Easter break, and we'll see you for one more week!

Hi all,

We are aware of an issue with the dryrun CLI tool where it does not run the dryrun tests. You should instead use the GitLab option which is described and explain in the assignment specification. You can also download the dryrun files and copy them into your repository if you wish to debug the tests.

For any re-run changes that would have been caught by the dryrun, we are not applying the 20% penalty. For all other re-runs, the 20% penalty will remain.

Please also note that the deadline for submitting re-runs has been changed to: Monday 28th April (Week 11) 1pm. This still gives you ample time to inspect your automark results.

Hi all,

Automarking results for Task 2 have been released to the automark-results branch, similar to assignment-i.

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: https://cgi.cse.unsw.edu.au/~cs2511/25T1/student-grades.

Each task will have its own mark and a penalty if a re-run attempt was made. (See more info about reruns below).

Please note that the total automark for each Task will be scaled and summed with your design marks. These below are the raw marks.

Re-run requests (Failed compilation)

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

Please tick all the checkboxes for which task you are requesting a re-run for.

If you are unsure why it is not compiling, you can make a private post on Ed, 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/uV4XYJUGiPLNLKuB9. Please make sure you follow the exact instructions the form provides.

Re-run Request (Short 20 line fix for each section)

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

We will take the maximum mark between your new automark (with the 20% penalty) and current automark for each task you have requested a re-run for.

You can find the instructions on how to submit a re-run request in the form: https://forms.gle/uV4XYJUGiPLNLKuB9. Please make sure you follow the exact instructions the form provides.

Other

Final marks will be released around the end of Week 11.

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

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 🧟

Assignment II is due this Friday at 3pm. We do not accept any late submissions under any circumstances - ELS and special considerations provisions are handled on a case by case basis so email the class account to discuss with us.

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

Assignment III 🎏

Assignment III has released! Both the spec and repo are available on the course website, and your groups are the same unless you expressed a desire to change your group, or if you were in a group of 3 for assignment II, in which case your group was split. You can verify your group on the course website, and you can still contact your tutor to change your group if you'd like to.

The assignment is worth 8% bonus marks (which only catch up lost assignment marks, not marks lost in labs or the exam). This means you won't lose any marks if you don't complete it. It is due Week 10 Friday at 3pm, though no late penalty is applied until Week 11 Tuesday at 3pm. Submissions won't be accepted after Week 11 Friday at 3pm.

We will also be briefly going over the assignment spec in an upcoming lecture, so keep an eye out for that.

Sample Exam 🧑‍💻

In the week 10 lab, there'll 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.

Public Holidays 🐰

There's a number of public holidays coming up - this Friday, next Monday and next Friday are all public holidays. No classes run on Fridays, but for next Monday, all classes will not run - students in those labs will need to attend another lab to complete the sample exam.

Assignment I Reruns ⏪

All assignment I reruns have now been run - if your mark hasn't updated, either your rerun mark would've been lower than your old mark so we took the old mark, or your rerun wasn't accepted.

Git Helper 🔀

And finally, a quick mention of an existing helper present on the course website - https://cgi.cse.unsw.edu.au/~cs2511/25T1/assignments/how-to-git-merge contains some information about git and Gitlab which is quite useful for assignment 2.

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

Hi all,

The assignment-i results have been released. You can find it on the course website here: https://cgi.cse.unsw.edu.au/~cs2511/25T1/student-grades

Your tutor should have given you feedback on GitLab. It could be on the submission merge request, or in a branch. If you are unsure, please contact your tutor first.

If you have any questions, please contact your tutor or marker first. If you are unable to solve any issues, you can raise the issue to cs2511@cse.unsw.edu.au.

Automarking Re-runs

See this for more info: https://edstem.org/au/courses/21364/discussion/2554323

Hey all! Hopefully everyone's well underway with assignment II! Only a few quick announcements this week

Assignment I Marks 🖋️

Assignment I marking is nearly done, and we'll be releasing the marks on give over the coming couple of days. 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.

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 using this form. We will rerun patches 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.

If you have more than 20 lines changed in your request, your rerun request will not be run. Similarly, failing to follow the instructions on the form correctly will make you ineligible for a rerun, which will not be grounds for another rerun. All reruns will incur a 20% penalty to your automark, though we will take the maximum of your old and new mark i.e. your mark will not be lowered. Note that the form will close at 3pm this Friday 11/04/25, and that all rerun requests will be run shortly after that date. For further information, have a look at this forum post

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!

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. Failing tests are guaranteed with the dryrun as it runs it against every option for Task 2, not just the ones you picked - just make sure you check that the tasks you completed are passing.

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 some exciting new content in the form of more complex generic typing and the singleton pattern!

Hi all,

We've made some amendments to our automarking after identifying an issue. The impacted tests were B-2-2 and B-3-1.

To view the updated results, follow the same instructions as outlined in #898. The automark-results branch has been updated, so viewing it now will reflect the corrected data.

Edit: B-3-5 was also amended.

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: https://cgi.cse.unsw.edu.au/~cs2511/25T1/student-grades

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 8.1 Dryrun in the spec.

If you are unsure why it is not compiling, you can make a private post on Ed, 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/s5HftoN4Ecm78kDb9. Please make sure you follow the exact instructions the form provides.

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.

We will take the maximum mark between your new automark (with the 20% penalty) and current automark.

You can find the instructions on how to submit a re-run request in the form: https://forms.gle/s5HftoN4Ecm78kDb9. Please make sure you follow the exact instructions the form provides.

Questions

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

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 not showcase why your project failed to compile, only that it didn't. You can validate and determine why your submission did not compile by following 8.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.

We have ensured that every student who passed the dryrun has a valid compilation result.

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 8.1 Dryrun in the spec.

If you are unsure why it is not compiling, you can make a private post on Ed, 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/s5HftoN4Ecm78kDb9. Please make sure you follow the exact instructions the form provides.

Hey all,

Welcome back! We hope you had a relaxing and/or productive flex week! Not too many announcements this week, all regarding:

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! To help with better understanding the assignment, we will be having a discussion of the assignment tomorrow, Week 7 Monday in the lecture. Please come along with any questions you'd like to get answered!

As a quick reminder, if you have any group work issues as you're working on the assignment, please tell your tutor as soon as they occur - swift resolutions mean you can get back to coding quicker. A paper trail starting as soon as it happens also makes our life easier.

I'll also quickly shout out that assignment II 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 3 weeks! The forum also has an FAQ with a list of approved assumptions pinned, which you can use to quickly check if your question has already been answered! We'll keep this up to date as the term goes on.

And with that, we're done with announcements! We'll see you back in classes starting from tomorrow as we continue looking at design patterns 🙌

I hope you had a restful and well-deserved break! We'll kick off Week 7 with an in-depth introduction to Assignment 2 during our Monday morning lecture at 9 AM. Please come prepared with any questions or clarifications you may have about the assignment. We'll also explore more interesting software design patterns and discuss essential considerations for effective software development. See you tomorrow morning!

Cheers Ashesh

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 😌

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 Friday 3pm. This includes all special considerations and most ELS cases (you'll know if you're an exception).

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 🕷️

Assignment II is out! Both the spec and repos have been released on the course website, and you should be able to see your partner on the website as well. 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 try 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.

Also note that assignment II is a pair project (with a few groups of 3). We're well aware that with groupwork issues can come some teamwork issues. If you're having issues working with your partner/s, first try and resolve the situation within your group - see if you can talk with them and let them know how their actions affect you. If issues continue to persist, then let your tutor know as soon as it happens - telling them the week of is best as then we have the most time to try come to some sort of resolution. Only telling us in week 11 severely cripples our ability to do anything as we have no more opportunities to discuss this in person with you.

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, I exit stage right - enjoy your earned break, and we'll see your refreshed faces in week 7 👋

Hi all,

Lab04 is due Tuesday 10am in Week 5.

Our submission scripts will still run on Monday and will be incorrect. Tutors will be aware of this when marking.

Hey all,

We've only got a few announcements, but they're quite important - please read them carefully!

Lab Due Dates 🔬

As we reach week 5, we have some quick reminders about lab due dates as they get a bit funky with flex week. Lab04 is due Week 5 Tuesday, and lab05 is due Week 7 Monday - there is a two week gap between the two as we don't count flex week. From there, lab07 and lab08 are due Week 8 and Week 9 Monday respectively.

Assignment I ⌛

One more week of trains! Assignment I is due this coming Friday at 3:00pm Sydney Time. As with labs, submit your work via Gitlab by pushing to the main branch (we will not accept any work pushed to other branches under any circumstances). The final commit before the hard deadline is what we look at when marking, so feel free to push as many times as you want, including after this Friday if you need more time and are ok with the late penalty (detailed in the spec).

As most of you will have experienced, Gitlab pipelines can slow down a massive amount nearing submission deadlines - we recommend you try to submit early to avoid issues with Gitlab. If you find pipelines slowing down a lot, you can test everything locally (including dryruns) to verify the pipelines yourself instead of waiting for Gitlab to run them. These pipelines are merely a convenience, not a necessity, and as such we will not accept slow pipelines as a reason for any form of leniency.

We've got a lot of help sessions scheduled this week, so feel free to drop into any of them and get assignment help (or any other help) you may need! The schedule is accessible on the course website as always.

Assignment II 🧟

After assignment I, we have assignment II! Group organisation should be coming to a close, and your tutors should either have already assigned groups, or be finalising them over the coming days.

The spec will release on Gitlab and will be accessible on the course website under the assessments tab. It will be released Tuesday-Wednesday for anyone who wants to read it early. The group repos will be released afterwards on Friday night, after the assignment I deadline has passed.

Even though we're releasing the spec early, you aren't expected to read it as soon as it comes out - spend your time on assignment I as you see fit, and once you're happy with your work and you finish submitted, you can move onto assignment II. We are just releasing it early so it's available during flex week and so that you can start early if you want, not because we expect you to.

Considering it's due Week 9 Friday, you have more than enough time to wait until you finish assignment I and potentially also have a bit of a break during flex week before you start assignment II. In the week 7 lectures, we'll also have a section where we'll go over the spec with some added commentary and more detail, so stay tuned for that!

That's about it from us - all the best with assignment 1!

Hey all!

Week 3 down - basically 1/3 done with the term! Here are the announcements for this week.

Assignment I 🚆

It's been great seeing so many of you well underway with Assignment 1 and asking questions during labs/help sessions! If you haven't begun yet, now is the best time to - the assignment is due Week 5 Friday at 3pm Sydney Time, just under 2 weeks from now.

As another note, we have a dryrun available on CSE servers and as a manual CI/CD job, with instructions on how to run both dryruns on the spec. These dryruns are not comprehensive autotests - they only check that your code will compile with our marking autotests. This is important as we can't award marks if we can't test your code, and there is no leniency for compilation errors, so we recommend to run the dryrun and run it often. If you are unsure of why your dryrun fails, you can find the contents of the tests here.

As one final bit of assignment related news, we have a lot of help sessions scheduled for you to ask all sorts of questions both in person and online. Similarly, forum questions will regularly be answered thanks to our wonderful tutors - we're here to help you out 🫡

Coursework Marks ✅

Lab marks for the past couple of weeks should be accessible on give - any lab you get marked off with a tutor should show up on give within 24 hours. If you don't see your mark and instead see ., that lab hasn't been marked off yet on our system - if you think it should be marked off, let your tutor know ASAP - either email them or let them know in person.

Assignment II Pairs ✌️

Assignment II group creation should be well underway and will be finalised by the end of this week, so make sure to give preferences to your tutors if you haven't already. They should already have told you how best to give them your preferences, so just fill out their form, send them an email or whatever they asked for!

As another reminder, this assignment can only be completed in pairs from the same tutorial (with one group of 3 for classes with an odd number of people) - this will not be waived under any circumstances.

And that's about it for this week - we've got one more week of design principal content this week, and then we move into the design pattern section of the course for the remaining weeks of term!

Hi everyone, We've shared a kick-starter video here to help you get started on your assignment! This video builds on the Week 2 Wednesday lecture (spec walkthrough) and provides advice on how to approach domain modelling effectively. You can also find the link for the video in the tips section of the spec.

Hey all,

Week 2 is now over - hope things are still going strong! We've only got a couple of announcements this week:

Assignment I 🚃

Assignment 1 is now fully released! You should have access to both the spec and the repo, accessible on the Assignments tab on the course website! It's great to see plenty of people starting on it already - as we say every term, starting early is the best way to have a good time with the assignment as gathering and deciphering requirements, as well as implementing them with good design, takes quite a while.

There are some things in the upcoming tute which will be useful for the assignment as well - design principles, UML diagrams and testing with JUnit are all quite necessary to complete the assignment.

Note that there have some been changes to the assignment in the:

• Spec:

  • Viewable on the changelog of the spec

• Codebase:

  • We updated some equality checks to handle NaNs for floating point values

  • Added a test (disabled by default) which tests for use of static variables. Static variables may cause issues with our testing and lead to reduced marks

Assignment II Pairs 🥢

Over the next couple of weeks, your tutor will begin organising assignment 2 pairs, and will explain what their process for pairing you up is. Please note:

• Pairs must be from the same tutorial

• You will be given the opportunity to give preferences for pairs, and while we will try our best to match those preferences, we can't guarantee all preferences will be satisfied.

That's about it from us - hope things go smoothly for you with labs and the assignment, and we'll see you all next week 🫡

Hello everybody,

Week 1 has finally come to an end! We hope you had a great first week back at uni and had the chance to meet up with your peers and our staff. Every week, we'll be posting an announcement just like this one on our course website to remind you of the upcoming things each week. Here are the announcements for week 1:

Tutorial Solutions + Recording 🎥

At the end of each week on a Friday, we will release solutions and a recording for the tutorial that week. The Tutorial 01 solutions and some legacy recordings are now available on the tutorials page.

Lab01 ☕

Don’t forget --- Lab01 is due Monday, Week 2, at 10am. Make sure you push (not just commit) your code to Gitlab by the deadline each week. Late submissions won’t be accepted, so don’t miss the cut-off!

We do highly encourage that you give these labs your best shot. A reminder that around 50% of the exam content will be very similar to the labs and tutorials within this course. If you have completed every lab properly, I'm sure you will all smash it with flying colours 😎.

Over the next two weeks, your tutor and lab assistants will be manually marking your submissions during your lab sessions. Be sure to attend so they can mark you off. After this period, labs won’t be marked without a valid reason, as detailed in the course outline.

Assignment I 🚅

The Assignment I specification will be released early next week. We'll be going through the spec in a lecture, so tune into the lectures to get some explanations of what's going on!

Support ❓

The beginning of term often comes with setup challenges and questions about getting to grips with Java. These can be tricky to tackle on your own, so if you’re running into problems, make sure to jump into a help session or post your query on the forum.

And that’s it! I hope you’ve all had a fairly smooth start to your week. Take some time to relax over the weekend, and we’ll see you all again soon 🙌

Welcome to The Art of Software Design (Object-Oriented Design and Programming)! The course outline is now available; please take the time to carefully read it as it contains all the necessary details for the most recent course offering. The course website is located at https://cgi.cse.unsw.edu.au/~cs2511/ .If you have any queries about the course, please use the course forum , see the link in the left panel of the course webpage.The tutorial and lab start in Week 01. You can find Tutorials and Labs by clicking on the corresponding links in the left panel of the course website .The first lecture starts at 9am on Monday , 17 Feb 2025! You can find the location and Teams link under "Lectures" in the left panel of the course webpage.

30+ passionate tutors, the administrative staff (Alvin, Sai, Michael, Grace and Daniel), and I are excited to start the new term next week.CheersDr Ashesh MahidadiaLIC, COMP2511 (25T1)

Hey everyone, welcome to COMP2511 🥳!!! Over the next few weeks, we’ll unravel the mysteries of great software design and how it comes to life in the real world. This course is all about equipping you with the skills to stand out as a software engineer, but you're going to hear all about it from your tutors next week :).

My name is Michael (or Mike), and I'm one of the admins this term alongside Alvin Cherk, Sai Nair, Grace Kan, and Daniel Khuu! I'm currently in my fourth and final year of my Computer Science degree and have been tutoring this course for quite a while now.

In my spare time I love eating new food, hanging out with friends, playing video games (recently been Baldur's Gate 3 and Marvel Rivals), and most recently dabbling in making games with Godot!

The tutor team and I are very much looking forward to meeting all of you over the coming term, so please feel free to drop an introduction of your own in this thread! Pet pictures are always welcome, so I'll start with my dog Bingo who loves sitting under my desk 😆