Hi everyone,
Now that we're wrapping up for the term, we would just like to say a quick thank you and goodbye :)
The first thing to say is a good job and congratulations to you all for making it through the term!
The top ten performing students of the course were, in order:
Chen, Daniel
Liu, Jason
Ly, Jayden
Cooper, Daniel
McPhee, Jun
Wang, Jennifer
Zheng, Samuel
Widjaja, Dominick
Lambrechts, Flynn
Cooney, Xavier
You've all been a genuinely great group of people to work with over the last 12 weeks and we hope that you are proud of your efforts.
We also want to say a massive, massive thank you to the tutors who are always putting their all into the course and into you students, both in class and behind the scenes. I'd also like thank the rest of the admin team Sai, Alvin and Carl for all their dedication in running the course and working to make your experience as smooth as possible.
As a final note โ COMP2511 is a core course for CSE degrees for a reason, and we hope you're able to take away some of the skills and principles as you move into the real world. You're more than a programmer now, you're a software designer! The fact that youโve all come so far to complete the course is a testament to your dedication, commitment and tenacity, and with these qualities you can achieve almost anything.
Hope you have a relaxing summer and a lovely holiday period! Come and say hi if you see us on campus next year :)
From the ad min team + Ashesh
The big day is almost upon us!
The COMP2511 Final Exam is tomorrow. Couple of quick reminders:
If you're concerned about the hurdle, or are just generally a bit stressed for tomorrow - that's OK. You've done all the hard work already and it'll pay off tomorrow :)
Any other problems - email cs2511@cse.unsw.edu.au, or come see Alvin (one of the admins) who will be on site tomorrow.
Best of luck,
COMP2511 Admin Team ๐๐
Hey everyone!
Just wanted to announce that your class mark and pre-exam marks are now out. Note that it does not include assignment iii marks. Have a look on give and let us know via the course email if there's any big problems :)
Also, just bumping yesterday's announcement - I added a disclaimer about the 'L' on give. In short, you can ignore the L - all late penalties are integrated into the mark itself, not with the L.
Once again, all the best with the exam!
Hey Everyone!
Sorry for the confusion with assignment 2 marks! A couple of things:
All the best with the exam prep and final exam!
EDIT: Appears I made a typo in the title, it is not week 13 quite yet! โณโโณ
Some start of week announcements for a change!
Assignment II marks should be out on SMS! This includes rerun results. Your tutor should have provided you with feedback on GitLab unless they have notified you otherwise.
If you have any questions about the manual marking of your assignment, please contact your marker. If you have other questions please email the course account or make a private post on the forum.
Assignment III marking will be done after the exam and released along with final course results.
All your other marks for the course should be finalised by now.
We've received some questions about the exam on Edstem so reposting many of the answers here for visibility.
Q: When is my exam slot?
A: You should have received an email with information about your session
Q: Do I have working paper?
A: You will have a single A4 sheet, bring your own pen.
Q: What design patterns are in the exam?
A: All the design patterns that we have taught in lectures and tutorials might be on the exam. However, we won't be asking you to write code for the Builder, Adaptor, Visitor, or Command/Facade patterns.
Q: What should I be studying?
A: See the list from last week's announcement. We particularly recccomend reviewing the regular tutorial and lab examples, especially completing ones you have not completed yet.
Q: I have another question!
A: Ask on the forum and we will endeavour to reply.
The final response rate was 57%, so unfortunately no bonus mark :( but thank you to everyone who responded, we will use the feedback to continue improving the course.
Hope you all have a calm and un-stressful week, see you all on Thursday with a new notice before the exam.
Hey everyone!
The revision lecture happened yesterday at 11-1pm, and we had a great turnout! We hope those who joined us in person found it fruitful and gained something from it!
If you couldn't make it, fear not! Here is the recording for your viewing pleasure: https://www.youtube.com/watch?v=LdpXqcJrdXU
If you have any questions about content covered in the lecture, feel free to make a post on Edstem and we'll answer as soon as possible!
Final notice in this series - just two key points!
The exam revision lecture's time and date has been confirmed! It will be
We strongly recommend you show up, I've heard students in previous terms often regret not going. So see you all there :)
You should have all received a personal Gitlab repository of practice exam questions . It also contains the sample exam.
It is available at this link (or here if that doesn't work: https://nw-syd-gitlab.cseunsw.tech/COMP2511/23T3/students/z5555555/revision-exercises (replace the zID with your own)).
Please feel free to post on Edstem if you have any questions or if you want to discuss answers with other students and course staff.
In summary, the revision resources available to you are:
As mentioned yesterday, the Assignment II rerun form is now open and available!
If you feel you have a small mistake in one of your tasks, which requires a change of up to 20 lines, you can fill in this form to apply for a rerun. Note that in all cases there will be a penalty of 20% applied to the new performance mark for that given task. This includes if your code didn't compile beforehand.
For example, if your enemy goal did not compile, you may patch it (<=20 lines) on a separate branch and submit the complete (patched assignment) on Give in order to have it rerun, but you will be penalised 20% of your enemy goal performance mark. Your other marks will be unaffected.
Note we will not accept rerun requests after the 25th of November 11:59pm AEDT (this Friday). We will also not be waiving rerun penalties unless it was an internal issue on our end regarding automarking or dryruns.
Hi everyone, well done on reaching the end of Week 10! Let's keep this brief:
You (yes, you!) ๐ซต, stop reading this notice and fill out your MyExperience!
We are currently at a 41% response rate, but this course has historically gotten to > 80% before so I know that number can be higher :)
Thank you to everyone who has filled it out already ๐๐
The admin team will be running a revision lecture this week to go through some sample questions from past exams and hopefully give you some tips :) It will be held on campus and also recorded (no livestream option), so come along with your questions! The pending time is Wednesday 11-1pm , room TBC.
Many of you attended the sample exam this coming week and got some familiarity with the exam environment! For those of you who didn't, the sample exam paper and solutions (but not the exam environment) will be available to you on Monday night .
On Monday night we will also be releasing a series of other revision questions, including some sample coding questions. Multiple choice and short answer are already available to you via this link.
Assignment II automarks are being rolled out right now, and they will be available to you on the
automark
branch
. Edit: Automarking is complete.
Please note there were issues with some autotests for the snake task which we have since amended - if your branch was last updated > 5 hours ago (as of this notice being published) these changes have not been applied to you yet, just sit tight :)
If anyone believes there are any other issues with their automarking, or if you have a question about your results, make a private message on the forum. The rerun form will be open on Monday.
If you do not have an automark branch at all it means there was an issue with your submission on Give. Please email the course account to resolve this.
As a reminder, no late penalty will apply until Tuesday 5pm .
However, w e will not be taking submissions after Friday 5pm (including ELS and spec cons).
Happy stuvac everyone, see you at the end of next week as well :)
We covered the exam-related information in Monday's lecture. If you haven't already, please watch the video. In addition, we reviewed the course and addressed a few topics about the final exam. Monday's lecture was the last ; we will post a pre-exam consultation time later this week or early next week. Please post any questions you have in the forum.
myExperience Bonus: Each student enrolled in the course will receive one bonus course mark if 80% of the class completes their myExperience. For example, if your final grade was 59, it will now be 60, 71 will now be 72, and 84 will now be 85. Please fill it out and motivate others to do the same.
Hey everyone! Just a couple of announcements:
First of all, assignment 3 is well underway, and is officially due at 5pm AEDT this Friday, though late penalties do not begin to apply until next Tuesday 5pm AEDT. Submission instructions have been added to the spec, and they are pretty much exactly the same as assignment 1 and 2.
Please make sure to submit as you go and submit often - we store backups so it's always good to submit, plus it's just a good practice to do for all courses. We will not accept technical issues in the last 5 minutes as a reason for leniency.
Do also note that there is no dryrun for assignment 3 - please be extra careful during submission (errors in your structure and things like that will not be grounds for leniency either).
Earlier today you would've received an email outlining some information about putting in preferences for the exam session you are seated in - this would've come from exam@cse.unsw.edu.au, and be sure to look out for it (might've gone to spam, though it's pretty unlikely).
This email outlines some brief instructions and the link (https://cgi.cse.unsw.edu.au/~exam/23T3/seating/register.cgi). Note that this is due by this Friday at 10pm AEDT, but that it is first come first served. Also note that if you do not care about which session you're in, you don't have to submit this form - the default option is no preference.
Do note that this is just to pick a session - the actual time (should already be accessible on myUNSW when it comes back online) and more importantly place will be released later.
All the best for students in our final week of term, and just a reminder to attend an in-person lab for the sample exam , so that you can play around with the environment and see some examples of the style (not number or difficulty) of questions you can expect in the exam.
Welcome to the end of Week 9 everyone! There's just one last push left in the course. Here's this week's notices.
Congratulations to most people for submitting for Assignment II! For anyone still working on it, a reminder that we won't be accepting submissions after 5pm on Friday 17th November . This includes ELS and spec cons cases.
Your marks for Assignment II will ideally be released near the end of Week 11.
Assignment III is of course underway! If you are choosing to work on it, we are continuing to provide support, especially on the course forum. Of course there is no pressure to work on it, since it is only worth bonus marks - if you are struggling to make it to the end of this term, I'd recommend ignoring it completely and just focusing on the exam instead :)
MyExperience is now open! It's really important that you fill it out: a lot of the recent changes in this course have been directly because of myExperience feedback but we are constantly looking to improve, and any nice comments can really make your tutor's term ๐๐
A reminder the sample exam will be held next week during lab time! You will need to attend an in-person lab to complete the sample: you will be given a special login by your tutor to let you access the exam environment on CSE machines.
The full paper, plus sample solutions, will only be publicly released on WebCMS at the end of Week 10, so everyone is encouraged to attend next week.
Please also note that the sample exam's format and style of questions will be the same as the actual exam, but the difficulty does not necessarily reflect the difficulty of the actual exam.
A special shoutout to our tutor team who have collectively answered over 2100 questions on Edstem this term! + certainly many more in class and help sessions๐ฅณ๐ฅณ
I'm sure that you all have a busy Week 10 coming up, so keep up the good work. We're in the home stretch! ๐
Hi everyone, Assignment II is due soon! ๐ Again we have a low number of submissions so here's a gentle reminder that you should be submitting intermediate copies of your assignment on Give, to avoid the last minute rush! We won't be taking submissions on Gitlab (no exception).
It is also your responsibility to check your dryrun output . If your code doesn't compile and it was clear from the dryrun that it would not, we won't waive the rerun penalty.
EDIT: The link to the dryrun tests is https://cgi.cse.unsw.edu.au/~cs2511/dryrun_ass2/ if you want to see what we are testing.
On a separate note, if you have applied for Assignment I rerun, those marks have been processed and are up now :)
Hi everyone, glad you've made it to the end of Week 8! Hope you all are holding up in this rainy weather ๐ง๏ธ
This week's updates:
Assignment III is out - the spec and repos have been released! Your groups are the same as your Assignment II groups unless previously discussed with your tutor - if you want this to be changed please contact your tutor ASAP. You may also choose to do it as an individual if you prefer. The marking criteria is different for individual vs pair so make sure you have a read of the spec!
This assignment is worth
5% bonus marks
(i.e. marks to catch up on other assignment marks only) so if you don't do it you won't be losing any marks! It's due
Week 10 Friday, 5pm
, though no late penalty will be applied on submissions until
Week 11 Tuesday, 5pm
(21st November).
Your Week 10 lab will be dedicated to a sample exam . This is not worth anything, but is to allow you to gain familiarity with the exam environment on the CSE machines, and experience some practice questions. We strongly recommend you attend this sample exam or you may be at a disadvantage for the final exam (e.g. technical issues).
If you are in an online tutorial , you should attend an in-person lab for the sample exam. Contact the tutor of that class if you have any questions about attending :)
Assignment II is due Friday Week 9 5pm . Thanks for all your good questions on the Course Forum so far!
Remember now is also the time to make use of Help Sessions before they get inevitably more full before the assignment due date. Our final sessions before the assignment is due are on next Wednesday so make sure you have any questions ready.
Assignment I rerun requests close this coming Monday at 11:59pm. Remarking will be released for those cases soon after.
Lots of notices this week but I recommend you keep your eyes focused on Assignment II for now. Good luck, see you all in Week 9!
Hi everyone!
Assignment 1 marks have been released to all - you can view it on the give system , or by running:
2511 classrun -collect ass1
on CSE servers. Note that there are still a few assignments which are yet to be marked - those will be marked in the coming days and then released. Your tutor should have emailed your class saying that your class is affected as such.
That information will contain a list of all the tests and whether you passed or failed them, as well as your design mark breakdown. Do note that despite it being called 'style', the design mark is still the design mark. One other thing to note is that code quality is out of 2.5 , not 5. The other 2.5 marks are already integrated into your 'performance' mark - if you passed linting you got the 2.5 marks. Please ignore the informal criteria there which lists it as out of 5.
That breakdown does not contain comprehensive feedback however. You can expect to see it in a file called feedback.md in a branch called feedback in your repository, though this may change from class to class - your tutor will advise your class if your feedback is kept elsewhere.
We have integrated all extensions into your mark itself - you can safely ignore the L.
If you feel you have a small mistake which requires a change of up to 20 lines, you can fill in this form to apply for a rerun. Note that in all cases there will be a penalty of 20% applied to the new performance mark. This includes if your code didn't compile beforehand. Note we will not accept dryrun requests after the 6th of November 11:59pm AEDT.
No. The marks are not final. They are subject to change based on plagiarism checks which will be conducted in the coming weeks.
You can see the marker on give, and can email them to ask for further clarifications regarding your marking. Do not continually email them asking for extra marks or further feedback beyond what they feel is appropriate.
A huge thanks to the tutors for getting the marking done quickly. Hopefully everyone is happy with their marks, and keep up the good work with assignment 2!
Hi everyone! Hope you're doing well, we're back with another week of updates.
Tutors are working hard marking Assignment I, your marks and feedback should be available Monday Week 8. We will make an announcement when this is released.
Assignment II is well underway, we hope you are getting stuck into it!
There have been some minor changes to some wording of the specification since release, you can always check the changelog in readme.md for more information. If you need any extra clarification on intended behaviour, the best place to ask is the Course Forum .
We have also just released submission instructions for Assignment II. An FAQ is available on the Forum. Only one of your group members needs to submit. Please remember we will not be taking any submissions on Gitlab (without exception) so please submit via Give.
Just like Assignment 1, your submission comes with a dryrun . This dryrun is the simplest form of test for each Task 2 section, in order to check that you are following the technical specification correctly. It is in the same format as the autotests we will be running on your repository. We very strongly recommend all groups run this dryrun as you go to ensure your code compiles before submitting .
All groups will probably fail a number of the dryrun tests for Task 2 for the sections you did not complete. This is fine and won't impact your submission.
Your final exam is on the 30th of November and will be held in person. More information on it will be released soon :)
Hope you're having a lovely week! ๐๐
Hey Everyone,
With assignment 2 well underway, we have now made the assignment 2 submission public - it will once again be done through
give
on CSE systems. You can run
give cs2511 ass2 <zip file name>.zip
with the
.zip
file which you can download from Gitlab. Instructions are laid out in the submission section of the spec (
link here
, or in the spec at subheading 5.2).
For a FAQ on submission, please check the Ed Forum ( link here )
Hey everyone, well done on making it to the end of Week 5! We hope you use flexi week as a chance to recharge and do something non-uni related for a change ๐ด
This week's updates:
Well done to most of you for completing Assignment 1! No matter how you found it, we hope you at least found it helpful, and learnt something along the way.
For those of you still working on the assignment, please note no submissions will be taken after next Friday 5pm - anything submitted after this point will be awarded 0 marks. This includes ELS and spec cons cases as well.
Our tutors will be hard at work marking the next few weeks ๐ช๐ช We're aiming to get the marks and feedback back to you by the end of Week 7.
Assignment 2 has been out for a few days now - make sure to have a read of the spec (it's quite long!) and catch up on Wednesday's lecture where we discussed it some detail. We highly recommend you at least make a start to it over Week 6: as you possibly learnt from Assignment 1, good design takes time! It's good to have at least a chew over the tasks you need to do sooner rather than later.
If you have any teamwork issues with your partner, it's important to communicate with your partner and your tutor ASAP to try and resolve it, ideally the week the issues occur. If you leave it to Week 11 there's not much we can do ๐
Lab05 is due Week 7 Monday , but working through it might help with your understanding of the assignment, so it might be good to take an earlier look at it as well.
Help sessions are still running over the break! As always, the schedule is here .
That's it for now, lectures and tutorials resume Monday Week 7.
See you at the end of Week 7!
Hi everyone, with the deadline coming up, this is your reminder to be submitting intermediate versions of your assignment via Give !
We have a concerningly low number of submissions right now. Submitting early lets you run the dryrun on your assignment, as well as lets us maintain intermediate versions of your work in case an issue occurs. It's fine if your submission doesn't compile or pass the submission tests - only the final submission of your assignment will be marked.
Hi everyone, we made it to Week 4! Here's the updates for this week.
Lab 04 is due Week 5, Monday 10am .
Lab 05 is due Week 7, Monday 10am .
Assignment I is due next Friday (Week 5) at 5pm. Less than a week to go ! Make sure to submit your repo via Give on the CSE Systems, there are more detailed instructions on how to do this on Edstem.
We've included a minature test with your submission as a sanity check - this lets you check nothing in your repo breaks our autotests (e.g. putting files in the wrong place, modifying important controller methods) - we highly recommend running this at least once before the deadline . We'll only take your latest submission, so feel free to submit as many times as you want.
Make sure to not leave submitting to the last minute - Give can slow down a bit if too many people are submitting at the same time. ๐ฅด๐ฅด
Our last few help sessions before the assignment deadline are running Monday and Wednesday, feel free to drop in if you need any help!
The Assignment II specification will be released on Wednesday morning on the Assignments tab on WebCMS.
Tutors are in the process of finalising groups - if by Wednesday you still don't know who your partner is please contact your tutor.
There will be an introduction to it in Wednesday's lecture - but don't stress about jumping straight on it! It'll be there waiting for you after you finish Assignment I, and of course after you have a very well-deserved rest. We're releasing it earlier rather than later so that you'll have all of Week 6 to chew on it, and so you can bring any questions to the Week 7 Monday lecture.
We're now in the second phase of the course - Design Patterns! Think of these as tools in your toolkit - both in Assignment II and forever after in your software career.
The
Monday Week 04 lecture
, as previously mentioned, is available below. It addresses two essential topics:
Refactoring
and
Functional paradigms
. Please
view
the lecture
before
your tutorial/lab for week 4. If you have any questions, feel free to bring them up during our lecture on Wednesday.
Hi everyone, we're wrapping up week 3 - time really flies!โ๏ธ
Just a few updates from us:
This coming Monday is a public holiday! There is no live lecture on Monday - we will make up the course content later in the week.
Lab03 is now also due Tuesday Week 4, at 10am.
Many of you have tutorials on the Monday - your tutor should have emailed you with other arrangements.
Assignment I has been out for a while - if you haven't started, you should try get on it soon! It's due 5pm on Friday Week 5 .
We'll be providing specific instructions on how to submit your assignment sometime early this coming week.
Of course, we have plenty of tutors staffed on help sessions and on the course forum if you need extra help :)
Lab marks are starting to be released, and you can access them via give . The lab marks are updated daily so if they are showing as `.` then it means you don't have a mark in the system yet. If you have any questions about your lab marks, please email your tutor and lab assistant.
Weโve covered the foundational elements of the course โ OO Concepts, some fundamental programming patterns and Design Principles. We now move into the wide and wonderful world of Design Patterns starting next week.
Enjoy your long weekend, and see you in week 4! ๐ป
Hey everyone! Now that lab marking is in full swing, a reminder that we have help sessions running regularly - you can check out the schedule here (and at the bottom of the WebCMS sidebar). If you need help outside your lab hours or just have a burning question make sure to drop in.
Remember that we're here to support you! This time of term tends to be more free compared to weeks that assignments are due, so now is an especially good time to ask away :)
Hi everyone, just a few short updates this week!
Assignment 1 has been released - it's great to see so many of you getting stuck into it! If you haven't already, we recommend getting started on it over the next few days (or at least sooner rather than later), since a lot of the thinking and figuring out how the pieces fit together takes time.
There's also an Assignment 1 FAQ on the forum which we will keep adding to, and of course we have help sessions and the forum in general if you need any extra help.
Next week weโll be covering some more concepts that will be useful for the assignment - we'll be going over some core Design Principles as well as JUnit testing in the lectures, and UML diagrams in the tutorials .
Next week in the labs your tutors will give you the chance to start forming pairs for Assignment II. Your partner must be from the same lab as you. We always try to take your preferences into account and your tutors will do their best to make things work, but we can't guarantee everyone will get their preferences :)
As always, if you have any feedback on the course, we're open to it - just send an email or make a post on the forum.
Enjoy your weekend and see you next week! ๐
Welcome to the end of Week 1 everyone! This is the first of our weekly end-of-week notices. Hope you're getting settled into the course and getting familiar with the way things work around here :)
It's important for you to try to attempt as many labs as you can since it's some of the foundational learning for this course - if you're struggling, or if you have issues with setup, please go to a help session or post on the forum as we'll be able to help you out!
That's it! Enjoy the rest of your weekend - up next we're jumping straight into Week 2 content and Assignment I. ๐๐
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/23T3/ .
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 , on Monday, September 11, 2023! 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 Monday
, September 11th! The location and link are listed under
COMP2511 Lectures (in Person/Online)
.
Twenty-three passionate tutors, the Admin team (Alvin, Sai, Carl, and Amanda), and I are looking forwards to seeing you all, in person or online! We're all looking eagerly to the start of the new term next week.
Cheers
Dr Ashesh Mahidadia
LIC, COMP2511 (23T3)