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: https://forms.gle/bYPU6bmQuXEtU3GX8

Hi all,

Assignment-ii marks have been released on the course website. There are 3 entries, ass2_part1, ass_part2 and ass2 which are marks for Part 1, Part 2 and overall respectively.

If you have issues with your marking, please email the tutor who marked you and cc the course email cs2511@cse.unsw.edu.au.

Also a reminder to complete the anonymous feedback form: https://forms.gle/bYPU6bmQuXEtU3GX8

Hi all,

We are looking for extra feedback from students as we had a low participation rate in myExperience and myExperience doesn’t allow you to comment on things such as exams.

We do and will read all feedback from myExperience and this form, and we value your feedback.

Found the exam hard/easy? Liked/disliked group assessments? Are there things we could have done better? Let us know

The form is anonymous and you can complete it at any time until the end of Week 13: https://forms.gle/bYPU6bmQuXEtU3GX8

Hi all,

The exam is this coming Monday 18th August.

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

1. There is now an extra combined-25t2.pdf file in the provided exam resources which contain all the lecture slides. This should make it easier to search for things (Index of /~cs2511/public/25T2/exam-files/lecture-slides).
2. Watch the exam environment demo so you are familiar with the exam environment before you sit your exam. This is a good preparation and stress reducing step!

3. Use the Week 11 Revision Lecture to assist you in your studies for the exam.

---

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 Admin Team

Hi all, you can find the revision lecture’s recording link here:

Hi all,

The revision lecture is tomorrow (Wednesday) starting at 1pm. The lecture will be held in-person at Old Main Building G31. You can find a map guide here: MazeMap

There won’t be an live online alternative. The revision lecture will be recorded and released later in the day via an announcement.

---

We have added some more online help sessions for this Wednesday and Thursday. You can find them on the course website here: 🧑‍🏫 Help Sessions | COMP2511 (25T2)

Hi all,

For those who were not able to make it to an in person lab in Week 10 for the sample exam, or want a refresh about how the exam environment works, I have recorded a demo you can watch:

If you have any questions, please post on the forum

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.

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 forum, 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/kdbytKEqpkdvAaNu6. 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/kdbytKEqpkdvAaNu6. Please make sure you follow the exact instructions the form provides.

Hi all,

You are encouraged to attend and bring any questions you have. The tutors will be walking through some core topics and how to answer exam style questions.

For those we cannot attend on the day in person, a recording of it will be released. There will be no live version.

---

If there are any issues or questions, please post on the forum.

Hi all,

The sample exam has been released under week 10 on the course website: 🧪 Labs | COMP2511 (25T2). If there are any issues with the sample exam, please make a post on the forum.

We will release further revision exercises soon.

Hi all,

Our tutors have created some extra course notes that may assist you in the assignment and exam. They are:

• 🗂️ C4 Diagrams | COMP2511 (25T2)
• 🐟 Mermaid Sequence Diagram Docs | COMP2511 (25T2)
• ✏️ Excalidraw & Mermaid | COMP2511 (25T2)

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, submitting part 1 via Gitlab and part 2 via Moodle. As a quick reminder, the assignment is due by this Friday at 3pm.

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. This term in particular, 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

With that, enjoy your final week of term!

Hi all,

If you were not aware, COMP2511 in this term introduced the topics of Architecture Design/Systems. We reduced the Object-Oriented/Design pattern content to allow for this to occur. Lab08 and Lab09 as well as Tute08, Tute09 and Tute10 are new content that the tutor and course team have written.

We understand there may be many pain points and confusion in our course content and assignments. We welcome any and all feedback about these new changes. We want to improve and build on your feedback.

You can find the myExperience survey here: https://myexperience.unsw.edu.au/

Hello everyone! Hope you’re all keeping up with Assignment 2. Just a reminder that it’s due next Friday, so if you haven’t started on Part 2 yet, I highly recommend getting onto it soon.

To help you get started, we’ve made a video that was added to the spec a few days ago. If you haven’t seen it yet and you’re finding Part 2 a bit tricky to approach, definitely give it a watch.

I’ll include the link in this announcement as well: COMP2511 Assignment II Part 2 Walkthrough | Loom

Hi all,

See below if you’d like to participate in a study with the School of Psychology at UNSW.

---

