Skip to menu Skip to content Skip to footer
Course profile

Major Design Project (ENGG4552)

Study period
Sem 1 2025
Location
St Lucia
Attendance mode
In Person

Course overview

Study period
Semester 1, 2025 (24/02/2025 - 22/11/2025)
Study level
Undergraduate
Location
St Lucia
Attendance mode
In Person
Units
4
Administrative campus
St Lucia
Coordinating unit
Mech & Mine Engineering School

Group design project based on a multidisciplinary topic sponsored by active players in industry (research, academic, and commercial organisations). Requires completion of detailed design, construction of a prototype and testing to demonstrate sponsor's requirements are met.
For information about how to find a project and supervisor, and enrol in this course, please refer to the school website.

This course acts as a capstone course for senior students of Mechanical, Mechanicalᅠand Aerospace, and Mechanical and Materials Engineering, and requires an in-depth, project-based application of subject matter from a wide range of preceding courses. Students must conduct and demonstrate their ability to independently study and research relevant material as required to complete their selected projects.

Students are expected to formulate the technical specifications for their projects from a limited brief. This should be achieved through an iterative process of discussion with the industry stakeholder (project sponsor) and the course staff. There will be a focus on teams developing a direct relationship with the stakeholders. Once the project requirements have been agreed, teams are expected to follow appropriate engineering processes to design and build a prototype that can be subjected to verification or validation tests.

To do well in the course, teams will have to follow a rigorous and scientific process and deliver a prototype that meets or exceeds the project requirements. Processes, performances, and reports are evaluated in theᅠcontext of the standards expected of professional consulting engineers.

Frequently Asked Questions:

What projects are available? Where can I find out more?

The current list of projects can be viewed atᅠhttps://student.eait.uq.edu.au/projects/index.wphp and by searching for ENGG4552. Prior to the start of semester we will still be in the process of negotiating projects with industry partners, so the list may change up until the first lecture. Also, depending on enrolment numbers and interest levels, we may have to withdraw some of the advertised projects.

How are projects assigned?

Students will select their project through a two-stage process. Firstly, an attempt will be made to allow students to self-select projects and groups through discussion/negotiation with their peers during the first contact session in Week 1 of Semester 1. Details of this process will be provided in the first lecture. If this fails to sufficiently distribute students between the projects we will resort to a process of preferential voting, where each student will be able to list their preferences.

Is there a project budget?

Yes. All teams will receive a small start-up fund. In addition, depending on the project you may have additional cash or in-kind contributions (e.g. workshop hours, access to facilities, ability to out-source) provided by the project sponsor.ᅠᅠ

Will there be lecture recordings?

Yes, but don't rely on them. The majority of the course content will be delivered as part of our weekly contact sessions. For example, student teams will present their work to date to the class, or during supervisor team meetings, and then receive immediate verbal feedback. I.e. the teaching material is delivered interactively. When we have presentations, these will be recorded when permissible. However, to maximise learning you should attend the contact sessions.ᅠ

How do I receive feedback in this course?

For submitted assessments, the marking rubrics will identify the areas where your work has been deficient and there will be written comments. In addition there will be interactive verbal feedback in the weekly workshops. We can't keep a record of this, so it is up to you to keep notes, reflect on the comments, and learn. Furthermore, ask the course staff for comments, ideas, suggestions, feedback, to read your drafts, etc. We have some capacity to do this, but the onus is on you to ask. Students are encouraged to submit draft reports two weeks before each due date to maximise both the time for teaching staff to read and provide feedback, and also the time for you to implement that feedback into your submitted assessment tasks.

How will individual contributions be measured in team assessments?ᅠ

We expect you to have sufficient team working skills so that everyone in the team contributes equitably. It is strongly recommended that any issues arising from differences in team members' contributions and expectations are managed professionally within the team prior to the submission of assessment. This will help ensure a positive and collegial team environment for the full year. By default, each group member will receive the same mark for each assessment item. For the cases where equitable teamwork breaks down, peer evaluation may be considered for written assessment items. The procedure for group mediation and eventual mark adjustment will be presented in class.

Course requirements

Assumed background

It is assumed that you are a final year engineering student and that you bring all prior knowledge to this course including theoretical and practical engineering knowledge as well as project management, communication and team work knowledge and skills. We will not be re-teaching you these things but instead will expect you to apply these fundamental engineering competencies and develop them further. For most of you, the next year you will be working in industry - this is where you get to demonstrate your preparedness.

Prerequisites

You'll need to complete the following courses before enrolling in this one:

Completion of 32 units toward BE(Hons) program

Incompatible

You can't enrol in this course if you've already completed the following:

MECH4500 or MECH4501 or ENGG4600 or ENGG4601

Course contact

Course coordinator

Dr Tristan Vanyai

Primary contact for Dr Vanyai will be in timetabled contact sessions. For further questions, please post to the discussion board if applicable to other groups or members. Otherwise, please email Dr Vanyai at t.vanyai@uq.edu.au to organise a meeting.

Course staff

Lecturer

Timetable

The timetable for this course is available on the UQ Public Timetable.

Additional timetable information




Aims and outcomes

This course aims to:

  • assist your transition to becoming a responsible professional engineer through a group design project in which you will incorporate engineering skills and knowledge acquired throughout your engineering program,
  • encourage student engagement between group members and with a client, under the guidance of academic supervisors,
  • develop your project management skills to complete a major project within a specified time frame.

Learning outcomes

After successfully completing this course you should be able to:

LO1.

Formulate an engineering problem from a limited brief.

LO2.

Critically evaluate previous research.

LO3.

Apply project management and team working techniques to plan and carry out a small engineering project as a group in the allocated time frame, within the available resources, and in a safe and ethical manner.

LO4.

Demonstrate an ability to conduct both the research and design necessary to take a complex engineering project from initial scoping, to detailed design, to prototype manufacture, to verification tests.

LO5.

Demonstrate an ability to apply core engineering knowledge, design principles (e.g. requirement capture, system thinking, safety and risk mitigation, professional standards etc.), and innovation/creativity to solve a complex mechanical engineering project.

LO6.

Demonstrate ability to conduct verification/validation tests and extract useful information that informs future designs.

LO7.

Communicate technical information precisely and clearly---both individually and as part of a team---utilising a range of technologies and modes of communication, including oral presentation, written documentation, graphical illustration and computational and/or physical modelling. This includes communicating effectively with the client to ensure that the final design is delivered to their satisfaction (i.e. on time, on budget, and meeting their expectations).

LO8.

Appreciate the role of a professional engineer in society.

Assessment

Assessment summary

Category Assessment task Weight Due date
Portfolio Project Requirements Documentation
  • Team or group-based
10%

15/04/2025 1:00 pm

Paper/ Report/ Annotation Preliminary Design Report
  • Team or group-based
15%

27/05/2025 1:00 pm

Presentation Preliminary Design Review
  • Hurdle
  • Team or group-based
  • In-person
5% Pass/Fail

9/06/2025 - 13/06/2025

Paper/ Report/ Annotation Demonstration Risk Assessment
  • Team or group-based
  • Online
P/F - Impacts Demonstration

9/09/2025 1:00 pm

Practical/ Demonstration, Presentation, Product/ Design, Project Prototype validation test/demonstration
  • Team or group-based
  • In-person
15%

7/10/2025 - 10/10/2025

Paper/ Report/ Annotation, Product/ Design, Project Final design report
  • Team or group-based
50%

24/10/2025 1:00 pm

Presentation, Product/ Design, Project Presentation Evening
  • Team or group-based
  • In-person
5%

27/10/2025 - 31/10/2025

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

Project Requirements Documentation

  • Team or group-based
Mode
Written
Category
Portfolio
Weight
10%
Due date

15/04/2025 1:00 pm

Learning outcomes
L01, L02, L03, L04, L05, L07, L08

Task description

After completing your meetings with project stakeholders, it is time to plan your project. At this stage we are not expecting a report, but instead a collection of material to show you are on the right track. 

