ENGGEN 131 : Introduction to Engineering Computation and Software Development

Engineering

2025 Summer School (1250) (15 POINTS)

Course Prescription

Introduction to problem solving in engineering through the use of the software package MATLAB, and the programming language C.

Course Overview

Many of the engineering computations you will meet over the course of your degree can be done much more efficiently with the aid of a computer program.  Developing a basic level of computer programming competence is important regardless of which engineering specialization you pursue and it is extremely useful to be able to develop your own software.

This course is divided into two halves. The first half will introduce you to programming using the software package MATLAB. The second half will introduce you to the high level programming language C.   Both halves focus on teaching you core programming and software development concepts, within the context of solving engineering problems.  

Being exposed to two different programming languages that are used in industry will allow you to develop a basic level of competency in both languages as well as providing an opportunity to see how programming languages can differ and why you might prefer one over the other.  Learning two languages also emphasizes how core programming concepts  are transferable from one  programming languages to another.  MATLAB and C are also used in a range of other engineering courses.

Course Requirements

Restriction: ENGSCI 233, 331

Capabilities Developed in this Course

Capability 3: Knowledge and Practice
Capability 4: Critical Thinking
Capability 6: Communication

Learning Outcomes

By the end of this course, students will be able to:
  1. Describe what software engineering is and understand the differences between interpreted and compiled programming languages, demonstrating the ability to create and run programs in both interpreted and compiled development environments. (Capability 3.1)
  2. Apply a problem-solving methodology to develop an algorithm for solving a problem, using pseudocode and flowcharts where appropriate, and translate that algorithm into code, using scripts and/or functions as appropriate. (Capability 3.1 and 4.1)
  3. Produce well-written human-readable code that follows standard style guidelines, including the use of comments, appropriate variable names, correct indentation, suitable layout and the avoidance of unnecessary repetition. (Capability 3.1 and 6.1)
  4. Test code to determine if it works as expected, identifying and fixing any software bugs present and improving performance, making use of a debugger where appropriate. (Capability 3.1)
  5. Obtain user input from within a program and display information to users using appropriately formatted text and/or graphics. (Capability 3.1)
  6. Create and manipulate variables, arrays and data structures that can represent a range of data including logical values, numerical values, strings, pointers, vectors, matrices and images. (Capability 3.1)
  7. Control program flow through the application of logical operators, conditional statements and loops. (Capability 3.1)
  8. Solve a range of engineering computational problems, including those that require calculus and linear algebra, by writing computer code and calling existing in-built functions and libraries where appropriate. (Capability 3.1 and 4.1)
  9. Write programs that can read and write data stored in computer files. (Capability 3.1)
  10. Work with higher levels of abstraction including writing recursive functions and functions which take as inputs other functions. (Capability 3.1)

Assessments

Assessment Type Percentage Classification
Laboratories 10% Individual Coursework
Projects 18% Individual Coursework
Test 20% Individual Test
Assignment 2% Individual Coursework
Final Exam 50% Individual Examination
Assessment Type Learning Outcome Addressed
1 2 3 4 5 6 7 8 9 10
Laboratories
Projects
Test
Assignment
Final Exam

A passing mark is 50% or higher, according to University policy.

Late labs and assignments are not accepted unless an extension request is lodged using the extension request form, along with a valid reason, AND that request is approved.

Late projects are accepted but have a late penalty applied of 4% of the total mark for each hour late (which means that after 25 hours, it is impossible to score more than zero).  Note that if an extension request is lodged for a project using the extension request form, along with a valid reason, AND that request is approved, then the approved extension date becomes the new due date.

This course uses Exam mode C - In-person invigilated exam on paper.

Students must sit the exam to pass the course. Otherwise, a DNS (did not sit) result will be returned.

A student's final mark for the course may not exceed their exam mark by more than 10 percentage points.

Teaching & Learning Methods

This course is run in studio mode, where each 2-hour class includes both up-front teaching and students working through problems, with staff on hand to help.

Workload Expectations

This course is a standard 15 point course and students are expected to spend upwards of 20 hours per week involved in each 15 point summer school course that they are enrolled in (a single course equates to 150 hours of work and for summer school you have only 6 weeks to complete this work).

For this course, each week you can expect 8 contact hours (a mixture of lectures and labs), 2 hours of reading and thinking about the content and 10+ hours of work on programming which includes finishing lab tasks, doing projects and/or test preparation.

There are two large projects (one for MATLAB and one for C).  Unless you manage your time well, you will likely need to spend a significant number of hours on these projects just before each is due.  

Delivery Mode

Campus Experience

Attendance is expected at scheduled activities, including lectures and labs, to complete some course components ( the lab tasks can be submitted online, but help is obtained by attending in person).  Note that in summer school, the lectures and labs are combined into the same time slots rather than having dedicated time slots for each.  This means each 2-hour session will feature a mix of presentation of material and working on lab tasks.  It is highly recommended that you attend *all* 2-hour sessions.

Lectures will be available as recordings (but as per the note above, we recommend attending in person).
If you can't attend in person, it is recommended that you attend via the live stream option.

Attendance on campus is required for the test and exam.


Learning Resources

Course materials are made available in a learning and collaboration tool called Canvas which also includes reading lists and lecture recordings (where available).

Please remember that the recording of any class on a personal device requires the permission of the instructor.

There are two course books (hard copies are available for purchase from UBIQ and pdf versions are available for free from Canvas).

Health & Safety

Students must ensure they are familiar with their Health and Safety responsibilities, as described in the university's Health and Safety policy.

Student Feedback

At the end of every semester students will be invited to give feedback on the course and teaching through a tool called SET or Qualtrics. The lecturers and course co-ordinators will consider all feedback and respond with summaries and actions.

Your feedback helps teachers to improve the course and its delivery for future students.

Class Representatives in each class can take feedback to the department and faculty staff-student consultative committees.

Students expressed concern that it was challenging to keep up with the pace of the course, especially as the assessment schedule was so packed.  Summer school is, by its nature, very fast-paced, and it can be difficult to catch up if you fall behind. We will be piloting livestreaming the classes, as a way of enabling people to engage with the course, even on days they can't make it to class physically.

Academic Integrity

The University of Auckland will not tolerate cheating, or assisting others to cheat, and views cheating in coursework, tests and examinations as a serious academic offence. The work that a student submits for grading must be the student's own work, reflecting their learning. Where work from other sources is used, it must be properly acknowledged and referenced. A student's assessed work may be reviewed against electronic source material using computerised detection mechanisms. Upon reasonable request, students may be required to provide an electronic version of their work for computerised review.

Class Representatives

Class representatives are students tasked with representing student issues to departments, faculties, and the wider university. If you have a complaint about this course, please contact your class rep who will know how to raise it in the right channels. See your departmental noticeboard for contact details for your class reps.

Inclusive Learning

All students are asked to discuss any impairment related requirements privately, face to face and/or in written form with the course coordinator, lecturer or tutor.

Student Disability Services also provides support for students with a wide range of impairments, both visible and invisible, to succeed and excel at the University. For more information and contact details, please visit the Student Disability Services’ website http://disability.auckland.ac.nz

Special Circumstances

If your ability to complete assessed coursework is affected by illness or other personal circumstances outside of your control, contact a member of teaching staff as soon as possible before the assessment is due.

If your personal circumstances significantly affect your performance, or preparation, for an exam or eligible written test, refer to the University’s aegrotat or compassionate consideration page https://www.auckland.ac.nz/en/students/academic-information/exams-and-final-results/during-exams/aegrotat-and-compassionate-consideration.html.

This should be done as soon as possible and no later than seven days after the affected test or exam date.

Learning Continuity

In the event of an unexpected disruption we undertake to maintain the continuity and standard of teaching and learning in all your courses throughout the year. If there are unexpected disruptions the University has contingency plans to ensure that access to your course continues and your assessment is fair, and not compromised. Some adjustments may need to be made in emergencies. You will be kept fully informed by your course co-ordinator, and if disruption occurs you should refer to the University Website for information about how to proceed.

Student Charter and Responsibilities

The Student Charter assumes and acknowledges that students are active participants in the learning process and that they have responsibilities to the institution and the international community of scholars. The University expects that students will act at all times in a way that demonstrates respect for the rights of other students and staff so that the learning environment is both safe and productive. For further information visit Student Charter https://www.auckland.ac.nz/en/students/forms-policies-and-guidelines/student-policies-and-guidelines/student-charter.html.

Disclaimer

Elements of this outline may be subject to change. The latest information about the course will be available for enrolled students in Canvas.

In this course you may be asked to submit your coursework assessments digitally. The University reserves the right to conduct scheduled tests and examinations for this course online or through the use of computers or other electronic devices. Where tests or examinations are conducted online remote invigilation arrangements may be used. The final decision on the completion mode for a test or examination, and remote invigilation arrangements where applicable, will be advised to students at least 10 days prior to the scheduled date of the assessment, or in the case of an examination when the examination timetable is published.

Published on 04/11/2024 06:37 p.m.