Hi everyone,
Your iteration 3 marks and comments have been made available to you on the sturec page of Webcms3.
These include:
Note that the iter3_automark and iter3_manualmark are the marks BEFORE adjustments and BEFORE penalties (late). So, there is nothing wrong if your iter3_finalmark =!= iter3_automark + iter3_manualmark. iter3_bonus will be added to your overall project mark. More details about your automarking result has been pushed (on last Saturday) to your repo on a branch that is called iter3-results.
It's important to remember that these marks are tentative, and whilst very rare, are still subject to change as new information comes to light. Furthermore, there are still some tutors marking classes (they should have emailed you). If there are issues with your project mark, please reach out to your tutor. Whilst their response won't be necessarily quick, we will be thorough.
If you would like to talk to your tutor about reruns (as per spec) for major project, you have until the end of Sunday the 20th of August to produce the new commit and email your tutor the branch name that you'd like to re-run. This is the cut-off for re-runs for T2. This doesn't mean they have to have it resolved by the end of Sunday night, but we need you to at least start the conversation.
Good luck for everything!
Hi everyone,
Please read this notice.
For your take home assessment tomorrow, we will communicate with you via EdStem forum posts. An example post is here . If you have not already signed up to the forum, please do - we will need you to. We will not communicate with you via Webcms3 notices.
All EdStem forum posts will be also delivered as an email to your UNSW email inbox. If there are issues with EdStem we will email you directly via your UNSW Email.
Your final assessment begins at 12pm tomorrow . We will notify you when it starts with a link to the spec. Please do not ask about where to find the take home assessment link before then - it will not be available until 12pm. The link will give a 404 in the meantime. DO NOT spam refresh the page at 12pm - we don't control the gitlab servers so can't do much if people overload it.
We have also rolled out your personal assessment repo . Remember, we release the SPEC to you tomorrow at 12, but you actually complete your work on your personal assessment repo! This distinction is really important, so please take a moment to familiarise yourself with the sample spec we provided.
If you have any other questions, please post on the forum.
Yuchao & Hayden
Hi everyone!
Huge congrats to those who have submitted their iteration 3! It's a big achievement 🏆. For those who are still working on the project, please make sure you look after your well-being 🫶.
It's been incredible seeing everyone pick up the work and tackle the challenge. The term has flown by. It's crazy how much you've all managed to learn this term.
Everyone is
required
to complete their peer review for iteration 3. This is invaluable feedback for your tutor to track how your group is performing together. You need to complete this by 9am Monday 7th August!
Now that iteration 3 is done, some reminders about what is next:
Have a great weekend - Rest easy, it's been a long week. 😊
Hi everyone,
We have just rolled out a merge request to your project repo that includes a new route to the swagger that we'd like you to implement for iteration 3. (see image below)
🧠 Why was this only just included?
This has been in the spec since before term, however , an administrative error meant we accidentally removed it whilst trying to sort out git across many iterations. It's just human error.
🔥 Why you shouldn't stress
This is a very easy route to implement. It has no error conditions, and basically just returns sets of data you already have directly or indirectly. It should be extremely manageable - but if anything is stressful our team of tutors are here to help you out.
Please also note that:
Thanks all!
🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒🦋🦒
Hi everyone!
We're wrapping up week 9 - keep your heads down and keep focused. No more new content. One tutorial. Make this weekend count, and keep steady next week. Updates below:
The take-home exam will be in the form of a mini-project (like a project assignment). There is no hurdle for it. It will be due on the Friday of week 11. Have a look at the announcement on our forum for details on duration, structure, platform to complete the mini-project, communication & help during the project and preparation.
Filling out MyExperience is one of the most helpful things you can do for the teaching team in COMP1531. We really wish to listen to and capture your experience with the aim of understanding and acting upon it. The higher the response rates, the more robust the insights for us.
⚠️ ALSO!‼️ For every 5% that we score over 50% response rate, we will add 1 extra hour onto the mini project!! Maximum extended to week 11 Friday (11 August) at 19:00! More details are on the forum announcement .
Some key updates and reminders for you:
Iteration 3 is due on Friday of week 10. Super soon. Good luck - you'll figure it out. Make good use of the help sessions, forum, tutorials and labs. We will do our best to support you.
We will be running the leaderboard on the Monday, Wednesday, Friday of week 10. Don't forget we will take the commit you made at around 10pm the night before leaderboard runs, so if you want it run on that day commit it in time!
Have a great weekend - so close! 1 week to go until the bulk of it's over :)
Hi everyone,
Welcome to the end of week 8. Things are starting to wrap up soon! Your last lab is about to be submitted, the tutorials start to get quite light, the lecture content is also quite light. Buckle down and get through the next 14 days and we'll be there in no time.
Some key updates and reminders for you:
Your iteration 2 marks and comments have been made available to you on the
sturec page
of Webcms3. If you have any follow-up questions about your grades after this time, please email your tutor directly
.
More details about your automarking result has been pushed to your repo on a branch that is called iter2-results. If you would like a re-run (as per the spec) you must start this conversation with your tutor within 7 days of the results
release.
It's important to remember that these marks are tentative, and whilst very rare, are still subject to change as new information comes to light.
The final exam will be a take-home exam that takes a couple of days in week 11. It will be an individual-based mini-project. It will be independent of your major project. We will talk more about this take-home exam with more details in week 10.
Only 2 weeks to go until you've completed 70% of the course. You're on the home stretch, and the best part about this period of the course is you're more equipped than ever to tackle the challenges in front of you. Let's keep going.
Hi everyone!
Congrats on submitting your second iteration :)
Some key updates and reminders for you:
Everyone is
required
to complete their peer review for iteration 2. This is invaluable feedback for your tutor to track how your group is performing together.
You need to complete your peer review by Monday afternoon of week 8.
Iteration 3
will be released tonight (Sunday)! Similar to iteration 2, you have 3 weeks to complete it before it's due.
Iteration 3, for most of you, will be a tone-down from iteration 2. It will be a chunk more work to do, but with a much smaller set of new concepts.
On Monday, we will talk about code coverage and start discussing requirement engineering. During Wednesday's lecture, in addition to continue talking about requirements, we will explain iteration 3 and have Q&As.
We're getting closer to the end of the journey.
We hope your flex week is going well. Very straightforward update this week.
Iteration 2 is due on Friday of week 7. One week! Keep working and use the course staff as necessary :)
We will be running the leaderboard on week 7.
Remember to check it out! You will need to select iteration 2 from the drop-down next week.
We rearranged the lectures so that you can focus on your iter2 this upcoming week. 🍻
We will be talking about code coverage in the week 7 lecture. :)
Enjoy the rest of the flex week(end)!
Hey everyone!
Congratulations for making it through to the end of week 5. Flex week is right around the corner! We're excited for you all to have a week without any classes. When we chatted to the tutors on Friday they were all quite impressed in general with your performance so far.
We will also remind you of two things:
Some key updates and reminders for you:
Your iteration 1 marks and comments will be made available to you on Webcms3 by 10pm tonight (Friday). If they are not available, your tutor should have emailed you with an update.
Your marks will be able to be found on sturec . If you have any follow up questions about your grades after this time, please email your tutor directly.
More details about your automarking result will be pushed by tomorrow late evening to your repo on a branch that should be called iter1-results. If you would like a re-run (as per the spec) you must start this conversation with your tutor within 7 days of the results release.
Stay safe and stay well everyone!
Hi everyone!
Iteration 1 is due tonight. Congratulations to everyone for their amazing work. We've seen some tentative marks and a lot of groups have done very well. For the groups that struggled a little more, keep your chin up and take on the lessons for the next iteration. The last two iterations of the course are 3 weeks instead of two. That breathing room will help.
Don't forget to catch up and make sure you're on top of the
week 4 lectures
by end of weekend.
We'll give you the quick last for the lower-attention-span people:
Some key updates and reminders for you:
Everyone is
required
to complete their first peer review for iteration 1. This is invaluable feedback for your tutor to track how your group is performing together.
We have extended the
peer review deadline is
5pm
on Monday the 26th of June (week 5).
You have a few days to complete the survey. It should be quick.
Iteration 2 will be released by Sunday at 5pm . Keep an eye out for it and get started next week.
Remember that iteration 2 is where you will need topics from lectures:
Advice is to start iteration 2 early next week. The very beginning of it (particularly in adjusting to Typescript + Linting + HTTP) will feel like a hurdle. But just focus on getting over that hurdle so that you can get into the more interesting stuff.
We are having a bonus lecture on Monday at 6pm about iteration 2! You can find the link HERE !
We're investing extra into this lecture this term to really step through the new project's iteration 2 to provide you with as much support as we can. We hope this guidance will be helpful in getting underway.
It will be online only. And yes, it will be recorded. And it will be available on the lectures page once done.
Your iteration 1 marks will be released next Friday!
A reminder that this weekend (Sunday) is the last day you can drop the course and make it as if your enrollment never happened. If you do drop the course just shoot your tutor or team members a quick email letting them know (1 minute of your time saves everyone a bit of pain). Since you've dropped right after an iteration everyone will be fine and tutors figure things out :)
Other than that please have an amazing weekend and look after yourselves! Stay steady, we still have a bit of term to go.
- Yuchao & Hayden
Hi everyone!
Congrats on the end of week 3. Nearly a third of the way through the course. Keep it up!! It's been so fun for us to hang out with you and learn together this term :)
During week 4 both of our lectures will be ONLINE
This is reflected on the lecture timetable page .
Your lab02 has been marked, and your marks can be seen on sturec .
Your mark has been awarded between 0 and 1. If your mark appears as "-0.1", it is because there was an error whilst marking (this could be our problem or your problem). This is just a place holder mark. You have not gotten negative marks. It's kind of like a "null" We're still double checking a number of these "-0.1" cases so if you got this please check again on Sunday morning as it may be fixed.
You can read our detailed info about looking at your lab marks here - this is a very useful guide !! If you have any issues you can follow up with your lab assist in your lab time during week 4.
Your iteration 0 marks and comments have been made available to you on sturec . If you have any follow up questions about your grades after this time, please email your tutor directly.
We will be running the leaderboard (described in the spec) to have your tentative marks available on Monday , Wednesday , and Friday of week 4. The leaderboard will be updated around lunchtime - assume at 12pm. We will not be running the leaderboard more often and won't be doing individual re-runs for students. This is a new initiative of the last 12 months that is aimed to give you more support by giving you an indicative of your progress without telling you exactly what is wrong (which would undermine the nature of the assessment).
You will be able to access the leaderboard here on Monday (before then it might have a 404 error).
In terms of lecture content next week:
See you Monday!! :)
Hi everyone!
We hope you've had a great end to your second week! Lots of positive stories are coming my way from tutors who are enjoying the groups in their classes. Congrats on submitting iteration 0, and you can take a little bit of a breath this weekend before things start to progressively pick up next week. We know it may feel like a lot sometimes, but we'll get through it. Our teaching team is excited to support you!
Some key updates and reminders for you:
Iteration 1 will be released on Sunday at 5pm. Keep
an eye out for merge requests in your project repo. An introductory video is contained in the spec. Take your time reading the spec and watching the video, as it will all be very helpful in getting started.
Iteration 1 is due on Friday, 23rd June ( week 4 ), so you have around 2 weeks to complete it.
Now that you've seen the week 2 lectures, we expect to see engagement with standups, meetings, task boards, etc from everyone between now and iteration 1 is due.
Your lab01 has been marked, and instructions on viewing your "theoretical" marks can be found here . Remember, these marks don't count for anything! It was just a trial run.
You can read our detailed info about looking at your lab marks here - this is a very useful guide !!
In week 3, we will learn about continuous integration (an exciting and critical part of software engineering) and touch on a lot more static verification. These are exciting topics.
Next Monday's lecture is online due to the public holiday. Enjoy your weekend :)
Hi everyone!
It was great meeting you online and in person! Now that we're wrapping up week 1, it's a great time to summarise the key things that happened this week and give you some pointers for week 2.
The key things that happened in week 1 are:
During your week 1 class, your tutor finalised your project groups in your lab time.
A reminder that whilst you aren't required to communicate via the Microsoft Teams channel, it's important to note that if teamwork disputes arise or you make claims about other team member's contributions later in the course - the
only
places we will look to for evidence of how you interact with your group are:
If we need to analyse group communication, we won't be able to look at things like Facebook, Discord, Slack, etc., as these are out of our control and are open to tampering etc that makes it unfair to consider reasonable evidence. However, anything in your Microsoft Teams chats we'll happily take into account. If you're uncertain about anything here or aren't agreeing with your group on how to communicate, talk to your tutor in week 2; they will help you figure it all out! :)
If you don't have your group sorted, please email your tutor ASAP.
As of Monday morning of week 2, a group project repository will be created for each group. The repository is called " project-backend ". You can find your group repository (if you haven't already) on the homepage of nw-syd-gitlab.cseunsw.tech. If you can't find your repository, please post on the forum. If you can find the repo, but you're in the wrong group, please email your tutor ASAP.
The project's first stage is iteration 0, and due next Friday night - week 2. It's a
very
easy stage.
You will have 4 days to complete it - but that is OK! It should only take a couple of hours!
Please watch the introductory video from the project .
Next Monday, the most important thing to do is to start messaging or emailing your group members and reading through the project specification. You can sync up about it and start some early planning, and I would strongly encourage you to organise times to meet next week. From week 3 onwards, we will expect groups to follow a more rigid meeting as we move onto the project's next stage.
Over the coming days, there may continue to be slight changes to your group, primarily due to students potentially dropping the course before the census date. Your tutors will always support you and find solutions that will make things OK :)
Other than that, have a great weekend!
Hi everyone! Welcome to COMP1531 23T2 :)
The fundamental aim of COMP1531 is to help you on your transition from being a
solo
programmer
into being a
collaborative
software engineer
. We have a teaching staff team of more than 30. Feel free to i
ntroduce yourself in the forum
and we're all super excited to get to know you!
Hi everyone,
A very early welcome to COMP1531 for 23T2. This early welcome is predominate to give you time to
fill out the
group preference form
below.
A more detailed introduction with information and summaries will be sent out next week, but here are a few things to get you prepped for the term.
As specified in the course <u>outline,</u> COMP1531 has a major project component that is a 5-person, 9-week group project that constitutes 60% of the course assessment. The successful and equitable formation of amazing groups of students for this major project is a priority for us. And we need to finalise these groups before week 1.
For us to form groups effectively, you
are required
to complete the
preference
<u>form.</u>
This form asks you to:
We sadly aren't in a position to accept late preferences, so please fill it in prior to then. Preferences are not guarantees that you will be in a group with that person, however, in nearly all cases we make it work.
If you don't have anyone to preference, or only have one preference, don't even worry! That's very normal. You might hear murmurs from other students that you could end up with a "horror group" for COMP1531. Believe it or not, typically about 50% of student's don't provide preferences, and we just randomly match students in the same class.
We can assure you that while groups that struggle do exist, they only make up a small number of groups. We have structured the course and assessment very intentionally to have processes in place to ensure that if you work hard and follow the rules, your accomplishments should reflect your mark, even if you end up with some challenging group situations.
Lastly, a reminder that we can't manually enrol you in a full class, and we aren't accepting more than one preference per person as this ensures equitable group formation.
We'll reach out again next week with much more information about getting started and first classes!
🎃 Until then, enjoy your week and stay safe. The entire team can't wait to meet you.