Submit a portfolio containing the following project planning documents:

  • Concise literature review identifying prior art relating to the proposed project.
  • Functional requirements capture - including associated analysis and justification.
  • Work Breakdown Structure (WBS) for the project and brief explanation of how this results in an effective division in sub-systems.
  • Plan (e.g. Gantt Chart) for the project. This should include all activities with associated times and required resources, critical path items and a detailed description of critical tasks to be completed prior to Preliminary Design Review
  • Risk register. This should include OH&S related risks that may arise during design, build, and test phase, program risks that may affect your ability to deliver plan on time and proposed mitigation strategies.
  • Set of concept sketches or preliminary CAD models

Aim for an overall length between 15 and 30 pages. The documents are to be assembled into a single pdf file.

Students will be required to complete peer evaluation for this assessment task.

This task has been designed to be challenging, authentic and complex. Whilst students may use AI and/or MT technologies, successful completion of assessment in this course will require students to critically engage in specific contexts and tasks for which artificial intelligence will provide only limited support and guidance. A failure to reference generative AI or MT use may constitute student misconduct under the Student Code of Conduct. To pass this assessment, students may be required to demonstrate detailed comprehension of their written submission independent of AI and MT tools.

Please refer to Blackboard for detailed marking criteria.

Submission guidelines

Submit via Turnitin 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.

To facilitate timely feedback to students.

A Student Access Plan (SAP) can only be used for a first extension. Extensions based on an SAP may be granted for up to seven (7) days, or the maximum number of days specified in the Electronic Course Profile (ECP), if it is less than seven (7) days. Any further extensions will require additional supporting documentation, such as a medical certificate.

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.

Preliminary Design Report

  • Team or group-based
Mode
Written
Category
Paper/ Report/ Annotation
Weight
15%
Due date

27/05/2025 1:00 pm

Learning outcomes
L01, L02, L03, L04, L05, L07, L08

Task description

Each team must write a Preliminary Design Report. This is a formal report based on the material previously reviewed as the Project Requirements Portfolio and should incorporate the feedback received on the previous assessment and during the contact sessions. You can re-use previous materials, but this should be updated and expanded to reflect the current status of your project.  

The report should clearly define the project scope and objective, present a detailed review of relevant background material and an assessment of the impact of previous work on the current project. All background and related material should be appropriately referenced and appear in the reference list.

In addition, results from the preliminary analysis and how this has been used to select a preferred concept for further development must be included. This analysis should form the basis for the concept presented at the Preliminary Design Review presentation. 

The report should demonstrate the initiative and abilities of your team to complete the design project, in particular, initiative, creativity and problem solving skills. A detailed plan for the remainder of the project should be provided, which identifies the resource requirements (incl. cash) from the industry partners. 

The report format is flexible but the following is expected to be included:

  • An introduction to the topic;
  • A critical review of prior art;
  • A detailed analysis of the functional requirements leading to a clear functional requirements capture. This should include associated analysis and justification.
  • Present and discuss the project WBS and how this will allow an efficient solution to problem;
  • An overview and description of the design solution your team has identified, how this was selected (e.g. pros and cons), and how this will address the requirements;
  • Results of calculations/preliminary experiments that de-risk your aims;
  • Project plan for the remainder of the year, including resource and cost considerations;
  • Table of resource requirements (including cash) with appropriate justification. This should be discussed with stakeholders prior to submission;
  • A comprehensive risk management plan for the project;
  • A complete list of references.

The report main body (excluding preliminary pages, tables of contents, and appendices) should be around 25 pages and certainly not more than 40 pages long.

What to submit

Teams are required to submit the following:

  • One (1) electronic version submitted via Turnitin on the course Blackboard site. 
  • Students will be required to complete peer evaluation for this assessment task.

