Hey everyone!
Short announcement this time. Here's the recording for the revision lecture: https://youtu.be/M7piga1K0dE
Other than that, we hope exam preparation is going well!
We've done it! We've made it to the end of term! Congrats to every single one of you for making it through this term! As you finalise assignment 3 and begin prepping for the exam, here's a few announcements!
As mentioned last week, we have a revision lecture coming up this Tuesday from 2-4pm in Ainsworth G02. As this is only an in person lecture, try make it in person to see our wonderful admins solve some problems in the same style as your exam, and to ask any burning questions you have. If you can't make it though, don't fret - we'll put up a recording after it's done for you to view!
A quick final reminder to complete myExperience - it's still open for a few more days this week, and it's a great way to give us any feedback which we will look at and respond to for coming terms!
Assignment II marking is now underway - final marks will be released around the end of Week 11. In the meantime, all automarking logs and results have been released and are viewable on the automarking branch on your repo.
Similar to assignment I, we'll be accepting reruns for compilation issues or small issues which led to lots of automarking tests failing. We will only accept patches with at most 20 lines per task changed excluding imports, tests and config/dungeon files (note that a line addition and deletion on the same line will count as 1 line). This rerun also carries a 20% penalty, but it only applies to the specific tasks in task 2 which were affected - you will need to indicate which tasks you need tests rerun for, only those tests will be rerun and the penalty will apply to only those tasks. For example, if you only need to rerun your snakes task, we will run those tests and apply a 20% penalty to those tests only - other marks will remain unchanged.
To apply for a rerun, fill in this form - not following the instructions in the form will lead to your rerun not being run with no opportunities for another rerun. The deadline for rerun applications is Sunday 24 November 11:59pm . Penalties will not be waived unless the reason for the rerun is not your fault.
For assignment III, a quick note that whilst the official deadline has passed, there are no late penalties up until Tuesday 5pm. There is also a 7 day hard deadline after which submissions will not be accepted (except for specific cases who know who they are) - this deadline is Week 11 Friday 5pm .
Finally, we've compiled a list of resources we recommend going through during exam revision!
By attempting these, you'll be set for a good time with the exam!
And that's about it - we hope you have a productive (but not stressful) stuvac period, and wish you all the best with your preparations π«‘!
The supplementary exam for COMP2511 (Term 24T3) is scheduled for Tuesday, January 21, 2025. If you are approved for the supplementary exam, you must be available to take it in person on Tuesday, January 21, 2025.
Please be aware that you can only take the supplementary exam if it is approved by the special consideration unit. If your special consideration application is not approved, you will not be eligible to sit for the supplementary exam.
Hey everyone,
Almost done with content! We've got just one more week before stuvac and exams, with plenty of announcements for the week!
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 - there are more details in last week's announcement and the assignment spec. 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.
All assignment I reruns are now completed - your marks are updated on give, and there should be an extra commit on your automarking branch with the rerun logs. If your mark didn't change, we took the old mark as it was higher.
myExperience is now open! Please do complete the questionnaire, as your feedback directly leads to changes in the way we run the course from term to term - we do in fact read all the responses! I'm sure your tutors would also appreciate any feedback on their teaching, either nice comments or constructive criticism!
As mentioned in last week's announcement, we'll be running a sample exam this week in in-person labs only - online students are free to join any in person lab to give it a go. The environment we provide is not the default CSE lab environment, so playing around with the environment is a good idea! The full paper will be released at the end of the week, so you'll still be able to revise content using it even after the sample exam.
Do note that the sample exam has the same format and style of question as the actual exam, but the difficulty and number of questions may differ.
Finally, we'll be hosting a revision lecture on Tuesday Week 11 from 2-4pm in Ainsworth G02. While there won't be an online stream, it will be recorded so don't worry if you can't make the time.
And that's about it from us - one more week to power through and then you're in the end zone! We'll see you on the other side π«‘
Hey everyone,
A quick announcement to let you all know that we've moved this Friday's online help session to an in person one from 10am to 12pm at Old Main Building 151. This has also been updated on the Help Sessions page on WebCMS!
Other than that, we hope assignment II is going well! A few more days to go!
Hey everyone, we've got a fair few announcements this week!
Assignment III has now been released, with both the spec and the repo available to you (and can be found on the assessments tab on WebCMS3). Your groups are the same as in assignment II unless you have indicated that you would like a change, or if your assignment II group was a group of 3. To see who exactly is in your group, you can check the members of your repo. If you'd like to change your groups or do it solo, contact your tutor ASAP and they can change your group for you.
The assignment is worth 8% bonus marks (which can only catch up on marks lost in other assignments, not labs or the exam), so not completing the assignment won't lose you any marks. It is due Week 10 Friday at 5pm Sydney time, though no penalty is applied until Week 11 Tuesday at 5pm . Submissions won't be accepted after 7 days past the original deadline i.e. after Week 11 Friday at 5pm.
We will also be briefly going over the assignment spec in tomorrow's lecture, so stay tuned for that!
In the week 10 lab, we'll be running a sample exam for you to gain experience with the exam environment. This is not worth any marks, but it is useful to gain familiarity with the system so you spend less time in the exam acclimatising and more time working on the exam. It will also enable you to look at some questions which will mimic the type of questions you'll see in the actual exam (the number and difficulty of questions may differ).
Note that the environment is only present on the CSE computers, so if you are in an online tutorial, you will want to attend an in person lab for week 10 - any such tutorial is fine.
Assignment II is due this Friday at 5pm . A reminder that no late submissions are accepted for this assignment under any circumstances . If you have ELS provision which apply to the assignment, email the class account and we'll discuss other arrangements.
And, as always, feel free to hop in a help session or ask questions on the forum - we've got plenty of support in both regards!
A gentle reminder that the rerun form for assignment I will close this Wednesday at 11:59pm. All requests will be run shortly after.
Lots coming up these next couple of weeks - knuckle down for a couple more weeks, and we'll see you on the other side π«‘
Hey all! Week 8 is now upon us - hopefully everyone's underway with assignment 2, and things are going smoothly!
Assignment 1 marking is almost done, and should be released over the coming couple of days on
give
. Feedback should be released by your tutors over the coming days as well - this will most likely be on Gitlab, either as a new branch, a merge request or an issue on your repo. Your tutor will let you know if it's none of those options. Automarking results will also be pushed to your repo under the
automarking
branch for you to review. 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 11:59pm on 06/11/24, next Wednesday, and that all rerun requests will be run shortly after that date.
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 1 - regardless of your marks, we hope you have gained something from this assignment and have a better understanding of your design principles and how to apply them!
A quick reminder that assignment 2 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 - 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!
Due to a mix up on our end, the spec for lab07 incorrectly states that it is due Tuesday i.e. tomorrow - this will now be the actual due date, as it would be unfair to people who only saw the spec deadline not to extend it.
Other than that, we hope you enjoy some exciting new content in the form of generics and the singleton pattern!
Hey all,
Hope you had a restful and/or productive flex week! We only have a few announcements this week, and they all are regarding:
Now is around the time where everyone should be beginning to look over the spec and make a start on the assignment, if you haven't already. To help with familiarisation, we will be having a discussion of the assignment spec and requirements of the assignment in Tuesday's lecture . Feel free to come along with any questions you have about the spec or the codebase!
As a reminder, if groupwork issues arise whilst working on the assignment, please flag it to your tutor as soon as it happens - we want to resolve all issues as soon as possible so you can continue working on the assignment as smoothly as possible. It also gives us a paper trail to refer to when finalising resolutions later in the term.
I'll also quickly shout out that, similar to assignment 1, assignment 2 has a dryrun - check the spec for further instructions, but in general it should be very similar to assignment 1 in terms of how it's run. There are differences in what is tested though, which are outlined in the spec.
Finally, there are still tutors manning the forums, and plenty of help sessions over the coming few weeks - make good use of them! The forum also has an approved assumptions/FAQ thread pinned, which you can use to check if something you're unsure of has already been answered!
That's about it from us - we'll see you over the next few weeks as we continue and finish design patterns, and move onto some other closing topics for the term.
Hey all!
Congrats on making it to the halfway point of the term! We've got flexi week next week, so make good use of it to rest up, catch up on course content (for this and any other courses you are doing) and relax a bit π
Congratulations on finishing assignment 1! No matter how difficult you found it, you should be proud of your efforts and your application of OO principles to your code!
For anyone who's working into the weekend and flexi week, please remember that no submissions will be accepted after this Friday 18th October at 5pm Sydney time. This includes all special consideration cases and most ELS cases (you'll know if you're an exception).
Our fantastic tutors will be busy marking your assignments over the next couple of weeks π€©. Marks and feedback should hopefully be released by the end of week 7/beginning of week 8.
Assignment 2 is out! The spec and repos are out, and can be found in the assessments tab on WebCMS3. We recommend reading over the spec and looking over the codebase over this coming week, and potentially beginning some of the first few tasks if you have the time and are feeling especially relaxed or up to the task. As with assignment 1, developing a good design takes time, and this is truest when working with someone else's codebase. Even just looking through and noting entities, relationships and how functionality works is well worth the effort this week - that will certainly take longer than expected and save you a ton of time in the future.
Assignment 2 is also a pair project - we're well aware that teamwork issues can crop up. If they do, try communicate the issues with your partner and see if they can be resolved internally. If the issues persist, please let your tutor know as soon as it happens - telling them the week the issue arises is the best option. This puts us in the best possible position to try resolve it early and as amicably as possible. Leaving it to week 11 when there are no more opportunities to talk in person and discuss the issues will make everyone's life harder.
Last week I incorrectly mentioned that lab05 was due week 7 Tuesday - it is actually due Week 7 Monday at 10am. That has been corrected on the old announcement now and has always been correct on the spec.
We also have help sessions and the forum running throughout flexi week as well for any questions you may have!
That's about it from us - enjoy your flexi week, and we look forward to seeing you back in week 7, hopefully more refreshed than we left you π
Hey all! Only a few announcements, but some big ones - make sure to read them in their entirety!
As we reach the mid-way mark of the term and flex week, lab due dates can get a bit muddled, especially this term with the public holiday. As a quick reminder, Lab04 is due Week 5 Tuesday at 10:00am and Lab05 is due Week 7 Monday at 10:00am . From there, Lab07 and Lab08 will follow after Lab05 in weeks 8 and 9 respectively.
We're in the final week of assignment 1! It's due next Friday (Week 5) at 5:00pm Sydney time. Remember submission is done solely via Gitlab - just push to your main branch (no other branches will be accepted). We only look at the latest submission, so feel free to push as many times beforehand as you see fit.
Similar to COMP1531, the Gitlab pipelines have the potential to slow down a lot during the submission period, so try to submit early to avoid the issues. If you do encounter slow pipelines while submitting, you can test your linting and tests locally as a substitute for the pipeline to check your code is passing. Note that slow pipelines are not a valid reason for any leniency.
In anticipation of the deadline, we've got 7 help sessions from today till Friday, so drop into any of them and get any assignment help (or any other help for that matter) you may need! The schedule can be found on the help sessions page on WebCMS3.
One final reminder - the CSE server and Gitlab dryruns are both available for use as a quick sanity check and check that your code will compile with our tests ( they are not exhaustive ). More info is in the spec .
Assignment 2 is next! Group organisation should be wrapping up, with your tutors already having given you your pairings, or giving them to you in the coming few days.
The spec will release on Gitlab in the same place the assignment 1 spec can be found ( here ) and on the assessments tab on WebCMS3. 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 1 deadline has passed.
While the spec will be up for a few days before assignment 1 is done, don't feel compelled to begin immediately. Take your time finishing assignment 1 first, and once you're happy with where it's at and you submit, you can move onto assignment 2. We're just releasing it early so you have the time to look over it in Week 6 and potentially make a bit of a start, not because you need to begin that early. With a deadline of Week 9 Friday 5:00pm Sydney time , you have plenty of time to finish assignment 1 and have a bit of a break during flex week if you would like.
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, and enjoy the long weekend!
Monday, October 7th, is a public holiday, so we will miss our face-to-face lecture. Please watch the following three videos (from 24T2) covering three patterns before the Tuesday lecture. At the start of the Tuesday lecture, we will discuss any queries/doubts you may have about the following three topics.
Week-5 Monday video lecture:
Hey everyone!
Another week down! Here are the announcements for the week π
It's great to see so many people have begun assignment 1 and are making their way through the tasks! If you haven't yet begun on the assignment, now would be a great time to start! As a reminder, it's due 5pm Friday of Week 5 , just under 2 weeks from now.
Also a quick shout out to the dryruns available on CSE servers, as well as a manual job on all Gitlab pipelines in the assignment repo - further instructions on how to run them are present in the spec. This dryrun runs some very basic autotests which check that your code will compile with our tests - it does not test functionality. If you're unsure why your dryrun is failing, you can check the contents of the tests in this link . As the dryrun ensures compilation with our tests, we recommend running it often, and well before the deadline, so that you can be sure your code will be properly tested.
In other assignment news, over the next couple of weeks, there will be a lot of help sessions for you to attend and ask all sorts of questions, and forum questions will be regularly answered thanks to our remarkable tutors who work tirelessly to help you! There's lots of support available to you, so make good use of it!
Lab marks for the previous couple of weeks should be accessible on give - every lab you get marked with a tutor will show up on give within 24 hours of you having marked it off. If you see a '.' for your labs, that lab hasn't been marked off - if you think it should've been marked, email your tutor .
Assignment 2 pair creation should be well underway, and will be finalised by the end of this week, so make sure to give your preferences to your tutor however they told you to do so! Just another reminder that this assignment can only be completed in pairs (with one group of three in classes with odd numbers of people) and that groups must come from the same tutorial i.e. you can't pair with someone from another tutorial. We will not waive these rules under circumstances.
Over the past three weeks we've covered the foundational parts of the course - the fundamentals of OO design, design principles/code smells, design practices and testing. Now that we've got a good base to work off of, we're transitioning to the design pattern section of the course, starting with the strategy, observer and state patterns this week!
Hey all,
Hope week 2 treated you alright! We've only got a couple of announcements this week:
Both the spec and actual repo you'll be working in have been released for assignment 1, and can be accessed via the assessments tab on WebCMS! It's great to see some of you have already begun sinking your teeth into it - if you haven't already, we'd highly recommend getting started early as fully understanding the requirements and executing them with good design takes a while - much longer than you'd 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 tutor will begin organising assignment 2 pairs, and will explain what their process for pairing you up is. Please note:
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 π«‘
Hey everyone!
Week 1 is over! We hope you enjoyed your first week back at uni, meeting old and new friends as well as the course staff! Hopefully setup issues were few and far between as well, and you found the first lab doable.
Each week, we'll be doing one of these announcements here on WebCMS. They exist to remind you about things coming up the following week, as well as to keep you in the loop regarding any course related info or updates. With that being said, let's get into the announcements!
At the end of each week, we will release solutions and a recording for the tutorial that week. The first of these solutions and recordings are now available on the tutorials page .
Lab01 is due Week 2 Monday at 10am . All students must push (not just commit) their code to Gitlab by the deadline each week , as mentioned in the instructions in the read me file. There are no late extensions for labs, and failure submit on time will mean your lab will not be marked .
If they haven't already, your tutor and lab assist will be manually marking them over the next two weeks in your labs , so make sure to attend! This is also outlined in the course outline, but after these two weeks, we will not mark your lab without good reason, so don't delay marking them off!
Please also attempt the labs sincerely - they give you a good opportunity to exercise the content learned in tutorials that week, which will be assessed further in the assignments and final exam. Finishing all the labs and properly attempting them with the intent to learn should set you cruising to pass this course easily π
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 rife with setup issues, as well as some questions stemming from unfamiliarity with Java. These questions may be hard to solve by yourself, so if you're having such issues, please hop in a help session or post a question on the forum . Our amazing tutors are friendly and knowledgeable - a killer combo π€©!
And with that, we're done with the announcements this week! Enjoy the rest of your weekend, and we'll see you next 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/24T3/ .
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
12:00 noon on Monday
, September 9th! The location and link are listed under
COMP2511 Lectures (in Person/Online)
.
30+ passionate tutors, the administrative staff (Alvin, Sai, Amanda and Carl), and I are excited to start the new term next week.
Cheers
Dr Ashesh Mahidadia
LIC, COMP2511 (24T3)