The Health Psychology lab in the School of Psychology at UNSW is looking for participants to take part in a variety of research studies. Current opportunities are for studies related to: eating in everyday life; and communicating and predicting pain. If you are interested in learning more about the available opportunities, click this link to complete an expression of interest form (Qualtrics Survey | Qualtrics Experience Management) or contact us at healthbehaviourresearch@unsw.edu.au.

Hi all,

Jesse will be away in Canberra for a conference on Thursday. There won’t be a lecture on Thursday. Instead, Jesse has recorded the lecture and it has been published on the course website under “Special Lecture Recordings” found here.

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

The second half of assignment II has been released! Take a look at the new sections and begin working on them as soon as you can, since assignment II is due next 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 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.

Lab07 Results

We are aware of some issues relating to lab07 marks - please consult your tutor if your mark doesn’t match what you expect, or if you have a mark where you shouldn’t or vice versa. We are trying to resolve this issue internally as well, but it’s still advisable to reach out for discrepancies regardless.

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

Hey all! Hopefully everyone’s well underway with assignment II! Here are this week’s announcements, a bit later than normal this week

Assignment I Marks

Assignment I marking is nearly done, and we’ll be releasing the marks by the end of the 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 this Friday. 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.

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 and 09

Just a quick reminder that lab08 is due on Moodle Monday 28th July at 10am, as opposed to on Gitlab as with previous labs. Please ensure you submit via Moodle by the due date in order to avoid any issues.

Despite the different submission medium, Lab08 is still marked in person. However, we will not be marking it in help sessions, only in labs. This same marking process will hold for the new lab09 as well, which will be completed and marked in the labs.

If you are unable to make your lab, you may join another lab to have your labs marked. However, as always, tutors will prioritise their enrolled students before any extra students, and you may not get your lab marked if too many students are in a lab.

Assignment II

Assignment II part 2 is now out! The spec is available on the same assignment II spec as part 1, and focuses on a financial data system and how to design the architecture for it. It is also submitted on Moodle, similar to lab08.

Also, 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 the new system architecture content!

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 (25T2)

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). ass1_late_penalty_days is the late penalty calculated from your submission. The number factors in any ELS/ELP/Special Consideration extensions.

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/K79CHdU9XHcYts258. 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/K79CHdU9XHcYts258. 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.

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 8.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/K79CHdU9XHcYts258. Please make sure you follow the exact instructions the form provides.

Hey all,

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

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 on Tuesday Week 7 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 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 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.

Lab08

Lab08 has been released! The link is accessible here, and is submitted via Moodle. This is also how the second part of assignment II will be submitted. The due date will be 10am Week 9 Monday.

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

Hello everyone! Just a quick update: the Assignment II specification has recently been updated to include:

• A link to a walkthrough video I created, under the Getting Started section
• An approved assumptions list, now available under the Assumptions section

You can also find both of these directly here:

• Walkthrough Video: https://www.loom.com/share/cef4b99f5f42472a8c48532929fd18f3?sid=9ec3952e-e0c7-404b-89e8-c7a1af6e433f
• Approved Assumptions: [Assignment II - Part 1] Approved Assumptions

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 most special considerations and 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

The first part of 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 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 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 the incidents 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.

Lab09

As an extra addition this term, we’re adding a lab09 to assess your understanding of architectural content. This lab will be completed and marked in the lab itself, and is worth the same 10 marks as all other labs.

However, despite this adding 10 more marks to be gained in the lab component, we are not changing our calculation of your lab component of the course mark. We still cap your achieved number of marks at 60 and use that to calculate your lab mark - this just means that there are 80 available marks and we only cap it at 60, effectively giving you 10 more possible marks to achieve - if you cannot make lab09 or cannot complete the lab for any reason you will not lose any extra marks compared to if lab09 wasn’t there.

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,

For all classes Thursday onwards will be normal. We expect no more changes for this week.

Similar to Tuesday, due to the poor and dangerous weather, Wednesday classes have moved online.

Your tutors will reach out with information on how to join the online class via email tonight.

We expect business as usual Thursday onwards.

Due to poor weather forecasts tomorrow and a severe weather warning Bureau of Meteorology, UNSW has instructed all course to move in-person classes and lectures online. No classes on Tuesday will be in person.

Your tutors will reach out with information on how to join the online class via email tonight.

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 Monday , 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.

For marking off the labs in person, we don’t count week 06 as a lab for the 2 week rule.

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 later this week for anyone who wants to read it early. The group repos will be released shortly afterwards, after the assignment I deadline has passed.

We’re releasing the spec earlier than we expect you to start reading/working on it - 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 10 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!