Course overview
- Study period
- Semester 2, 2025 (28/07/2025 - 22/11/2025)
- Study level
- Undergraduate
- Location
- St Lucia
- Attendance mode
- In Person
- Units
- 2
- Administrative campus
- St Lucia
- Coordinating unit
- Elec Engineering & Comp Science School
Small teams of students undertake design, implementation, testing, evaluation and presentation of specific project of a size and complexity suitable for novice students.
ENGG2800 (Team Project 1) is a learn-by-doing course that endeavours to teach issues in project management, teamwork, communication and design by giving teams of three or four students the task of designing and building a complete product encompassing both electronic and software design in a structured team environment. The substance of the course centres on the design and implementation of a product to conform to a specification. The design components of this product will be appropriate for a student with second year technical knowledge and pre-requisite course knowledge. A small number of in-person lectures and a video lecture series, encompassing technical and project management aspects are presented/available in the first half of semester. Online resources, and teaching staff guidance are provided within the course in both the practical and background theory relevant to the project. A challenging aspect will come from the requirementᅠto work effectively in a group, operate to fixed deadlines, and demonstrate progress regularly. This course is intended to be both a challenging and enjoyable way to enhance your engineering skills in electronics design and construction, programming at all levels and understand issues of sustainability in a team environment.
Course requirements
Assumed background
Fundamental electrical knowledge, basic digital and analog electronics, software and computer systems engineering knowledge as per prerequisite courses.
Prerequisites
You'll need to complete the following courses before enrolling in this one:
CSSE2010 and ENGG1300 and (CSSE1001 or ENGG1001)
Incompatible
You can't enrol in this course if you've already completed the following:
METR2800
Restrictions
BE(Hons) and BE(Hons) dual/integrated degrees
Course contact
Course coordinator
Course staff
Lecturer
Timetable
The timetable for this course is available on the UQ Public Timetable.
Additional timetable information
Pracs are not mandatory and there is no sign-up or allocation to particular sessions. They are an opportunity for you to get help from the teaching staff and it is expected that you will attend some sessions.
Aims and outcomes
Team Project courses address a wide range of goals for the learner from personal development to technical experience. Working in a team you may be only lightly exposed to some technical skill areas, while deeply developing your abilities in other technical areas. You will be responsible for your learning - choose your areas of expertise and interest in conjunction with your team. The goals related to personal development, on the other hand, are the core learning goals for the course that will relate to every member of the team. During this course you will:
- Experience working in a small but diverse team.
- Practice informal team building skills.
- Resolve conflicts and negotiate solutions.
- Write a report.
- Present a seminar.
- Plan a complex project to a fixed timeline and budget.
- Acquire CAD skills for drafting of schematic diagrams and PCB artwork.
- Acquire practical analog and digital electronics design and construction skills.
- Acquire real world software and firmware design skills.
- Manage your design files and code using a defined procedure.
- Consider aspects of sustainability and maintainability relevant to the project.
Learning outcomes
After successfully completing this course you should be able to:
LO1.
work effectively as a member of a team to design and build a functional electronic product on-budget and on-time.
LO2.
demonstrate specific electronic design and/or software skills required to produce a simple analog and digital system fit-for-purpose.
LO3.
design a simple schematic diagram, produce associated PCB artwork for fabrication and construct a working circuit.
LO4.
effectively use software tools to aid project management, product design, version control and communication tasks.
LO5.
summarise relevant aspects of the product design and design process to technical audiences via a seminar and report.
LO6.
describe issues that should be considered regarding sustainability of the product design.
LO7.
reflect on your learning practices or development process to identify areas for personal improvement.
Assessment
Assessment summary
Category | Assessment task | Weight | Due date |
---|---|---|---|
Paper/ Report/ Annotation |
Team Code of Ethics and Code of Conduct
|
Pass/Fail |
15/08/2025 4:00 pm
As long as the task is submitted on time, resubmission will be possible if a passing mark is not awarded. Details of the resubmission time will be made available to teams individually. |
Practical/ Demonstration |
Individual PCB task (working circuit module on PCB & pdf of schematic)
|
5% (Pass/Fail) |
4/08/2025 - 5/09/2025
Demonstrations during practical sessions only. (PCB manufacturing submissions must be received in pinecone before the beginning of week 4, see pinecone and the task description for details). |
Presentation |
Seminar Presentation
|
10% |
8/09/2025 - 12/09/2025
Presentations will be scheduled based on the availability of participants and suitable presentation spaces. |
Computer Code, Practical/ Demonstration, Product/ Design, Project |
Product demonstration sequence
|
80% |
Week 5 - Demo 1 (Preliminary) Week 9 - Demo 2 (Intermediate) [Any PCBs must be submitted to pinecone before the beginning of Week 11 - see pinecone and Blackboard for further details and exact times. Manufacturing of PCBs will not be possible after this date.] Week 13 - Final demo. All projects are due at 10am on Monday Signup polls will be distributed in the weeks before demonstrations. |
Paper/ Report/ Annotation, Reflection |
Final Report and Reflection
|
5% |
10/11/2025 4:00 pm |
Participation/ Student contribution, Reflection |
Assessment of Individual Performance (Formative/incorporated into product mark)
|
Incorporated into product mark |
25/08/2025 4:00 pm 22/09/2025 4:00 pm 27/10/2025 4:00 pm |
A hurdle is an assessment requirement that must be satisfied in order to receive a specific grade for the course. Check the assessment details for more information about hurdle requirements.
Assessment details
Team Code of Ethics and Code of Conduct
- Hurdle
- Team or group-based
- Mode
- Written
- Category
- Paper/ Report/ Annotation
- Weight
- Pass/Fail
- Due date
15/08/2025 4:00 pm
As long as the task is submitted on time, resubmission will be possible if a passing mark is not awarded. Details of the resubmission time will be made available to teams individually.
- Learning outcomes
- L01
Task description
Each team is to create and submit a team code of ethics and code of conduct outlining how team members will conduct themselves over the course of the semester.
The code of ethics must outline the principles that the team will adhere to during the semester. It is recommended that this is informed by the codes of ethics for relevant professional societies (e.g. Engineers Australia and IEEE).
The code of conduct must outline the expected (and/or prohibited) behaviour of team members, and must include statements on expected communication modes / frequencies and attendance expectations.
You may appropriately use generative AI tools in completing this task but you must reference every instance of any such use of AI. A failure to reference generative AI use may constitute student misconduct under the Student Code of Conduct.
Hurdle requirements
You must pass this assessment to achieve a grade of 4 or higher.Submission guidelines
Submission via Blackboard
Deferral or extension
You cannot defer or apply for an extension for this assessment.
Extensions for groupwork are typically not available as this impacts on all members of the team.
Extensions are not available for this assessment item. This is to allow the teamwork to proceed as scheduled with a code of conduct present.
Late submission
100% late penalty after a one hour grace period. The one-hour grace period is recorded from the time the submission is due.
Consistent with industry practice where late submission of documentation etc is not accepted, the stated late penalty applies.
This has been approved by the Associate Dean (Academic)
Individual PCB task (working circuit module on PCB & pdf of schematic)
- Hurdle
- In-person
- Mode
- Product/ Artefact/ Multimedia
- Category
- Practical/ Demonstration
- Weight
- 5% (Pass/Fail)
- Due date
4/08/2025 - 5/09/2025
Demonstrations during practical sessions only. (PCB manufacturing submissions must be received in pinecone before the beginning of week 4, see pinecone and the task description for details).
- Learning outcomes
- L02, L03
Task description
ALL students are to individually complete a working circuit element from a supplied design specification. This will require a simple, documented circuit design (schematic), component choices, PCB artwork, assembly and testing.
Submission of the PCB artwork for production by external service providers will be required well before the due date to allow for manufacturing time (see below). Return of the physical PCB is expected in approximately 7-10 days, although this manufacturing is done externally to the university and as such no guarantees are possible. Please see pinecone for the details of submitting a board for manufacture. You are not permitted to submit PCBs that were manufactured outside of pinecone, or you will receive zero marks for this assessment.
Individual assessments of the working circuits and schematics will occur in any practical session up to and including the last practical session of week 6. You will be provided with a single kit of components which is intended to be used to build your circuit. If these components are consumed, damaged, or otherwise no longer usable, you are expected to source your own equivalent components. More details are available in the project task sheet.
You will have an individual budget available at ETSG which can be used to purchase PCBs and other components. You may only order a maximum of 1 PCB per week using this budget, and the budget will expire at the end of week 6. After the budget expires, it will no longer be possible for you to order PCBs individually or purchase components for this assessment from ETSG. In addition, there is no mechanism to "top-up" your ETSG budget with your own funds. You may still purchase components (other than the PCB) externally if your budget runs out. You must have a PCB to submit with your identifying information, even if it doesn't work. Submissions of PCBs for external manufacturing for this task are only possible up to 11:59pm (one minute before midnight) on Sunday at the beginning of week 4; no submissions of PCBs for this task will be accepted after that. If the PCB does not work and it is no longer possible to order another PCB, your only option to unlock the grade hurdle is to hand-in the PCB as-is and additionally build a working circuit on a breadboard.
Only your first submission will be used in determining the marks awarded. Subsequent submissions may be used for the purpose of passing the hurdle.
You may appropriately use generative AI tools in completing this task but you must reference every instance of any such use of AI. A failure to reference generative AI use may constitute student misconduct under the Student Code of Conduct. It is not expected that generative AI will be particularly useful in this task, but use is still permitted.
Hurdle requirements
There are three grade hurdle criteria that your attempt must meet by the deadline: 1) You must produce and hand-in a PCB containing your identifying information on the silkscreen (your student number and name/initials). A non-working PCB is acceptable as long as it has the identifying information. 2) You must demonstrate the working circuit - either on your PCB or on a breadboard; and 3) You must submit your schematic (matching your working circuit) and PCB artwork (matching your PCB) via Blackboard (as PDF files) prior to your demonstration. You must meet all of these criteria in order to receive a grade of 4 or higher. You must have a PCB to submit with your identifying information, even if it doesn't work, otherwise you will receive zero marks for this task and your submission will not be considered satisfactory. You may only use PCBs manufactured through pinecone to meet these requirements.Submission guidelines
As described in the task specification on Blackboard.
Deferral or extension
You may be able to apply for an extension.
The maximum extension allowed is 14 days. Extensions are given in multiples of 24 hours.
No extensions are possible for any manufacturing submissions; extensions are only possible for the final in-class assessment.
Late submission
No late submissions are possible for any manufacturing submissions. You will receive a mark of zero if you do not complete your demonstration by the end of the final practical session on or before the due date (or by your extended deadline, if you have an approved extension).
Seminar Presentation
- Identity Verified
- Team or group-based
- In-person
- Mode
- Oral
- Category
- Presentation
- Weight
- 10%
- Due date
8/09/2025 - 12/09/2025
Presentations will be scheduled based on the availability of participants and suitable presentation spaces.
- Learning outcomes
- L01, L02, L05, L06
Task description
Each team will give a brief presentation (e.g., using PowerPoint) to demonstrate their progress. Physical artefacts such as breadboards, PCBs and components may also be used along with software demonstrations. Every team member is expected to demonstrate progress and must present for approximately 2.5 minutes. It is expected that you will identify problems and propose solutions. Presentations will be open to all students and a schedule will be determined in the week prior to seminars.
You may appropriately use generative AI tools in completing this task but you must reference every instance of any such use of AI. A failure to reference generative AI use may constitute student misconduct under the Student Code of Conduct.
Submission guidelines
Deferral or extension
You cannot defer or apply for an extension for this assessment.
Extensions for groupwork are typically not available as this impacts on all members of the team.
Students with valid extension requests either receive team mark or will be required to undertake alternative assessment.
Late submission
You will receive a mark of 0 if this assessment is submitted late.
Consistent with industry practice around presentations to clients/industry partners, the 100% late penalty applies.
This has been approved by the Associate Dean (Academic)
Product demonstration sequence
- Team or group-based
- In-person
- Mode
- Product/ Artefact/ Multimedia
- Category
- Computer Code, Practical/ Demonstration, Product/ Design, Project
- Weight
- 80%
- Due date
Week 5 - Demo 1 (Preliminary)
Week 9 - Demo 2 (Intermediate)
[Any PCBs must be submitted to pinecone before the beginning of Week 11 - see pinecone and Blackboard for further details and exact times. Manufacturing of PCBs will not be possible after this date.]
Week 13 - Final demo. All projects are due at 10am on Monday
Signup polls will be distributed in the weeks before demonstrations.
- Other conditions
- Peer assessed.
- Learning outcomes
- L01, L02, L04
Task description
Over the duration of the semester, teams are to implement a hardware and software product that meets the published specification and associated TP-STD standards available on Blackboard.
You will demonstrate your product at three separate points during semester. You will be assessed for participation as well as your progress (hardware, firmware or software) based on the evidence presented using a marksheet available on the course Blackboard site. The demonstrations will occur at the following points in semester:
- Preliminary demonstration 1 (weighting: 10%)
- Intermediate demonstration 2 (weighting: 10%)
- Final demo (weighting: 60%)
For all three demonstrations, a poll will be sent to all teams in the weeks before the due date in order to allow them to sign up for a time slot. Further details about the process will be available on Blackboard.
The final submission requires the team to submit the following in an Australia Post BX1, BX2, Small (SKU: 44862) or Medium (SKU: 44863) box (or equivalent) to staff in 47-209 by 10 AM on Monday of week 13:
- your product, including any cables, batteries (which should be uninstalled) etc. as required for the product to be tested. All of these parts must be budgeted for (any exceptions will be explicitly noted in the specification).
- printed copy of all schematic files documenting all electrical components (resistors, capacitors, integrated circuits, connectors etc).
- any other required documentation (details will be provided in the marksheet via Blackboard)
- a USB drive containing a software installer and any required files/documents (details will be provided in the marksheet via Blackboard). The USB drive will be returned to you after your demonstration.
- a declaration signed by all team members validating all submitted contents (provided as a label to stick on your submission box)
More details on the submission process will be provided via Blackboard.
Submissions will not be accepted unless they meet the following requirements (note that this has no relation to the marking/marks awarded for the submission, other than that no valid submission will result in zero marks awarded):
- The submission box must be less than or equal to the dimensions of an Australia Post Large (390x280x140mm) box
- The submission box must contain a USB drive
- The submission box must contain a printed schematic
- The submission box must have the submission label affixed with at least one signature
- The submission box must contain a maximum of 3 breadboards
In general, all members of the team are expected to attend the marking sessions. If you are not able to attend, your product will be marked in your absence and you will not be able to provide critical clarifications to the marker about the functionality implemented in your product. Given that the circumstances of any absence may be considered as part of the moderation process, it is important to let your team and the teaching staff know if you are unable to attend the demonstration.
While marks will be given for working subsystems, the assessment scheme is biased towards completeness. To get a good grade the product must be sufficiently implemented for the customer to be able to use it in its operational environment, even if it might not quite meet the specifications. If your final product does not work you will be better off submitting working prototypes. Anything not submitted at submission time cannot be assessed.
The system must be delivered in a testable form by the due date. Penalties will apply for missing or inaccurate files/documentation submitted with the product (and for inconsistencies between printed and electronic documentation). These penalties will be outlined in the marksheet on blackboard. Penalties apply for not meeting the TP-STD standards - your final product mark will be limited to a maximum of 50%. Your team's printed circuit board(s) (PCBs) must be manufactured via pinecone or your final product mark will be limited to a maximum of 50%.
The product mark will be based mainly on the performance of the product during evaluation. It is very important that your product is functioning correctly during the demonstration session, and that clear instructions are provided as to how the product is operated. However, you may not use operating instructions as a way to require the user to perform more complex/onerous actions than those that are required by the specification.
Consideration of past performance or re-evaluation of the product at a later date will not be available.
Based on staff observation and/or team request and/or the team’s performance in an interim demonstration and/or responses to a peer assessment, the teaching staff may require your team to attend regular meetings with a teaching staff member. This is intended to support teams that are perceived to be struggling in some way. Failure to participate in such meetings will be taken into account during the moderation process and may therefore result in a lower product mark.
You may appropriately use generative AI tools in completing this task but you must reference every instance of any such use of AI. A failure to reference generative AI use may constitute student misconduct under the Student Code of Conduct.
Submission guidelines
The preliminary and intermediate demonstrations will occur during prac sessions in the the allocated lab.
The final product is to be submitted to teaching staff in 47-209 (Axon) by the specified time.
Deferral or extension
You cannot defer or apply for an extension for this assessment.
No extensions are possible for any manufacturing runs.
If there are exceptional circumstances an exemption may be approved and may involve submitting/discussing your work as it stands. Exemptions must be requested as an extension with a note specifying exemption via my.UQ.
It is expected that teams will manage their time and tasks appropriately within the group to cover the overall project work and should plan for unexpected short duration absences by team members over the semester.
Late submission
No late submissions are possible for any manufacturing runs.
A 100% late penalty applies to the final product submission (final demo) after a one-hour grace period. The one-hour grace period is recorded from the time the submission is due. Non-attendance at any of the demonstrations will result in zero marks for that demonstration. (Only one team member is required to attend but all may attend.)
Consistent with industry practice where late submission of documentation etc is not accepted, the stated late penalty applies.
This has been approved by the Associate Dean (Academic)
Final Report and Reflection
- Hurdle
- Mode
- Written
- Category
- Paper/ Report/ Annotation, Reflection
- Weight
- 5%
- Due date
10/11/2025 4:00 pm
- Learning outcomes
- L05, L06, L07
Task description
The final report will consist of a brief re-statement of the team's roles and an individual summary of the background, methods and results of your work. The report must also address sustainability issues around your design. The report is an individual item of assessment - all parts must be completed individually. You may appropriately use generative AI tools in completing this task but you must reference every instance of any such use of AI. A failure to reference generative AI use may constitute student misconduct under the Student Code of Conduct.
In addition, a reflection describing your group work experience over the duration of the semester is required. The goal of this part of the assignment is to prompt reflective thoughts about the interactive aspects of the engineering project you have participated in. The reflection is an opportunity for you to consider the inter-personal mechanics of group work, and your experiences working as part of a team, and to document particular challenges you may have faced which did not form part of any technical reports or presentations.
- Discuss what you have learned about how to work in a group.
- Describe what worked well within your group, what did not work well, and why.
- How might you organise team work differently to improve performance?
- If your group had conflicts or problems in working as a team, describe them and give insights into how such problems were resolved, or could be avoided in the future.
This report is not assessed solely on the basis of technical outcomes of the team, but also on the identification of interactions, personality types and organisational tools which formed part of the successes (or failures!) of your team.
The document will be submitted through Turnitin on the Blackboard site.
Hurdle requirements
You must be awarded at least 40% of the marks in this task to achieve a grade of 4 or higher.Submission guidelines
Submit via Blackboard (Turnitin).
Deferral or extension
You may be able to apply for an extension.
The maximum extension allowed is 28 days. Extensions are given in multiples of 24 hours.
Late submission
A penalty of 10% of the maximum possible mark will be deducted per 24 hours from time submission is due for up to 7 days. After 7 days, you will receive a mark of 0.
Assessment of Individual Performance (Formative/incorporated into product mark)
- Online
- Mode
- Activity/ Performance
- Category
- Participation/ Student contribution, Reflection
- Weight
- Incorporated into product mark
- Due date
25/08/2025 4:00 pm
22/09/2025 4:00 pm
27/10/2025 4:00 pm
- Other conditions
- Peer assessed, Peer assessment factor.
- Learning outcomes
- L01, L07
Task description
You will undertake three evaluations of each member of your team through the semester. They, of course, will be evaluating you. The purpose of the first two evaluations is to give formative feedback to all team members on their performance to that point. Results from the third evaluation will be used if moderation takes place (see below).
The peer assessment scores will not directly moderate the product mark, but may serve as a prompt to teams to request a moderation meeting. The absolute values and trends across the three evaluations may be used as evidence of the team performance of individuals in a moderation meeting.
The default Peer Assessment Factor (PAF) which will moderate the product mark will be 1.0. If any members of the team wish to change this distribution, a moderation meeting will be required with teaching staff. Students must indicate this intention by email to the course coordinator by 4pm, Friday Week 13. It is recommended that you wait until after your final demonstration to apply for moderation, as moderation meetings cannot be cancelled once requested.
A moderation meeting will require in-person attendance of all members - once a meeting is scheduled, all members are expected to attend, and if any member does not, all decisions will be made in their absence without their input. Every opportunity will be given to the team to derive an acceptable distribution of PAFs. If no resolution within the meeting is possible, teaching staff will allocate PAFs on the basis of responses to questions, history of performance, demonstrator feedback and marked product. A document describing the moderation process can be found on Blackboard.
A PAF of 1.0 indicates that you are making a satisfactory/expected contribution to the team. A PAF less than 1.0 indicates your contribution is less than expected. A PAF greater than 1.0 indicates you are contributing more than expected. Failure to complete a formative peer assessment will result in you receiving a PAF of 0.5 for that evaluation, i.e. it will be assumed that your contribution to the team up to that point has been much less than expected.
Your overall PAF will determine a Product Scaling Factor (PSF) as follows:
- for a team of 4 or 5, PSF = PAF if your PAF is <= 1 and PSF = (1+PAF)/2 if your PAF is > 1
- for a team of 3, PSF = 1.1 * PAF if your PAF is <= 1 and PSF = 1.1*(1+PAF)/2 if your PAF is > 1
- for a team of 2, PSF = 1.25 * PAF if your PAF is <= 1 and PSF = 1.25*(1+PAF)/2 if your PAF is > 1
All three demo marks will be scaled (multiplied) by this PSF (and then capped at the maximum possible mark where applicable).
Submission guidelines
Submitted online via the provided tool (Blackboard link will be provided)
Deferral or extension
You cannot defer or apply for an extension for this assessment.
Late submission
Submission of formative PAFs at each timepoint is your responsibility. Submission after the due date is not possible, and a lack of submission may be considered negatively toward you in a moderation meeting.
Course grading
Full criteria for each grade is available in the Assessment Procedure.
Grade | Cut off Percent | Description |
---|---|---|
1 (Low Fail) | 0 - 19 |
Absence of evidence of achievement of course learning outcomes. |
2 (Fail) | 20 - 46 |
Minimal evidence of achievement of course learning outcomes. |
3 (Marginal Fail) | 47 - 49 |
Demonstrated evidence of developing achievement of course learning outcomes Course grade description: To receive this grade, you must meet ALL of the following criteria: 1) Achieve a total mark within the respective percentage band 2) Complete the WHS requirements 3) Your final report and reflection mark is 40% or higher |
4 (Pass) | 50 - 64 |
Demonstrated evidence of functional achievement of course learning outcomes. Course grade description: To receive this grade, you must meet ALL of the following criteria: 1) Achieve a total mark within the respective percentage band 2) Complete the WHS requirements 3) Your code of ethics/code of conduct is considered satisfactory 4) Your final report and reflection mark is 40% or higher 5) Your attempt at the individual PCB/schematic task is considered satisfactory |
5 (Credit) | 65 - 74 |
Demonstrated evidence of proficient achievement of course learning outcomes. Course grade description: To receive this grade, you must meet ALL of the following criteria: 1) Achieve a total mark within the respective percentage band 2) Complete the WHS requirements 3) Your code of ethics/code of conduct is considered satisfactory 4) Your final report and reflection mark is 40% or higher 5) Your attempt at the individual PCB/schematic task is considered satisfactory 6) Your product is under the target bill of materials cost |
6 (Distinction) | 75 - 84 |
Demonstrated evidence of advanced achievement of course learning outcomes. Course grade description: To receive this grade, you must meet ALL of the following criteria: 1) Achieve a total mark within the respective percentage band 2) Complete the WHS requirements 3) Your code of ethics/code of conduct is considered satisfactory 4) Your final report and reflection mark is 40% or higher 5) Your attempt at the individual PCB/schematic task is considered satisfactory 6) Your product is under the target bill of materials cost 7) Your team's final product is presented/demonstrated on PCB(s) with no use of veroboard/breadboard and no use of non-approved breakout boards |
7 (High Distinction) | 85 - 100 |
Demonstrated evidence of exceptional achievement of course learning outcomes. Course grade description: To receive this grade, you must meet ALL of the following criteria: 1) Achieve a total mark within the respective percentage band 2) Complete the WHS requirements 3) Your code of ethics/code of conduct is considered satisfactory 4) Your final report and reflection mark is 40% or higher 5) Your attempt at the individual PCB/schematic task is considered satisfactory 6) Your product is under the target bill of materials cost 7) Your team's final product is presented/demonstrated on PCB(s) with no use of veroboard/breadboard and no use of non-approved breakout boards 8) Your product contains a total of no more than two small, neat modifications |
Additional course grading information
The WHS requirements listed above refers to the declarations, inductions and/or assessments required for entry into the team project laboratory - note that the surface mount soldering training is not required to be completed for entry into the laboratory and as such is not considered part of this requirement. ALL students must individually complete the required declarations/inductions/assessment. Further details will be presented via Blackboard.
Exceptional circumstances may modify the required specification and/or submission date for some teams or some individuals. This will be uncommon and at the discretion of the course coordinator. The course coordinator reserves the right to adjust marks up but not down.
Your overall course mark will be rounded to the nearest whole number prior to applying the grade cutoffs above.
Supplementary assessment
Supplementary assessment is not available for some items in this course.
Course failure due to performance on team assessment items cannot be overcome with supplementary assessment. Supplementary assessment is therefore only available on a grade of 3 if your individual PCB/schematic task is graded as unsatisfactory and/or your individual report mark is at least 40% but no more than 50%.
Additional assessment information
The course Blackboard site will contain marking guidelines for all assessment items.
Use of Resources Developed by Other Entities
ENGG2800 is a course in which you develop a prototype of an electronic product. The task is intended to simulate how this might be done by a small team in a commercial environment. As in such an environment, we don't expect you to develop everything from scratch - you can take advantage of designs/code/libraries developed by other entities (people, companies, AI tools) provided you follow the required standards (TP-STD documents in this case). In particular, you can not use resources that would prevent the commercial sale of your product - this includes libraries that may be free for personal use but require a license fee for commercial use. (If you do use such a library you would have to include the cost of the license in the cost of your product - which may mean you can't keep your product under budget.) You should not use generative AI tools to create code for use in your product unless you can guarantee that the code produced is free from legal constraints (copyright or license violations) and would be able to be used in a commercial product. Many such AI tools are trained with copyrighted code and may include fragments of such code in their output - which would prevent commercial use.
Having Troubles?
If you are having difficulties with any aspect of the course material you should seek help. Speak to the course teaching staff in a laboratory session, or ask on the course discussion board.
If external circumstances are affecting your ability to work on the course, you should seek help as soon as possible. The University and UQ Union have organisations and staff who are able to help, for example, UQ Student Services are able to help with study and exam skills, tertiary learning skills, writing skills, financial assistance, personal issues, and disability services (among other things).
Complaints and criticisms should be directed in the first instance to the course coordinator. If you are not satisfied with the outcome, you may bring the matter to the attention of the School of EECS Director of Teaching and Learning.
Learning resources
You'll need the following resources to successfully complete the course. We've indicated below if you need a personal copy of the reading materials or your own item.
Library resources
Find the required and recommended resources for this course on the UQ Library website.
Other course materials
Recommended
Item | Description | Further Requirement |
---|---|---|
tp-info | https://tp-info.uqcloud.net/ | |
Saturn PCB toolkit | https://saturnpcb.com/saturn-pcb-toolkit/ |
Additional learning resources information
Online resources
Course material will be available via Blackboard. Theᅠweb site containsᅠinformation required to complete the course. You should investigate it thoroughly.
Discussion board
Students areᅠpermitted to post questions (and answers!) to aᅠdiscussion board accessible through theᅠBlackboard website.ᅠ Students are encouraged to collectively solve problems using the discussion board - staff will only intervene when necessary. Students are reminded of the UQ Code of Practice for Internet Use and are advised that breaches will be immediately referred to the School's misconduct procedure.
Lectures
The lectures will be used to provide material to assist with various technical and non-technicalᅠskills. Most of these are pre-recorded videos that can be accessed as students need them.
Learning activities
The learning activities for this course are outlined below. Learn more about the learning outcomes that apply to this course.
Filter activity type by
Please select
Learning period | Activity type | Topic |
---|---|---|
Multiple weeks |
Lecture |
Lectures and self-study series The lecture series will cover the course structure and organisation, product specifications, project planning, practical electronics and software design relevant to the product in the first few weeks of semester. Lecture notes will be posted on Blackboard and lectures will be recorded. Pre-recorded lectures are available on various topics. Further reading materials are available through tp-info. Learning outcomes: L01, L02, L03, L04, L06 |
Practical |
Teaching Staff Consultation in Lab Help and feedback provided by teaching staff during scheduled lab classes. Learning outcomes: L01, L02, L03, L04, L05, L06, L07 |
Policies and procedures
University policies and procedures apply to all aspects of student life. As a UQ student, you must comply with University-wide and program-specific requirements, including the:
- Student Code of Conduct Policy
- Student Integrity and Misconduct Policy and Procedure
- Assessment Procedure
- Examinations Procedure
- Reasonable Adjustments for Students Policy and Procedure
Learn more about UQ policies on my.UQ and the Policy and Procedure Library.
School guidelines
Your school has additional guidelines you'll need to follow for this course: