Most importantly, I have heard plenty of horror stories and seen a lot of people struggle doing this subject with CSSE2310 at the same time. So, please chat to some older engineers and take their advice. Both of these subjects are very demanding and completely consume your time. ENGG2800 requires you to perform multiple presentations (seminars) and asks you to build a complex device with a random team, which initially seems completely out of your league. To make things more difficult information about required components and structures is slowly released throughout the semester so there is absolutely no getting ahead, let alone keeping up with your time schedule unless you're an electrical genius. You really learn a lot doing this subject and it is very interesting, but you also have to learn to be incredibly patient waiting to components to be built or delivered etc. The staff also didn't appear to be too helpful. One of my friends had half of his team people drop out before a few deadlines for components were due and these teammates didn't bother passing on any of their work (assuming they did their work). The cherry on top of this was that my friend was given absolutely zero leniency or adjusted weighting etc for their group project, despite my friend having asked for some support. In the end my friend and his now partner had to try to complete 4 peoples worth of work for an entire semester in a ridiculously short time frame. Overall, you should try attending everything to obtain as much information as you possibly can, because this is one difficult course.
I have a love-hate relationship with ENGG2800. On one hand, if you put in an effort, the knowledge you will receive will be enormous and invaluable. On the other hand, it will destroy your will to live.
The course is the first of two team projects in electrical engineering. The learning curve is steep, but by the end you should be proficient at PCB design, soldering with minimal burns, and software/firmware design within hardware limitations. You should also find that sleep is an unnecessary luxury for the weak.
Seriously though, 2800 is time consuming, especially alongside CSSE2310. You'll have to make a strong effort early on in order to get a good result.
At the beginning of semester you'll be given a product spec detailing what you are to present software/firmware/hardware wise. From the vague and sometimes misleading guidelines you have to figure out how to implement the required features. Lecture attendance is a must unless you want to realize in week 7 that you completely misunderstood something and have to frantically redesign to send away PCB's.
ENGG2800 will teach you why peer reviews exist. Your experience in this subject will be largely dependent on the quality of your group. Make sure that everyone knows what is going on with software/firmware and especially hardware. If you are a coder, be prepared to design a PCB and vice versa. I personally ended up coding in C, Java as well as doing the hardware. Anything can happen and damage control is much easier when you don't have to start from scratch.
The tutors are usually helpful, however with the size of the course and the difference in approaches groups will take, you can't rely on them, nor should you. You will spend hours (days) on end looking at the same circuit, pulling your hair out trying to figure out what is going wrong, only to realize it was something incredibly stupid. Coffee is your friend here.
The assessment for this course (At least when I took it) consists of a preliminary design task, a couple of reports, two seminar reviews and the final product demonstration. The preliminary design task should be relatively simple, as should the initial report. The seminar's are basically to show the tutors/lecturer what you have completed or are planning. It is easy to lose marks for timing and slides, however if you have work you show, they shouldn't be too difficult.
The Final product Demonstration, in contrast to ENGG1100 and ENGG1200 makes up the majority of the marks, and you will need to do well here. The way it was marked in 2015 was that the product marking criteria was decided into sections (PCB design, Software, Firmware, Battery Life, Project specific hardware modules etc.).
in addition to getting the required grade percentage, you had to pass every section, as well as complete an advanced hardware/software feature to get a six, and both features to get a seven. You also had to come in under budget to get higher than a 4, which proved difficult while completing the advanced hardware.
This is what will crush your soul.
It doesn't matter how much work you put into your section, if one or more of your teammates drops the ball, there is a high chance grade capping will affect you.
In the end, you will learn a lot of important skills, and because you're not studying for an exam, you won't immediately forget them, you might just end up dying a little on the inside. If all else fails, vent through the form of a review after you scrape through.