Hey everyone,
A massive congratulations to all of you for completing the course and getting through the term! You are all hopefully one step closer to being 'perfect' software devs π. A special congratulations are also in order for the top 10 students in the course!
Congratulations to each and everyone of you for your fantastic performance - you should all be incredibly proud of your efforts.
On another note (the same note we give multiple times every term, but which warranted every time), the biggest of thank yous to our tutors - none of this would be possible without you. They work so hard to continuously improve your experience, both in your tut/labs as well as behind the scenes with marking, forums and help sessions. On a personal note, another massive thank you to my fellow admins, who are the reason this course runs at all. Their tireless work is the reason you have such a smooth and seamless experience. They are also the reason that the tutors have such a seamless teaching experience and can provide such a great education to you.
A massive and congratulations once again, and all the best for your future education and endeavours,
Ashesh and the admin team
Assignment-iii marks have been released on Give. Please have a check and raise any issues immediately to cs2511@cse.unsw.edu.au.
COMP2511 Admin Team π«‘π«‘
Hey all, just a quick couple of announcements from me regarding reruns and then the exams!
Assignment 2 reruns have been completed - the effects on your marks and repo should be the same as in assignment 1, and are listed below.
We're almost at the exam day! Tuesday is the day of the exam, with timings being dependent on which session you're in - make sure you check https://cgi.cse.unsw.edu.au/~exam/24T2/seating/register.cgi/allocations/ for your timing and room allocation!
Some reminders for the exam:
Other than that, just a quick pep talk - you have all put in the hard work with labs and assignments already, and have the necessary knowledge to complete the exam. You have got this - don't let the nerves psych you out. If there are any problems on the day, email cs2511@cse.unsw.edu.au ASAP - we'll be monitoring it throughout the designated exam times. There will also be some members of the COMP2511 admin team present at the help desk on the day, so you can approach us to rectify any issues :D
All the best - you're on the home stretch now
COMP2511 Admin Team π«‘π«‘
Hey all,
Just a quick announcement to let you all know that marks and feedback should be progressively releasing tonight! Some classes may be slightly delayed, but your tutors will be reaching out to give you a rough estimate of when your marks and feedback should be released!
On another quick note, the revision lecture recording is now up! Have a gander at this video for solutions to the sample exam, as well as some insight into how we would approach some of these questions https://youtu.be/KvnXzfRiaak . Thanks once again to everyone who attended in person, and hopefully you found it useful π€©
There are also written solutions to the multiple choice and short answer questions for the sample exam over at https://nw-syd-gitlab.cseunsw.tech/COMP2511/24T2/specs/sample-exam-solutions !
Other than that, we hope your exam prep is going well!
Hey all,
A quick announcement tonight - assignment 2 automarks are now all released and viewable on the automarking branch on your repo. Manual marking will be released early next week.
We will once again be accepting reruns similar to assignment 1. If your code didn't compile, or if a small mistake (up to 20 lines) led to a lot of failing tests, you can fill in this form to apply for a rerun. Note that for all tasks which are rerun (you will need to indicate which tasks you'd like rerun), a 20% penalty will apply. For example, if you need to rerun your snakes task, you can patch up to 20 lines on a new branch called rerun and fill in the form, and 20% of your new snakes mark will be deducted - your marks for other subtasks will remain unchanged.
Note that we will not be accepting rerun requests after the 14th of August at 11:59pm (next Wednesday). Penalties will also not be waived for any reason except in circumstances where the reason for the rerun is not your fault.
Hey everyone,
Congrats on making it to the end of the term! You've made it through some tough weeks and come out on top, and for that you all are superstars π€©. As you finalise assignment III and prep for the exam, here are a few updates.
As mentioned in the previous announcement, there is going to be a revision lecture tomorrow from 1-3pm in Ainsworth G02 - this is a great chance to see admins solving some questions in the same style as your exam, analyse their thought processes for each question and ask any burning questions you've got! This will be recorded, so don't feel like you're missing out if you can't make it, but for the best experience, you should definitely come in person!
A quick reminder that myExperience is still open for the next couple of days! Your feedback is ultimately how this course improves, so leaving constructive criticism for the course and your tutors is always greatly appreciated!
Assignment II marking is now well underway - marks and automarking will be released at the end of this week/the beginning of next week, at which point we will release another rerun form similar to Assignment I. Further details will be released later.
For Assignment III, the deadline for having no penalty is now past, and penalties will now apply as of 5pm today. You will have up until this Friday at 5pm to make submissions, after which no submissions will be accepted.
We often get questions about how best to revise for this course. Here's a list of all the resources we recommend going through for revision:
By completing these, you should be well prepared for the exam! Other than that, have a productive but also relatively stress free stuvac, and all the best with your preparations!
Hi everyone!
The admin team is going to be running a revision session next Wednesday 7th Aug, at 1-3pm .
We will be going through some practice problems, some sample exam questions, and be talking through some theory to help you prepare for the exam.
Location: On campus, room Ainsworth G02
It will hopefully be recorded but we recommend you come in person - people in past terms have said it's very useful!
Hope to catch you guys then :)
Hey all,
We're almost done with content! Just one last week to go before stuvac and exams!
Congrats on making it to the deadline of assignment II π€© As you have likely already seen, we have extended the due date by 24 hours due to the severe slowdown experienced by Gitlab yesterday, though make use of this time as a way to finalise your merge requests and commits as opposed to finishing more of the assignment. We will not be having a grace period for submissions slightly past 5pm as you have 24 hours to finalise your submission.
Marking for assignment 2 will begin later this week after we calibrate marking, and you should receive your marks by the end of Week 11.
Assignment III is well underway! Look at last week's update for more details on what it is and how it works. If you choose to work on it, you are still able to find support, including in help sessions and especially on the forum. That being said, there is no need to work on it if you are finding yourself swamped by other work, either in COMP2511 or in other courses - as mentioned in last week's announcement, this is a bonus assignment, so not completing it doesn't lose you any marks.
Assignment 1 reruns have been completed - your mark should already be updated on give, and you should be able to see an extra commit on your automarking branch if your rerun was accepted. If your mark hasn't changed, we took your old mark as your new automark would reduce the mark you receive. If you can't see the extra commit, your rerun wasn't accepted, either for not following the steps outlined in the form, or for changing too many lines.
myExperience is open! Please complete the questionnaire, as your feedback directly leads to changes from term to term and improvements for course offerings to come! We greatly appreciate all feedback that we receive, and take it all seriously! Your tutors also would greatly appreciate any nice comments you can give them, as well as any feedback you have for them π
As mentioned last week, a sample exam will be run this coming week in labs. This is only available in in person labs , so if you're in an online tutorial normally, try to attend any in person lab.
The full sample paper and solutions will be released on WebCMS at the end of the week, but a large part of the reason for attending this sample exam is to get familiar with the exam environment and avoid any mishaps on the day of the exam - we will be less lenient on such mishaps for this reason.
Note the sample exam paper has questions with the same format and style of questions as the actual exam, but the difficulty and number of questions may differ.
All the best with the final week of term! One final week of content π½
Hey all, lots of announcements this week!
Assignment III has now been released, with both the spec and the repository available to you. Your groups are the same as in Assignment II unless you have requested otherwise - check your assignment III repo to see who is in your repo. If you'd like to change your group now, or if you'd like to do it solo (as it is an optional solo/group assignment), contact your tutor ASAP.
The assignment is worth 8% bonus assignment marks (they can only catch up on marks lost in assignment I and II, not labs or exam) so not completing the assignment won't lose any marks - it is entirely to catch up on lost marks. It is due on Week 10 Friday at 5pm, though no penalty is applied until Week 11 Tuesday 5pm . Submissions are capped at 7 days after the original due date though i.e. no submissions are accepted after Week 11 Friday 5pm . Have a read of the spec for further clarification!
In the week 10 lab, we will be running a sample exam for you to gain some experience with the exam environment. This is not for marks, but it will help you to gain some familiarity with the system so that you can spend all your time in the actual exam answering questions instead of trying to navigate the system. It will also provide you with an opportunity to look at some past questions to observe the types of the questions present in the final exam (the number and the difficulty of the questions may differ).
It is highly recommended that you attend this sample exam for these reasons. Note that this exam environment is only present on the university computers, so if you are in an online tutorial, you will need to attend an in person tutorial for week 10 - any tutorial should be fine!
Assignment II is due this upcoming Friday 26th July at 5:00pm . A reminder that no late submissions are accepted for this assignment under any circumstances . If you have ELS provisions relating to group work, or special considerations, email the class account for other arrangements.
As always, remember that the forums and help sessions will be up and running this coming week, with a help session tomorrow and then 5 help sessions over the week. Make use of them, though please remember that simple asking for solutions is not an acceptable question to be asking tutors, both in help sessions and in classes.
A quick reminder that the rerun requests after Sunday 21 July 11:59pm will not be accepted. These requests will be rerun soon after.
Lots of things happening these next couple of weeks - hold on to your hats and we'll see you on the other side π€
Hey all! Hope you're all well underway with assignment 2, and that things are going smoothly!
Assignment 1 marking is nearing completion thanks to the amazing work of your tutors, and your marks should be available on Monday on give ! Feedback will be provided to you (or maybe it already has π) by your tutors over the coming days as well. Most likely this will be on Gitlab, either under a new branch or as an issue/merge request on your repo. If your tutor has another way of providing feedback, they'll let you know about it. Automarking results will also be pushed to your repos on Monday for you to look over. Please also note that all marks are subject to plagiarism checks which will be conducted in the coming weeks.
If your code didn't compile, or a small issue caused large amounts of tests to fail, you may ask for a rerun using this form . We will rerun patches with less than 20 lines changed - note if your changes are above this amount, your rerun will not be run. On a similar note, failing to follow the instructions in the form will prevent your rerun from running correctly, which is not valid grounds for request another rerun. All reruns will incur a 20% penalty to the automark (including if your code didn't compile) though we will take your original mark if your new mark is lower. Note that the form will close at 11:59pm on 21/07/24, this upcoming Sunday.
If you have any questions with your design marking, please email your marker (should be the person who pushed your feedback) for clarifications. Beyond that, regardless of your marks, we hope you have learnt from this assignment and have a better understanding of design principles, and that you can apply this newfound knowledge to Assignment 2! Speaking of which...
Similar to assignment 1, we also have a
dryrun
for Task 2 of Assignment II, run with the command
2511 dryrun ass2
. Please run it regularly to make sure that assignment II compiles correctly as well. It's especially important to
run as you go
instead of leaving it to the last minute and having unexpected bugs come up before submission. Don't panic because of errors - all groups are guaranteed to fail the dryrun for the Task 2 tasks they did not do. However, do make sure to read the errors carefully in case it's an error in a task you
did
do.
Finally, a reminder that our forums and help sessions are still running this week - make good use of them to get any questions you have answered!
We're nearing the end of term - we're entering the back end of design patterns, and heading nearer to holidays week by week! All the best in these last few weeks!
Hey everyone, welcome back! We hope you had a very restful and/or productive flexi-week! The main announcements we have are all regarding:
During Tuesday's lecture, we'll be having a discussion of the assignment specification and the requirements of the assignment - come along with any questions which have arisen when looking over the spec and/or beginning the work last week.
Hopefully everyone has had a look at the assignment by now, and potentially have started! As you continue working, if groupwork issues arise, please ensure you flag it with your tutor as soon as it happens - we want these conflicts to be resolved sooner rather than later to give everyone a good shot at completing the assignment with no further problems. It also gives us an opportunity to keep a trail of what happened when.
Other than that, a reminder that assignment 2 also has a dryrun (the command is
2511 dryrun ass2
), and our forum and help sessions are still perfect places to ask questions! The forum also has an approved assumptions thread which is pinned (this is linked on the spec as well) so make sure you have a look at that before asking a question :)
That's about it from us - we hope you enjoy the next few weeks of the course π!
Hi everyone! We're at the halfway point in the term - congratulations on making it so far! This upcoming week is flexi-week, so make good use of it to rest a bit, catch up on anything you're behind on (for this or any other courses you're doing) and release some stress! π
Congratulations on completing Assignment 1! No matter how easy or difficult you found it, you did well to complete it and apply some OO principles to your own code!
For people still working on their code, please note that no submissions will be accepted after this Friday, 5th July, at 5pm. This includes all special considerations cases and most ELS cases.
Our tutors will be hard at work marking your assignments over couple of weeksπͺ. Marks and feedback should hopefully be released back to you by the end of Week 7 or at the beginning of Week 8.
For those of you who didn't see the spec and repo release on Wednesday and Friday respectively, assignment 2 is out! We'd recommend reading through the spec, looking through the codebase you've been given, and potentially beginning some of the initial tasks over this week . As we mentioned for assignment 1, getting a nice design takes time, and this is especially true when you're working on a codebase which you haven't designed. Even just looking through the codebase is a good idea - that will almost certainly take longer than expected, and if you don't, you might miss things useful in later tasks!
Note that if any teamwork issues arise, it's best to first attempt to communicate these issues with your partner, but if they persist, let your tutor know as soon as it happens - the week the issue occurs is the best option. This allows tutors to try and resolve it early - leaving it to week 11 will limit how much we can do.
As mentioned last week, Lab05 is due Week 07 Monday - do note that working through the lab will likely help with your assignment as well, so doing it early is well worth it.
And as always, we still have help sessions running this week - schedule is on the help sessions page on WebCMS!
That's all from me - enjoy your well deserved break, and we'll see your fresh faces again in Week 7!
Hey all! Hope you've been having a fantastic term so far! Let's get right into it π€©
As we reach the halfway mark of the term, lab due dates get a bit muddled due to flex week. A quick reminder that Lab04 is due Week 5 Monday at 10:00am and Lab05 is due Week 7 Monday at 10:00am (both times are Sydney time) . From there, Lab07 and Lab08 will follow weekly after Lab05's due date.
We're reaching the end of the first assignment! It's due next Friday at 5:00pm (Sydney time) - less than a week to go! Remember that submission is done via Gitlab - to submit, just push onto your main branch. We only look at your latest submission, so you can push as many times as you want.
Some of you may remember pipelines slowing down a lot during submissions for COMP1531 - this may be the case again this term as the deadline draws near, with the potential for pipelines to become increasingly slow or even fail. Make sure you try to submit early to avoid this issue, and if you do encounter the issue, test your linting and tests locally to ensure that when your pipeline actually runs, it remains passing.
We've got 5 help sessions running in Week 5 from Monday to Thursday, so feel free to drop in to any of them for any assignment help!
And finally, a quick reminder that the dryrun is still available for use for a nice sanity check ( not exhaustive testing ). More info is in the spec and in last week's announcement.
Assignment 2 is up next! Group organisation should be wrapping up - if you don't receive your pairings by this coming Wednesday, please contact your tutor.
The assignment specification will be released on Gitlab (in the same place as the assignment 1 specification) and on WebCMS (under the Assessments tab) on earlier in the week (most likely Wednesday night, though maybe earlier). Group repos will then be created on Friday night (after assignment 1 is due). While the spec is up for a few days before, and the repo is up immediately after assignment 1 is due, you don't need to stress about getting right into it. Take your time finishing up assignment 1 first, and once you're done and dusted, you can move onto assignment 2 (possibly with a well deserved break in between).
We're releasing the spec and repo early so that you have time to look over them in Week 6 and maybe make a bit of a start, not because we expect you to get right into it at that moment. The deadline is Week 9 Friday 5:00pm (Sydney Time) , so you have some time to rest in between if you would like.
We'll also have a section in a lecture in Week 7 where we'll go over the spec in a bit more depth and with some commentary, so keep an eye out for that!
Other than that, there's not really much else from us - all the best with assignment 1, and we'll see you victorious on the other side!
Hey everyone! Let's just get straight into the announcements
Assignment 1 has been out for nearly two weeks now! If you haven't made a start on it yet, now is a great time so begin! It's due 5pm on Friday of week 5 , so we're steadily approaching the deadline. The assignment is bigger than most people expect, so definitely don't leave it to the last minute!
We also have a dryrun command which you can run on CSE machines only to make sure your code compiles with our (very basic) autotests. Note it only checks that your code will compile - there are no tests which properly test your functionality. If you're unsure as to where the dryruns are failing, you can check the contents of these basic tests at this link . We recommend running this often and well before the deadline, so that you avoid any last minute rushes trying to get your code to compile.
There are also plenty of help sessions this coming week for assignment questions, and the forums are being well maintained thanks to our amazing tutors who are always there to answer questions π€©
Lab marks should be available for everyone on give - every lab you get marked off should show up on give within 24 hours of it being marked off. If you see a '.' for one of your labs, that means that lab hasn't been marked off. If it has been marked off and the lab is showing a . mark, then please email your tutor .
Assignment 2 pairs should be coming along, with your tutor discussing pair formation with your class. Pairs will be finalised by the end of this upcoming week, so if you have any preferences and you haven't told your tutor yet, make sure to do so quickly! Just a reminder that this assignment must be completed in a pair (or a trio in odd classes, with at most one trio per class) and that all groups must come from the same tutorial i.e. you cannot pair with someone from a different tutorial. There are no exceptions to these rules.
Over the past few weeks we've covered the foundational content of the course - OO design, fundamentals of programming in OO and design principles and smells. Now that we've built a solid base to continue learning on, we're moving into the wide and varied world of design patterns, starting off with the strategy, observer and state patterns this week!
That's about it from us! Keep up the great work, and we'll see you in week 4 π
Hey everyone! Hope your term is going well so far! Only a few announcements this week!
Assignment 1 has now been released - both the spec and repo can be accessed at the assessments link on WebCMS3! It's great to see some of you have already started working on it - if you haven't already, we'd highly recommend getting started nice and early over the next few days, as understanding the requirements and actually executing them with good design takes a while, longer than most people expect.
There are a couple of things covered in tute03 which will be useful for the assignment as well, namely some design principles, UML Diagrams and testing with JUnit, which is how your tests should be made for the assignment.
Over the next couple of weeks, your tutors will be organising assignment 2 pairs, and will let you know how that process will work for your tutorial. Please note that
Lab02's original due date coincided with a public holiday, so we've pushed back the due date by one day to Tuesday 11 June at 10am!
We hope that otherwise things are going smoothly! See you next week π€©
Hey all!
We're down with week 1 - we hope you enjoyed your first of many weeks back at uni, meeting course staff and peers! Hopefully setup issues weren't a problem for you, and you found the first lab doable.
This is the first of many announcements we'll be doing every week here on WebCMS. The aim of these announcements to give you some reminders of things to keep track of in the upcoming week, as well as announce any course related info to you and keep you all in the loop.
Every Friday evening to Saturday morning, we will release solutions to the tutorial for that week, as well as a recording of the week's tutorial. The first of these solutions and recordings are now available on the tutorials page.
Lab 01 is due Monday at 10am. We require all students to push their code and blogs to Gitlab by that date, as is mentioned in the lab instructions. If you haven't already gotten the lab marked, your tutor and lab assistant will be marking them this coming week in your labs, so make sure to attend class! As mentioned in the course outline, you have two weeks after the due date to get them marked off so please don't delay too much.
Please do make a good attempt at the labs - the content in the labs will set you up nicely for the assignments and the final exam, and should set you cruising for a pass (or higher) for the course!.
Assignment I will be released this coming week, so keep an eye out for that! We'll be going through the spec in a lecture, so tune in to the lectures to get some explanations of what's going on!
The start of term is where a lot of one-off issues can come up, and they may be obscure and generally hard to figure out. If you're having issues with setup issues or something along those lines, feel free to hop in a help session or post on the forum - our tutors are very friendly and knowledgeable π€©
That's about it from us! Enjoy your weekend, and we look forward to seeing you back again for another week!
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 website for the course is located at https://webcms3.cse.unsw.edu.au/COMP2511/24T2/ .
If you have any queries about the course, please use the course forum . The course forum can be accessed by following the instructions provided here .
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
9:00 am on Tuesday
, May 28th! The location and link are listed under
COMP2511 Lectures (in Person/Online)
.
Twenty-four passionate tutors, the administrative staff (Alvin, Sai, Carl, and Amanda), and I are excited to start the new term next week.
Cheers
Dr Ashesh Mahidadia
LIC, COMP2511 (24T2)