Course coordinator
Mr Steven Scott
Course overview
- Study period
- Semester 1, 2025 (24/02/2025 - 21/06/2025)
- Study level
- Postgraduate Coursework
- Location
- St Lucia
- Attendance mode
- In Person
- Units
- 2
- Administrative campus
- St Lucia
- Coordinating unit
- Elec Engineering & Comp Science School
This course introduces students to the Design Computing Studio stream. Students work in multidisciplinary teams to design, iterate and implement design computing projects. Students will move from concept and proposal through to the design and technical resolution of proposed designs. The projects will also enable students to develop important skills such as problem solving, reflection in action, communication and presentation.
This course introduces students to the design process in the domain of Interaction Design and Information Technology. Students will be able to apply their understanding of technology, coding, and design, gained in previous courses such as DECO1400/7140 and DECO1100/7110, to an iterative design project. Working in teams, students will follow an iterative development process to design and prototype computing solutions based on a given outline. Students will be introduced to methods and skills for the generation, refinement, and implementation of their solutions, including critical reflection, project scoping, and ethical impact analysis. Students will develop the ability to communicate design ideas effectively, identify different design approaches, and assess the impact and outcomes of these approaches on both their users and society as a whole. Additionally, they will gain skills in managing team-based projects, including conflict resolution and effective collaboration skills. These skills will be applicable in future studio subjects, including Studio 2 and Studio 3. At the end of the semester, students will present their work to teaching staff and peers at a final tradeshow.
During the first five weeks students will be given a focused overview of the design process, team collaboration, project management, ethics in design, and project planning. From week three onwards, students will form teams to collaborate on a small project that applies their understanding of HTML, CSS, and JavaScript skills, while also incorporating foundational server-side programming techniques. Students will have to work to a project outline, identify tasks and work together to produce a simple functional prototype. Studio 1 expects all students to be able to undertake both design and programming tasks.
Studio 1 is broken into a 3-hour studio session and a 2-hour practical. The studio sessions will focus on teaching broader skills, running planned activities and providing time for students to work on their projects. Practicals will focus on developing technical skills while allowing students to ask questions about their individual team projects.
DECO7180 has been reworked based on previous student feedback to make it more in-line with studio-based learning, with more focus on developing team-based learning outcomes.
Course requirements
Assumed background
It is expected that students will have completed DECO1400/DECO7140 (Introduction to Web Design) prior or concurrently to enrolling in this course. Students will be utilising and extending on their knowledge gained in DECO1400/DECO7140 in this course's project work.
Companion or co-requisite courses
You'll need to complete the following courses at the same time:
CSSE7030, DECO7140
Incompatible
You can't enrol in this course if you've already completed the following:
DECO1800
Course contact
Course staff
Lecturer
Mrs Julia Drugova
Timetable
The timetable for this course is available on the UQ Public Timetable.
Additional timetable information
This course has 5 scheduled contact hours per student each week. Students can expect to spend an additional 5 hours per week on assessment work.
Students are expected to participate fully in all class activities:
- Studios (3 hours)—introduces theory and practical design-related content to be explored and applied, initially in the individual tasks, and then in the major project (team), Support for project work, assessment and project-based presentations, and exercises related to project work.
- Studios commence in week 1.
- Practicals (2 hours)—intended to develop technical skills for use in the major project (team), and for technical project support.
- Practicals commence in week 1.
- Self-study (5 hours)—Students are expected to continue work outside of scheduled Studio and Practical times on course activities, team project assessments, and self-directed learning related to both the project and individual portfolio and reflection assessments.
End of Semester Tradeshow
Teams will demonstrate their final projects at an in-studio tradeshow. Individual teams will all be required to be present for the entire 3 hours of the in-studio tradeshow. This is an in-person tradeshow for all students in the DECO1800/7180 course. Please ensure this date is in your diary and you have cleared all other commitments.
Aims and outcomes
This course aims to:
- Introduce students to the studio class format, allowing them to apply theoretical knowledge in a practical, project-based setting.
- Allow students to collaborate effectively in multi-disciplinary teams on a design computing project while introducing key techniques for project management and teamwork.
- Develop students’ ability to communicate effectively across multiple formats, including visual, oral, and written methods.
- Develop students’ ability to critically analyse and reflect on their design projects, allowing them to assess their work and identify areas for improvement.
- Deepen students' understanding of ethical considerations in design, encouraging them to assess the societal, cultural, and moral impacts of their work.
Learning outcomes
After successfully completing this course you should be able to:
LO1.
Analyse and propose design computing solutions that aligns with the objectives and constraints of a project scope.
LO2.
Understand key course concepts and studio workflow and apply those principles in an iterative development process.
LO3.
Apply design and technical skills within a multidisciplinary team to build a minimal viable prototype.
LO4.
Apply critical thinking to reflect on and analyse the project’s development and outcomes, evaluating how well they align with user needs and the project brief.
LO5.
Understand ethical concerns related to design decisions and apply ethical principles to assess their impact on users, communities, and stakeholders.
LO6.
Apply effective team collaboration skills by demonstrating communication, problem-solving, and conflict-resolution strategies to achieve project goals.
LO7.
Understand communication and documentation strategies to effectively convey design ideas and track project development.
Assessment
Assessment summary
| Category | Assessment task | Weight | Due date |
|---|---|---|---|
| Paper/ Report/ Annotation |
Exploratory Research Report
|
1 |
21/03/2025 3:00 pm |
| Presentation |
Initial Pitch Presentation
|
2 |
10/04/2025 12:00 pm |
| Computer Code, Creative Production/ Exhibition, Paper/ Report/ Annotation, Practical/ Demonstration |
Prototype Development Sequence
|
3 |
Team Report is due on BlackBoard 23/05/2025 3:00 pm Tradeshow in the scheduled Studio 29/05/2025 12:00 pm |
| Paper/ Report/ Annotation, Reflection |
Individual Project Analysis Report
|
4 |
9/06/2025 3: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
Exploratory Research Report
- Team or group-based
- Mode
- Written
- Category
- Paper/ Report/ Annotation
- Weight
- 1
- Due date
21/03/2025 3:00 pm
- Learning outcomes
- L01, L02, L04, L07
Task description
Both the design process and effective teamwork require clear goals and objectives. This assessment is designed to help you define your goals. It’s important to note that a goal isn’t always about building something or solving a specific problem. In this assessment, you will explore potential avenues of concern and examine the impact of specific data sets. While your oral presentation and design guide due in Week 9 will focus on what you're building, this report delves into the underlying "why," helping you set clear, purposeful goals for your project.
This report should outline your intended domain, the challenges and impacts you may face, and the knowledge you need to acquire in order to move forward. Additionally, you will define your design goals and establish what you hope to achieve as a team. This document serves as a starting point, outlining your objectives and providing a clear vision of what the project could become. It is something that you will refer back to during the semester.
Artificial Intelligence (AI) and Machine Translation (MT)
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 will be required to demonstrate detailed comprehension of their written submission independent of AI and MT tools
Submission guidelines
Submission is on BlackBoard.
Deferral or extension
You cannot defer or apply for an extension for this assessment.
This course uses team-based assessment. No extensions or deferrals are possible. 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.
Late submission
A penalty of 1 grade for each 24 hour period from time submission is due will apply for up to 7 days. After 7 days you will receive a mark of 0.
Initial Pitch Presentation
- Team or group-based
- In-person
- Mode
- Oral
- Category
- Presentation
- Weight
- 2
- Due date
10/04/2025 12:00 pm
Task description
As a designer, one of your primary roles will be to explain and justify comprehensive design solutions to the people who will use or implement them. Strong communication skills are essential for conveying your ideas persuasively, justifying your design choices, and explaining the rationale behind your work. You will also need the ability to articulate your design concepts clearly and succinctly, not only for collaborating with your peers and ensuring internal alignment, but also for presenting your vision to external stakeholders.
For this task, you will deliver an oral presentation (with slides) to the class, outlining the design approach you have chosen for your project. The presentation should provide a clear and cohesive overview of your design journey, highlighting not only what you aim to achieve but also the reasoning behind why your approach is the most appropriate. You should describe the envisioned final product, explaining its intended use and how it will meet the needs of your users. Additionally, you should address any potential ethical concerns related to your design. Finally, you will outline the key steps needed to reach a Minimal Viable Prototype by the end of the semester.
Before Studio in Week 7:
- Submit your slides and script for your presentation.
In Studio during Week 7:
- Deliver a 5-minute presentation, followed by 10 minutes for Questions and Answers.
Artificial Intelligence (AI) and Machine Translation (MT)
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 will be required to demonstrate detailed comprehension of their written submission independent of AI and MT tools
Submission guidelines
Presentation will take place during the scheduled studio session. Slides and Design Guide must be submitted to BlackBoard before the Studio starts. A printed version of your design guide will need to be handed to the Teaching Staff before your presentation begins.
Deferral or extension
You cannot defer or apply for an extension for this assessment.
This course uses team-based assessment. No extensions or deferrals are possible. 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.
Late submission
100% Late Penalty after 1 hour grace period. The one-hour grace period is recorded from the time the submission is due.
Prototype Development Sequence
- Identity Verified
- Team or group-based
- In-person
- Mode
- Activity/ Performance, Oral, Product/ Artefact/ Multimedia, Written
- Category
- Computer Code, Creative Production/ Exhibition, Paper/ Report/ Annotation, Practical/ Demonstration
- Weight
- 3
- Due date
Team Report is due on BlackBoard 23/05/2025 3:00 pm
Tradeshow in the scheduled Studio 29/05/2025 12:00 pm
Task description
The development process is rarely a one-time effort; it requires continuous refinement and adaptation, driven by feedback, testing, and evolving requirements. Through this iterative process, designers have the opportunity to refine their ideas, address challenges more effectively, and ultimately create solutions that better meet the needs of users. One of the core elements of this process is collecting data from prototypes, which helps inform decisions, validate assumptions, and guide the next steps of development. You will need to develop and strengthen interpersonal skills, particularly in time management, project understanding, and inter-team communication and collaboration. Studio 1 provides students with the opportunity to practice these skills while working together to explore a problem space.
This sequence is broken down into two major deliverables:
- Week 12: Minimal Viable Prototype and Project Handover Document.
- Week 13: Tradeshow.
This assessment is designed to run through the entire design process and provides an opportunity for students to receive feedback from teaching staff allowing them to make changes based on that feedback. By the end of the semester, your team will have developed a small, functional prototype of your proposed design. While this is still a prototype and does not need to be polished, its primary focus should be on demonstrating the core functionality of what you have created.
Minimal Viable Prototype and Project Handover Document.
For this assessment, you will submit your final MVP along with a Handover Document that explains what you built, how you built it, your design decisions, and the goals you aimed to achieve. The prototype serves to showcase the first step in your design process, illustrating how, with more time and refinement, what you could achieve. The submission for this task is divided into three deliverables:
- You will submit your final codebase to BlackBoard by the end of Week 13.
- Along with your code, you will submit a comprehensive report (details below).
- You will demonstrate your Minimal Viable Prototype (MVP) at the tradeshow during Week 13 studio.
Along with your codebase, you will submit a Project Report that details your design process and final MVP. The report should provide an overview of the project, including the problem space, target users, and how your design fits within the broader domain. It should also outline the roles and responsibilities of each team member, highlighting the contributions made by each individual. The report should include a critical analysis of how well your design approach addressed user needs, reflecting on both the strengths and weaknesses of your solution. Additionally, it should break down the individual components of your MVP, including user flow and experience, along with the rationale behind your design decisions. You should also discuss the ethical concerns related to your project, focusing on how your design may impact its users and the world at large. This includes considering potential unintended consequences, privacy concerns, accessibility, and how your design fits within broader societal contexts. If applicable, you can incorporate individual documentation created by members of team, provided you reference the creator of the media.
Tradeshow
In Week 13 studio, you will demonstrate your project to your peers and teaching staff in a tradeshow/exhibit format. Each team will be allocated a brief time slot during the exhibit to showcase and provide a short demonstration of their final prototype. Following the demonstration, there will be a question-and-answer session designed to explore your understanding of your project’s domain, the specific contributions of each team member, and how your project fits within the broader context of the field. It is important that each team member is prepared to answer questions, as everyone must be able to articulate their role, the design decisions made and showcase their understanding of the project as a whole.
Artificial Intelligence (AI) and Machine Translation (MT)
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 will be required to demonstrate detailed comprehension of their written submission independent of AI and MT tools
Submission guidelines
- Team Tradeshow Final Prototype, code should be submitted to BlackBoard before the Studio starts (by only one team member), AND an In-Studio step-through demonstration of your Tradeshow Final Prototype (all team members must attend in person and present).
- Team Final Report: One member of your team will submit a single electronic file via BlackBoard.
Deferral or extension
You cannot defer or apply for an extension for this assessment.
Team Tradeshow Final Prototype: This course uses team-based assessment where oral demo sessions occur in class. No extensions or deferrals are possible. If teams encounter extraordinary difficulties in meeting a deadline, they should contact the course coordinator in advance of the due date. All team submissions received after the due date will either; (1) receive a zero mark (or failing grade), or (2) if an earlier version of the team’s work was submitted then this will instead be graded.
Team Final Report: 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.
Late submission
Team Tradeshow Final Prototype: 100% Late Penalty (no grace period)
Team Final Report: A penalty of 1 grade for each 24-hour period from time submission is due will apply for up to 7 days. After 7 days you will receive a mark of 0.
Individual Project Analysis Report
- Hurdle
- Mode
- Written
- Category
- Paper/ Report/ Annotation, Reflection
- Weight
- 4
- Due date
9/06/2025 3:00 pm
- Learning outcomes
- L01, L04, L05, L07
Task description
Critical reflection is an essential skill for designers, enabling them to objectively evaluate their work and identify what was successful and what areas need improvement. This process supports ongoing personal and professional growth, and to foster deeper understanding of the impact on their users and society in general.
To help facilitate this reflection, students are required to document their work throughout the semester, starting in Week 6. This documentation will serve as scaffolding, enabling students to reflect on and recall design decisions and key development activities they undertook throughout the semester. It can take various forms, including written notes, photographs, video footage, or audio recordings. You will be able to share this documentation with teaching staff during studio sessions, where feedback and discussion will help you refine your process.
At the end of semester, you will take this documentation and use it as evidence of the work that you have done throughout the semester in the form of an Individual Reflection Report. This report will highlight the work that you did throughout the semester in relation to your project. This is not a journal of what you did, rather critical analysis of the project through from your point of view. Topics of conversation should include what steps you took, what you built and why, what went right/wrong and the impact on the end result and should always take the bigger picture into account. The report needs to be able to stand on its own, briefly explaining to the reader your concept, your role within the team, the problem space, target user, and potential solution.
Artificial Intelligence (AI) and Machine Translation (MT)
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 will be required to demonstrate detailed comprehension of their written submission independent of AI and MT tools
Hurdle requirements
To pass the course, students must achieve a Pass (+/-) for this individual assessment item. Failure to meet this requirement will result in the final grade being capped at a 3, regardless of performance in other assessment items.Submission guidelines
Submission is on BlackBoard.
Deferral or extension
You may be able to apply for an extension.
The maximum extension allowed is 7 days. Extensions are given in multiples of 24 hours.
This course uses a progressive assessment approach where feedback and/or detailed solutions will be released to students within 14 days.
Note that extensions on an assessment item due in the exam period may lead to an INC grade being entered for the course.
Late submission
A penalty of 1 grade for each 24 hour period from time submission is due will apply for up to 7 days. After 7 days you will receive a mark of 0.
Course grading
Full criteria for each grade is available in the Assessment Procedure.
| Grade | Description |
|---|---|
| 1 (Low Fail) |
Absence of evidence of achievement of course learning outcomes. Course grade description: Absence of evidence of achievement of course learning outcomes: The student has failed to submit multiple pieces of assessment and has failed to demonstrate any knowledge or understanding of the course concepts. |
| 2 (Fail) |
Minimal evidence of achievement of course learning outcomes. Course grade description: Minimal evidence of achievement of course learning outcomes: The student has failed to demonstrate accurate, relevant knowledge or understanding of the underlying concepts taught in the course. |
| 3 (Marginal Fail) |
Demonstrated evidence of developing achievement of course learning outcomes Course grade description: Demonstrated evidence of developing achievement of course learning outcomes: The student has demonstrated some knowledge of the course, but the student has only a limited understanding of the underlying concepts. The submitted work is largely inaccurate or irrelevant, demonstrating a rudimentary level of technical proficiency. |
| 4 (Pass) |
Demonstrated evidence of functional achievement of course learning outcomes. Course grade description: Demonstrated evidence of functional achievement of course learning outcomes: The student has demonstrated basic skills and competency and has sound knowledge of relevant information. The submitted work demonstrates at least a basic understanding of the underlying concepts, demonstrating a satisfactory level of technical proficiency. |
| 5 (Credit) |
Demonstrated evidence of proficient achievement of course learning outcomes. Course grade description: Demonstrated evidence of proficient achievement of course learning outcomes: The student has demonstrated basic skills and competency and has sound knowledge of relevant information. The submitted work demonstrates a sound understanding of the underlying concepts, demonstrating a good level of technical proficiency. |
| 6 (Distinction) |
Demonstrated evidence of advanced achievement of course learning outcomes. Course grade description: Demonstrated evidence of advanced achievement of course learning outcomes: The student has demonstrated key concepts and there is a clear ability to apply these to the design & development process. The submitted work demonstrates a strong level of technical proficiency. |
| 7 (High Distinction) |
Demonstrated evidence of exceptional achievement of course learning outcomes. Course grade description: Demonstrated evidence of exceptional achievement of course learning outcomes: The student has demonstrated key concepts, used with credible judgment in the design & development process. There is evidence of critical analysis and synthesis of information, concepts and skills from different aspects of the course. The submitted work demonstrates a high level of technical proficiency. |
Additional course grading information
Calculation of Final Grade
Your final grade will be calculated as a weighted average of your assessment grades, using the same formula as used for calculating your GPA. In this case, U equals the weighting for that particular assessment item, and G equal to the grade for the assessment item.
Example:
If you receive the following grades:
Individual Assessment
- 1 Individual Reflective Report - Credit (5), Weighting x 4 — (5x4)
Team Assessment
- 2: Exploratory Research Report - Distinction (6), Weighting x 2 — (6x1)
- 3: Initial Pitch Presentation & Design Guide - Distinction (7), Weighting x 2 — (7x2)
- 4: MVP & Tradeshow - Credit (5), Weighting x 3— (4x3)
Your final grade will be calculated as:
- ((5*4)+(6*1)+(7*2)+(4*3))/(4+1+2+3)
- 52/10 = 5.2 = Credit (5)
Final grades will be initially constructed from the separate assessment grades according to the assessment weightings and then reviewed and moderated based on overall performance across the course.
Identity-Verified Assessment with Hurdles (IVAH) Requirement
In order to meet IVAH requirements and to pass the course, students must achieve a Pass (+/-) for the Individual Assessment items. Failure to meet this requirement will result in the final grade being capped at a 3, regardless of performance in other assessment items.
Teaching staff monitor active participation in Studio sessions throughout the semester. Based on this monitoring the teaching team are aware of the degree to which each student actively contributes to individual learning and major project (team) outputs. If students have not actively participated throughout, further evidence may be requested of individual students to assess the level of active participation. The Course Coordinator reserves the right to moderate team member grades in the event of varied contributions to team effort.
The final grade for the course will be initially constructed from the individual grades according to assessment weightings. At the discretion of the course coordinator, final grades may be moderated.
BlackBoard/Turnitin Submissions:
When submitting your assessment items through BlackBoard/Turnitin, please allow plenty of time for the submission to be uploaded as many students will be attempting the same task at the same time. Be sure to allow enough time for uploading of assessment files. It is your responsibility to check that submissions have been uploaded correctly and ensure that you have received a digital receipt.
Supplementary assessment
Supplementary assessment is not available for some items in this course.
The course involves teams working on a semester long software/IT system design and prototype software/IT build project, including staged presentations and critical reflection. It is not possible replicate team-based assessment of this nature (prototype development, staged product demonstrations and critical reflections, and final seminar/trade show) in a supplementary context. If you receive an overall grade of 3 in this course, supplementary assessment will only be available to students whose failure is due to failure on the individual assessment items. Due to the design and development aspects of this team-based assessment over time, supplementary assessment will not be available to students who receive a failing grade on the team assessment items (Approved by EAIT AD-A).
Additional assessment information
1.__Qualitative Grading
Grades for assessment during the semester will identify your work as being of a particular standard from the following list:
- Low Fail (absence of evidence of achievement)
- Fail (minimal evidence of achievement)
- Marginal Fail (developing achievement)
- Pass (functional achievement)
- Credit (proficient achievement
- Distinction (advanced achievement)
- High Distinction (exceptional achievement)
Within each category, there may be a further qualifier of + or - to indicated that the work is respectively at the upper or lower bounds of the category. This style of assessment is intended for formative feedback on progress, in combination with regular design critique in Studios. These grades map directly to the standard UQ Grade descriptors (from https://ppl.app.uq.edu.au/content/3.10.02-assessment#Procedures Appendix 7.1). Note, that percentages or numerical marks are not required in grading assessment or for calculating grade cut-offs. Percentage cut-offs are primarily employed in courses that utilise quantitative (numerical based) methods for marking.
2.__Team-based Assessment
The course expects every team member to contribute to both design and development tasks. Teams working in industry are expected to plan to meet deadlines and allow for contingencies and other issues as they arise through good team management and appropriate redundancy in workload allocation, which also includes covering for colleagues when they are unable to fully contribute due to short-term illness, etc. The same is expected of teams in this course and this will be the default expectation for team assessment in this course. If more extreme circumstances occur, they must in the first instance contact teaching staff before upcoming deadlines to discuss the situation.
3.__Having Troubles?
If you are struggling with any aspect of the course material, you should seek help. Course staff are available to address your questions and concerns. However, if you feel uncomfortable discussing issues with teaching staff, UQ Student Services and the Student Union offer additional support for various challenges. UQ Student Services provides assistance with study skills, exam preparation, writing support, financial aid, personal issues, and disability services, while the UQ Student Union offers support for Welfare & Well-being. If you are not satisfied with the outcome of your discussion with teaching staff, you may escalate the issue to 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.
Additional learning resources information
Notices
Notices regarding the course will be posted onﾠBlackboard.
Web and MS Teams
This course supports communications through Microsoft Teams. The course MS Teams site will contain important information and links to other sites related to the course. You must be enrolled in the course to access this content.
Q&A
Questions about the course content will be answered on EdDiscussion, available via BlackBoard menu.
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 From Week 1 To Week 13 |
Studio |
Studios Studios introduce both theoretical and practical design content, which students explore and apply first through individual tasks and then in team projects. Support is provided for project work, including assessments, project-based presentations, and exercises. This culminates in the final in-studio tradeshow presentations. Learning outcomes: L02, L03, L04, L05, L06, L07, L08, L09 |
Practical |
Practicals Practicals offer activities and tasks that help students build on the technical skills learned in other subjects. These sessions are designed to develop technical abilities for the Major Project (Team) and provide support for technical aspects of the project. Practical exercises aim to inform and refine concepts that can be applied to projects. Learning outcomes: 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 - 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: