Coordinator for the Introduction to your Discipline module: Dr John Codrington (john.codrington@adelaide.edu.au)
Coordinator for the Introduction to Programming for Engineers module: Dr Cheryl Pope (cheryl.pope@adelaide.edu.au)

Lecturers for Introduction to your Discipline module:
Various (See MyUni)

Lecturers for the Introduction to Programming for Engineers module:
Ali Shemshadi (ali.shemshadi@adelaide.edu.au)

Any questions related to the specific lecture or assignment content should be addressed firstly to the lecturer in question. All course
coordination or other questions should be directed to the appropriate Course Coordinator.

The two modules in your course will be taught in parallel throughout the semester. You can find a schedule of the topics, and the tutorial and practical exercises on Canvas (MyUni).

On successful completion of this course students will be able to:

 

1	Explain what an Engineer is and what skills and knowledge are required to be an Engineer;
2	Apply design solutions to programming problems;
3	Demonstrate how to translate solutions into computer programs;
4	Explain programming constructs of the C and MATLAB programming languages;
5	Apply their knowledge of programming and problem solving to the development of C and MATLAB programs;
6	Discuss modern computing technology, and the place that programming has within the Engineering domain;
7	Recognise the need to undertake lifelong learning;
8	Demonstrate how to frame and solve unstructured problems; and
9	Apply problem-solving principles.

 
The above course learning outcomes are aligned with the Engineers Australia Stage 1 Competency Standard for the Professional Engineer.
The course is designed to develop the following Elements of Competency: 1.2   1.5   1.6   3.1   3.2   3.3   3.5   

The required text-book for Introduction to Programming for Engineers module is: Matlab: A Practical Introduction to Programming and Problem Solving Fourth Edition by Stormy Attaway, publisher: Elsevier,  ISBN 9780128045251

The textbook Problem solving with C++, by Walter Savitch is recommended for the C part.

Students are expected to attend lectures, collaborative sessions and also their supervised practical sessions. These practical sessions will be crucial to developing your understanding of the course material, and will provide access to additional assistance from practical supervisors.

Introduction to your Discipline:
Copies of lecture notes, lecture recordings and additional resources will be provided online through the MyUni system. Students are expected to check the MyUni website frequently for announcements and new resources.

Introduction to Programming for Engineers:
Copies of lecture notes, lecture recordings and additional resources will be provided online through the MyUni system. Any example programs demonstrated in lectures will be made available online after the lecture. Discussion forums will also be made available on the course website. Students should enrol in the course as soon as possibleand are expected to check the MyUni website frequently for announcements and new resources.

The course will be taught through a combination of lectures, collaborative sessions and supervised practical sessions.

Each lecture session will contain a mixture of:

• Explanations, to introduce new concepts;
• Demonstrations, to see the concept in action;
• Brief exploration, worksheets or quizzes, where you can check your understanding.

Introduction to Programming for Engineers practical sessions:

Many programming examples will be worked in small groups during the collaborative workshop sessions. You can talk with your group members, and to a lab supervisor to experiment and see how things work. Attendance and participation at these sessions is recorded and assessed. 

The supervised practical sessions will, except where explicitly stated by the lecturer, require students to individually prepare solutions to practical exercises. The supervisors can help you when you get "stuck", and will assess your work and assign a mark. The purpose of these practical sessions is for students to apply the examples and concepts discussed in lectures and collaborative sessions.

Students are expected to attend all scheduled classes. In addition to the schedule contact hours, students are expected to spend 3-5 additional hours per week in preparation of assignment work, and reviewing and understanding the course topics.

Introduction to your Discipline:
There is one 1hr class each week for this module. There is one assessment task that runs over the whole semester.

Introduction to Programming for Engineers:

There is an average of 3 one-hour lecture sessions each fortnight, (see the MyUni page of the course for the schedule), a two-hour workshop each week, and  (from week 2) a two-hour supervised practical session each week.

Students are expected to attend all scheduled classes. In addition to the  schedule contact hours, students are expected to spend 3-5 additional  hours per week in preparation of assignment work, and reviewing and understanding the course topics.

Note that programming is like any skill --- if you want to get better, you need to practice. Long-term data confirms that this skill needs to be learned over several weeks.

A schedule of the topics that will be covered in each lecture, a list of workshop topics, and the practical exercises can all be found on MyUni for both modules.

Introduction to Programming for Engineers:

The practical examinations are intended to assess the student’s knowledge in practical application of the concepts taught in lectures, specifically in designing and developing programming solutions. The practical examinations are summative assessment.

Assignments and Practical exercises are both formative and summative and extend the work done in the collaborative sessions. Assignments are used to help assess whether the required graduate attributes are being developed.  Written feedback will be provided for some of the assessment work.

The examinations are summative assessment and are intended to assess the student’s knowledge and understanding of the course material.

Not applicable.

Assessment Task	Weighting (%)	Individual/ Group	Formative/ Summative	Due (week)*	Hurdle criteria	Learning outcomes
Programming Practice	24	Individual	Summative
Practical Exams	20	Individual	Summative
Final Exam	50	Individual	Summative
Reflective Case Study	6	Individual	Summative	Week 11		1. 7. 8. 9.
Total	100

* The specific due date for each assessment task will be available on MyUni.
 
This assessment breakdown complies with the University's Assessment for Coursework Programs Policy.
 

The written examination is a minimum performance hurdle.

This means that to pass the course, students are required to obtain:

• At least 40% of the available marks for the final exam.
• At least 50% overall mark.

If a student does not achieve 40% in the final written exam component, their overall mark will be capped at 44% (F).

Introduction to Programming for Engineers:

In workshops you are expected to attend and actively participate and contribute for each session. There are 12 workshops worth 0.5% each up to a capped total of 5% (this means you must participate in at least 10 of the 12 workshops to get your maximum workshop mark). 

Start working on each practical exercise as early as possible, as they can take more that one 2-hour session to complete. Due to the very tight schedule for this course you must be present in the lab, and get your work marked by a lab supervisor in the week your work is due. To enable work to be marked off you must have your work ready to demonstrate and explain. If you are not able to start your  demonstration immediately the demonstrators are instructed to move on  and come back after marking others. You will recieve some-on-the-spot  feedback. Where warranted,  general feedback on each exercise will be provided in lectures. 

Practical exams are carried out under exam conditions. These sessions will either be on paper or on the computer (details to be announced in advance of each exam). The exams will run for one hour with the remaining hour of the practical session dedicated to administration and marking.

Mapping of Assessment to ICT Core Body of Knowlege (CBOK)*
*CBOK categories are explained in section 4 of "The-ICT-Profession-Body-of-Knowledge"; numbers assigned correspond to the Bloom taxonomy (see page 26 of the same document).

Assessment	Abstraction	Design	Programming	Communication
Practicals	3	3 or 4	3	3
Practical Exams		3	3
Assignments	3	3	3	3
Final Exam	2	2 to 4	2 to 5	3

Introduction to your Discipline:

The assessment for the Introduction to your Discipline module will consist of an expositional essay including a case study and reflective discussion of what it takes to be a professional engineer.

Introduction to Programming for Engineers

Practical exercises will be submitted electronically to Moodle and will be assessed by a tutor during the supervised practical sessions. 

Note every time you submit some work (either on paper, or electronically via the web), you are implicitly saying to the University "The work I have just submitted was (substantially) done by me". The core of this statement is "I didn't copy it" --- neither from another student, nor from any other person, nor from the web.


Introduction to your Discipline

Submission of the expositional essay will be hardcopy via the submission boxes on level 2 of Engineering South.