ENGG1001
Introduction to Engineering Computing
暂无已安排的考试。
关于 ENGG1001
ENGG1001 is UQ's introduction-to-computing course for engineering students, taught in Python. It assumes no prior programming experience and is organised into three modules: Python fundamentals (variables, control flow, loops, functions, lists, dictionaries, strings, file I/O), NumPy and data analysis (ndarrays, array creation and slicing, floating-point precision, datetime64, vectorisation and broadcasting, boolean indexing and aggregation, matplotlib), and object-oriented programming (classes, encapsulation, magic methods, class versus instance variables, inheritance, method resolution order, abstract base classes and polymorphism). The final exam is heavily weighted toward code tracing, so the StudyPilot question bank focuses on the exact question types that appear on past papers, each with a worked step-by-step solution.
考试形式
The ENGG1001 final exam is paper-based and answered on a Gradescope answer sheet. It is 40 multiple-choice questions worth 1 mark each (40 marks total), with 120 minutes of working time plus 10 minutes of planning time (about 2 hours). The exam is closed-book: no notes are allowed, only a Casio FX-82 series or other UQ-approved calculator, and no phones or computers. Two marking tips from past papers: if the code would raise an error, choose Error; when several options look correct, pick the most appropriate one. Coverage by position on past papers: Q1-14 basic syntax, Q15-27 NumPy and matplotlib, Q28-40 object-oriented programming, where the inheritance / MRO tracing question is always tested. Always check the current semester's course profile for any changes.
这里还没有内容,我们每周都会新增材料。
这里还没有内容,我们每周都会新增材料。
It is a 2-hour paper-based exam with 40 multiple-choice questions worth 1 mark each, answered on a Gradescope sheet. It is closed-book and only a UQ-approved calculator is allowed.
All three modules: Python fundamentals, NumPy and data analysis, and object-oriented programming. Each question is tagged by topic so you can drill your weakest area.
Code tracing across all three modules, and in OOP the inheritance / method resolution order (MRO) tracing question appears on every past paper, so it is worth practising until it is automatic.