This task has been designed to be challenging, authentic and complex. Whilst students may use AI and/or MT technologies, successful completion of assessment in this course will require students to critically engage in specific contexts and tasks for which artificial intelligence will provide only limited support and guidance. A failure to reference generative AI or MT use may constitute student misconduct under the Student Code of Conduct. To pass this assessment, students may be required to demonstrate detailed comprehension of their written submission independent of AI and MT tools.

Please refer to Blackboard for detailed marking criteria.

Submission guidelines

Submit via Turnitin 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.

To facilitate timely feedback to students.

A Student Access Plan (SAP) can only be used for a first extension. Extensions based on an SAP may be granted for up to seven (7) days, or the maximum number of days specified in the Electronic Course Profile (ECP), if it is less than seven (7) days. Any further extensions will require additional supporting documentation, such as a medical certificate.

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.

Preliminary Design Review

  • Hurdle
  • Team or group-based
  • In-person
Mode
Oral, Product/ Artefact/ Multimedia
Category
Presentation
Weight
5% Pass/Fail
Due date

9/06/2025 - 13/06/2025

Learning outcomes
L01, L02, L04, L05, L07, L08

Task description

The Preliminary Design Review (PDR), is one of many 'gates' that may exist in a rigorous engineering process. The aim of the PDR is to receive feedback on your proposal. Usually the review panel consists of project stake-holders, chief engineers, subject matter experts, and other senior technical and program management staff and their job is to use their wisdom to identify weaknesses in your proposal and to provide constructive feedback. This way you can modify and improve your proposal at this early stage and ensure your prototype has a higher probability of being a success. 

You will receive marks as per the rubric below. In addition, you need to meet the requirements for a pass as outlined in the second rubric.

Teams must pass the PDR to complete the course.

Teams receiving a fail or provisional pass will need to complete and pass a second PDR scheduled for week 1 of semester 2. 

Each PDR will be 30 min duration, with the initial 15 minutes allocated for your group's presentation, and the remaining time allocated for questions/discussion with the review panel. The presentation needs to be short but detailed, and keep to the 15min time allocation. The format is flexible, but you should include the following:

Explanation of the project and goals: Explain what your project is about. Make this crystal clear to the panel, on the assumption that they are technically minded but completely unfamiliar with your project. Give enough background so that the project makes sense. And clearly explain the goals. Remember, if you proceed past this point of your presentation, but your audience haven’t yet figured out the essence of your project, they won’t be able to follow the rest of the presentation.

Discussion of functional requirements and how these have been developed: Give a very clear picture of:

  • What does your design need to "do" (i.e. its functions)?
  • How will functionality be assessed (i.e. specifications)?
  • What are your design objectives? I.e. What will make the design a "good" one? What are the most important objectives?
  • What are the constraints? (money, time, interfacing systems, etc)

You don’t have much time to do this, and you’ll have people on the panel unfamiliar with your project. This is not easy, but, if you can’t explain functional requirements simply, then you need to…. still figure out how to explain them simply.

Summary of prior art and explanation about why/how your proposal is different/better: Explain where your project fits into the current scheme of things. What aspects of your problem are unique/new? Something must be new/unique, or else the client could just order a solution from an existing supplier. What aspects of your design have already been well addressed with existing design solutions around the world? If you aren’t going with existing solutions, even where they might seem like they fit, then explain why.

Overview and description of the design solution your team has selected: What solution are you planning to take? Can you explain the basic concept and justify it? This should be consistent with the outcomes of the prior art review, and also justified against the functional requirements and preliminary analysis.

Results of calculations/preliminary experiments that de-risk your aims: Show relevant preliminary analysis/experiments/results that provide confidence in your current design concept/strategy etc. For example, if you are taking an ambitious/original path to a solution, you need to show evidence that it should work. If some of these calculations or validation experiments are not yet ready, can you outline plans to obtain this de-risking data early enough to be useful? For this part, evidence should include one or more of the following:

  • 3D printed model of your design solution (or major critical sub-systems);
  • Preliminary 3D CAD model showing the concept;
  • Prototype simulations/models that show how your concept performs;
  • Prototype software that shows how you will provide functionality;
  • Other approaches that may befit your project. Talk to course staff for advise.

Here we want to see how you are approaching the problems; to see that your approaches are fit for purpose; and we want to give you feedback on how you can improve. 

Summary of critical risks and your corresponding mitigation strategies: Here you identify the show-stopping risks and how you will prevent these risks seriously compromising your project goals. Mitigation strategies should clearly and convincingly address the risks.

Your project plan (make sure this is legible when being presented, or bring hand-outs). This should include resourcing requirements and, if applicable, cash requirements: Show that you have a feasible plan to achieve your project goals. Show that you have disseminated all of the project activities into clear tasks, to a sufficient level of detail to enable meaningful scheduling of the tasks. Make sure all project activities, and all required resources, are included. And show how the workload will be distributed between the team members. Convince the panel that they can be confident your project will succeed.


This assessment task is to be completed in-person. The use of generative Artificial Intelligence (AI) or Machine Translation (MT) tools will not be permitted. Any attempted use of AI or MT may constitute student misconduct under the Student Code of Conduct.

Please refer to Blackboard for detailed marking criteria.

Hurdle requirements

Teams must pass the PDR to complete the course. Teams receiving a fail or provisional pass will need to complete and pass a second PDR scheduled for week 1 of semester 2.

Submission guidelines

Deferral or extension

You cannot defer or apply for an extension for this assessment.

Each team member must contribute to both the presentation and the follow-on discussion. Any individual who does not attend their group's presentation will receive 0 for this assessment item. However, if there are medical or other acceptable reasons that will affect your ability to attend, then you can apply for an extension.

Late submission

You will receive a mark of 0 if this assessment is submitted late.

The nature of a group oral presentation does not allow for the application of a late penalty with a sliding scale as they are presented within the allocated timeslot.


Demonstration Risk Assessment

  • Team or group-based
  • Online
Mode
Written
Category
Paper/ Report/ Annotation
Weight
P/F - Impacts Demonstration
Due date

9/09/2025 1:00 pm

Learning outcomes
L03, L04, L05, L06, L08

Task description

TO COMPLETE THE PROTOYPE VALIDATION TEST/DEMONSTRATION, YOU MUST COMPLETE THIS ASSESSMENT ITEM.

In preparation for testing each groups' prototype, a full assessment of the associated risks must be conducted.

Risk assessments must be submitted to UQ's risk assessment database system, UQ Safe.

This risk assessment must be submitted and approved prior to any potentially hazardous activity, especially relating to the demonstration of the prototype.

Any potentially hazardous activity, including running preliminary testing prior to demonstration to teaching staff, cannot occur until the full risk assessment process has been completed and approved. If you are unsure about what constitutes a potentially hazardous activity, please contact course staff.

Note that the demonstration assessment item CANNOT be completed until a risk assessment has been approved by teaching staff, and mitigation strategies have been employed.


Artificial Intelligence (AI) and Machine Translation (MT) are emerging tools that may support students in completing this assessment task. Students may appropriately use AI and/or MT in completing this assessment task.

Please refer to Blackboard for detailed marking criteria.

Submission guidelines

Submit online at UQ Safe: https://prod.riskcloud.net/?ccode=642

Deferral or extension

You cannot defer or apply for an extension for this assessment.

If there are exceptional circumstances you may apply for an extension. Extensions must be requested via my.UQ.

Late submission

Teams must submit on time, this is a pass/fail activity. Any delays to the demonstration activity due to risk assessments not being approved on time will incur a late penalty. 

Prototype validation test/demonstration

  • Team or group-based
  • In-person
Mode
Oral, Product/ Artefact/ Multimedia, Written
Category
Practical/ Demonstration, Presentation, Product/ Design, Project
Weight
15%
Due date

7/10/2025 - 10/10/2025

Learning outcomes
L03, L04, L05, L06, L07, L08

Task description

Each team is required to demonstrate the performance of the prototype/product they have developed. Depending on the type of prototype this may take the form of experimental testing, comparison to literature data, consultation/input from client, etc. To demonstrate performance, you should review the performance requirements that were identified in semester 1 and use these to establish a test campaign that will determine whether your prototype meets these. This should consider critical requirements, as well as secondary, or tacit, requirements that further improve the value of the product. The demonstration should be a live demo.

Format of submission

The format of the demonstration is flexible and you are encouraged to modify this to best suit your project. If the prototype is portable, or available on campus, live demonstrations with attendance of course staff are encouraged. You may want to consider including the following as part of your demonstration:

  • A short selection of presentation slides/handouts that show how key performance criteria (e.g. from the PDR) will be addressed through the demonstration tests;
  • Live demonstration or videos/photos that show tests being conducted. These should be included in a presentation or similar (showing videos from a phone is not acceptable). It may be prudent to create these as a back-up even if you are planning to conduct live demonstrations;
  • Details of your test set-up, including calibration information;
  • Tabulated/graphed results that show performance. (Make sure axes are appropriately labelled and have units);
  • A table and/or chart that shows whether, and to what extent, performance criteria have been met.  

You are encouraged to use your creativity in your use of demonstration materials (i.e. props etc).

A formal risk assessment must be submitted and approved prior to any experimental work done either during or in preparation for the demonstration.


This assessment task is to be completed in-person. The use of generative Artificial Intelligence (AI) or Machine Translation (MT) tools will not be permitted. Any attempted use of AI or MT may constitute student misconduct under the Student Code of Conduct.

Please refer to Blackboard for detailed marking criteria.

Submission guidelines

Submission / Assessment

Please contact the course coordinator to arrange a time for your live demonstration. The submission/assessment will consist of an around-a-table discussion between the full team and course staff. It is up to the team to organise and lead this discussion, to demonstrate the functionality of your product, and to ensure that all areas important for the project are covered. The course staff will ask probing technical questions. Risk assessments must be submitted to UQ Safe well in advance of the demonstration, as part of the previous assessment item. This will allow time for feedback and students to make any required changes prior to the demonstration. If a full risk assessment is not approved by the day BEFORE prototype demonstration, the demonstration will not go ahead, incurring a late penalty for each day delayed, as below.

Deferral or extension

You cannot defer or apply for an extension for this assessment.

Any individual who does not attend their group's demonstration will receive 0 for this assessment item. However, if there are medical or other acceptable reasons that will affect your ability to attend, then you can apply for an extension.

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.

Students will demonstrate their prototypes within an allocated timeslot. If risk assessment submission and subsequent approval are delayed, the demonstration activity will be late and subject to a late submission penalty. It is both industry standard and UQ policy that risk assessments are submitted prior to any major design project demonstration.

Final design report

  • Team or group-based
Mode
Written
Category
Paper/ Report/ Annotation, Product/ Design, Project
Weight
50%
Due date

24/10/2025 1:00 pm

Learning outcomes
L02, L04, L05, L06, L07, L08

Task description

The design documentation is one of the primary assessments components of the course. The purpose of this document is to capture the design process, justification for key design decisions, calculations, drawings, test results, and project outcomes. The last section should also identify any areas for improvement in the work and how these should be addressed in the future. Effectively, this report should provide the reader (a competent engineer) with a blueprint of how to repeat your project and maybe how to improve upon it. To achieve this, the report should concisely capture the critical steps in your project and also material that is required to re-create the work (drawings, simulation files, etc...). The materials included in and with the report must be organised in a systematic and accessible way.

As part of your documentation you should consider including the following:

  • Introduction & scope
  • System analysis & requirements synthesis
  • Design analysis (e.g. calculations/simulations)
  • Drawing register and pdf drawings (e-copies of models and drawings to be submitted electronically)
  • Key simulation results (submit simulation set-up files and results electronically)
  • Verification/validation results 
  • Conclusions and recommendations for future work

Format of submission

For the general format, please follow the general final year thesis submission guidelines, see the School website on "Undergraduate Engineering Theses Submissions". The link is currently - http://www.mechmining.uq.edu.au/mech-mining-thesis-submission. Please note, you do not require a signed letter in the front matter of your ENGG4552 final report.

Aim for your report body length (excluding front matter and appendices) to be in the range 50-100 pages. Reports shorter than this length generally indicate insufficent scope or ambition.

Groups are required to submit the following:

  • An electronic version of the report to be submitted via Turnitin on the course Blackboard site.
  • If applicable, relevant code/calculations/set-up/electronic files are to be provided by emailing the course coordinator a cloud-storage link to the electronic files---by the due date/time---and to ensure it is available for at least four weeks from this date.
  • Students will be required to complete peer evaluation for this assessment task.

This task has been designed to be challenging, authentic and complex. Whilst students may use AI and/or MT technologies, successful completion of assessment in this course will require students to critically engage in specific contexts and tasks for which artificial intelligence will provide only limited support and guidance. A failure to reference generative AI or MT use may constitute student misconduct under the Student Code of Conduct. To pass this assessment, students may be required to demonstrate detailed comprehension of their written submission independent of AI and MT tools.

Please refer to Blackboard for a detailed marking criteria.

Submission guidelines

Submit via Turnitin 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.

To facilitate timely feedback to students.

A Student Access Plan (SAP) can only be used for a first extension. Extensions based on an SAP may be granted for up to seven (7) days, or the maximum number of days specified in the Electronic Course Profile (ECP), if it is less than seven (7) days. Any further extensions will require additional supporting documentation, such as a medical certificate.

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.

Presentation Evening

  • Team or group-based
  • In-person
Mode
Oral
Category
Presentation, Product/ Design, Project
Weight
5%
Due date

27/10/2025 - 31/10/2025

Learning outcomes
L02, L04, L05, L06, L07, L08

Task description

Your team will make a presentation at the ENGG4552 Design Project Presentation Evening. This is an opportunity to show-case the outcomes of your project to an invited audience consisting of industry, staff, and fellow students. 

All group members must participate in the presentation.

This assessment task is to be completed in-person. The use of generative Artificial Intelligence (AI) or Machine Translation (MT) tools will not be permitted. Any attempted use of AI or MT may constitute student misconduct under the Student Code of Conduct.

Please refer to Blackboard for a detailed marking criteria.

Submission guidelines

Deferral or extension

You cannot defer or apply for an extension for this assessment.

Any individual who does not attend their group's presentation will receive 0 for this assessment item. However, if there are medical or other acceptable reasons that will affect your ability to attend, then you can apply for alternative assessment.

Late submission

You will receive a mark of 0 if this assessment is submitted late.

The nature of a group oral presentation does not allow for the application of a late penalty with a sliding scale as they are presented within the allocated timeslot.

Course grading

Full criteria for each grade is available in the Assessment Procedure.

Grade Cut off Percent Description
1 (Low Fail) 0.00 - 29.99

Absence of evidence of achievement of course learning outcomes.

2 (Fail) 30.00 - 44.99

Minimal evidence of achievement of course learning outcomes.

Course grade description: Fails to satisfy for a Pass.

3 (Marginal Fail) 45.00 - 49.99

Demonstrated evidence of developing achievement of course learning outcomes

Course grade description: Falls short of satisfyingᅠbasic requirements for a Pass.

4 (Pass) 50.00 - 64.99

Demonstrated evidence of functional achievement of course learning outcomes.

Course grade description: Satisfies all of the basic learning requirements for the course, such as knowledge of fundamental concepts and performance of basic skills; demonstrates sufficient quality of performance to be considered satisfactory or adequate or competent or capable in the course.

5 (Credit) 65.00 - 74.99

Demonstrated evidence of proficient achievement of course learning outcomes.

Course grade description: Demonstrates ability to use and apply fundamental concepts and skills of the course, going beyond mere replication of content knowledge or skill to show understanding of key ideas, awareness of their relevance, some use of analytical skills, and some originality or insight.

6 (Distinction) 75.00 - 84.99

Demonstrated evidence of advanced achievement of course learning outcomes.

Course grade description: Demonstrates awareness and understanding of deeper and subtler aspects of the course, such as ability to identify and debate critical issues or problems, ability to solve non-routine problems, ability to adapt and apply ideas to new situations, and ability to invent and evaluate new ideas.

7 (High Distinction) 85.00 - 100.00

Demonstrated evidence of exceptional achievement of course learning outcomes.

Course grade description: Demonstrates imagination, originality or flair, based on proficiency in all the learning objectives for the course; work is interesting or surprising or exciting or challenging or erudite.

Additional course grading information

Identity verified assessment

As a course driven by a group project, identity verified assessment in ENGG4552 will be ensured by teaching staff monitoring student progress over the semester, verifying that students contribute to group discussions and presentations, and via peer evaluation.

Supplementary assessment

Supplementary assessment is available for this course.

Additional assessment information

GROUP WORK & GROUP WORK GRIEVANCES

Group work is a critical skill for engineers.ᅠA pre-requisite to this course is that you have undergone appropriate training in group work, e.g. through ENGG1100/1200/1211 or equivalent courses.

By default all group members will receive the same grade. You should use your team working skills to ensure work distribution is equitable. Furthermore, to maximise grades, you should make sure each team member is allocated tasks that play to their strength. If team issues arise, attempt to resolve this professionally and respectfully within your group. Next, bring this up at group meetings with course staff and we will provide mentoring to resolve the issues. If this is not possible, please email the course staff for a private appointment.

If team-working breaks down and affects assessmentsᅠ(e.g. team member(s) fail to contribute) a peer evaluation tool may be used to scale grades of students based on individual contributions. Significant attempts at mediation will be necessary before grades will be adjusted; the full procedure for group work grievances will be discussed in class.

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.

Additional learning resources information

Background Reading Material:

The following booksᅠare available online through the UQ library. The rest are online resources we have found useful. Which one you will need will strongly depend on the project you are undertaking.ᅠ

C.L. Dym and P.Little.ᅠEngineering Design: A Project Based Introduction. Wiley. Available from UQ library at:ᅠhttps://search.library.uq.edu.au/permalink/f/12kerkf/61UQ_ALMA2199758040003131

Oberg, E., Horton, H. L., Ryffel, H. H., & Mccauley, C. J. (2016). Machinery's Handbook Guide. New York: Industrial Press, Inc. Available fromᅠUQ library at: https://search.library.uq.edu.au/permalink/f/tbms52/TN_cdi_proquest_ebookcentral_EBC5194484

Engineering Standards Databases, available from UQ library at:ᅠhttps://guides.library.uq.edu.au/how-to-find/standards/databases:

  • SAI Global on line premium formerly Australian standards online
  • BSOL British Standards Online
  • ASTM standards and engineering digital library
  • IEEE Xplore digital library
  • ASCE Standards

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
Clear filters
Learning period Activity type Topic
Multiple weeks

From Week 1 To Week 25
(24 Feb - 26 Oct)

Lecture

Presentation of course materials

As required during the course of the year, we will use part of the weekly contact session to present relevant learning materials and/or interactively discuss relevant aspects of the course.

Learning outcomes: L01, L02, L03, L04, L05, L06, L07, L08

General contact hours

Weekly team meetings (WITH course staff)

On most weeks we will set aside part of the weekly contact session for your team to have a meeting with the course staff to discuss any and all aspects of your project tasks. You should also aim to regularly involve your industry partner in a proportion of these meetings across the course of the year.

Learning outcomes: L03, L04, L05, L07, L08

Multiple weeks

From Week 1 To Week 26
(24 Feb - 02 Nov)

Team Based Learning

Weekly team meetings (WITHOUT course staff)

It is expected that you will arrange regular (at least weekly) meetings between your team members (or relevant subsets of members, depending on your project tasking) outside of the course contact sessions, across the full course of the year. You should also aim to regularly involve your industry partner in a proportion of these meetings across the course of the year.

Learning outcomes: L03

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:

Learn more about UQ policies on my.UQ and the Policy and Procedure Library.