XMUT 101 Engineering Technology

Second Semester, 2020/2021

Prescription

This course provides a general introduction to the fundamental technical concepts needed to understand the design and engineering of electronic, mechatronics, networked and software systems. Experience is gained in basic engineering practice, with assembly and testing of basic hardware, software and networked systems, and construction of a personal computer.

Course learning objectives

Students who pass this course will be able to:
  • Understand the fundamental principles underlying Engineering, especially electronic, mechatronics, networked and software systems (BE graduate attributes 3(a)).
  • Work within a team, including breaking up and allocating tasks, managing a team, and working with other people to achieve a defined task (BE graduate attributes 2(a), 2(b) and 3(d)).
  • Communicate through explaining what they have done in coursework and reasons for it with their peers and others (BE graduate attribute 2(b)).
  • Understand the role of engineers and their responsibility to society (BE graduate attribute 1(a)).
  • Be creative and able to apply critical thinking through the design, implementation and testing of systems to solve real-world problems (BE graduate 3(b)).

Course content

It is intended to give students experience in basic engineering practice, through gaining an understanding of basic software and hardware systems and applying this knowledge to complete projects which include all aspects of these technologies.

Lecturers

Teaching Format

Due to the COVID-19 (novel coronavirus), there will be online lectures during the semester through Tencent Meeting. You will be provided with recorded lectures every week. The labs will be conducted by lecturers in XMUT:

Textbook and other Materials

For Weeks 1 - 8: The book “Digital Systems”, by R J Tocci is the recommended text.

For Weeks 9 - 16: The book “Beginning C for Arduino, Second Edition: Learn C Programming for the Arduino”, by Jack J Purdum is the recommended text.

Assessment

This course will be assessed through assignments, lab reports and two tests.

Item Weight
Assignments 12%
Labs & project 38%
Test 1 (Week 8) 25%
Test 2 (Week 17) 25%

Penalties

Work submitted:
  • 1 day after the deadline will receive a maximum mark of 90%,
  • 2 days after the deadline will receive a maximum mark of 80%,
  • 3 days after the deadline will receive a maximum mark of 70%,
  • 4 days after the deadline will receive a maximum mark of 60%.

No work will be accepted after releasing the solutions unless previously arranged with the course organiser.

Extensions

Individual extensions will only be granted in exceptional personal circumstances and should be negotiated with the course coordinator before the deadline whenever possible. Documentation (eg, medical certificate) may be required.

Submission & Return

All work is submitted through the ECS submission system, accessible through the course web pages. Marks and comments will be returned through the ECS marking system, also available through the course web pages.

Workload

In order to maintain satisfactory progress in XMUT 101, you should plan to spend 10 hours per week on this paper.
A plausible and approximate breakdown for these hours would be:

Lectures: 1-3 hours per week

Laboratories and tutorials: 2 - 4 hours per week

Writing lab reports/assignments: 3 hours

Reading, review, preparation: 2 hours

Academic Integrity and Plagiarism.

Academic integrity means that university staff and students, in their teaching and learning, are expected to treat others honestly, fairly and with respect at all times. It is not acceptable to mistreat academic, intellectual or creative work that has been done by other people by representing it as your own original work. Academic integrity is important because it is the core value on which the University's learning, teaching and research activities are based. The University's reputation for academic integrity adds value to your qualification. Plagiarism is presenting someone else's work as if it were your own, whether you mean to or not. "Someone else's work" means anything that is not your own idea. Even if it is presented in your own style, you must acknowledge your sources fully and appropriately. This includes:
  • Material from books, journals or any other printed source
  • The work of other students or staff
  • Information from the internet
  • Software programs and other electronic material
  • Designs and ideas
  • The organisation or structuring of any such material

Notes

You should always properly cite any work of others that you are including in work that you submit.

Do not lend your work to others. If someone submits work that is the same as or very similar to yours you should expect to be asked to explain and, if the explanation is not satisfactory, to get zero.

If you are ever in doubt as to whether some action you have taken may be considered as plagiarism, you should consult your lecturer and/or clearly state on the submitted work the extent of the contribution from others.
  • Do not give your answers to other students – you may get zero!
  • If you copy another student’s work (assignment/test/final exam), you will get zero.
  • Do not ask other students for their answers – it is stealing their marks.

Plagiarism and Code

If you are completing a programming project, you may be allowed to use code segments from a software library on the web, from model solutions in previous courses you have taken, or even from other students. If you do this, you must clearly indicate all of the code that has come from another source and state the source. Unless your course requirements state otherwise, you are not required to cite algorithms, data structures or source code provided with the assignment or from lecture notes. If you are in doubt about the use of code that you have not written yourself you should check with your lecturer before submitting the program. If you have had help from someone else (other than a tutor), it is always safe to state the help that you got. For example, if you had help from someone else in writing a component of your code, it is not plagiarism as long as you state (eg, as a comment in the code) who helped you in writing the method.

Classroom Policies

  • No eating, drinking, or smoking.
  • Respect classmates’ ideas, opinions, and questions.
  • No behaviour that prevents other students from learning.
  • You are welcome to visit the instructor’s office in his office hours.
  • Take good care of the laboratory facilities.
Points: 15
Prerequisites: enrolment in BE
Duration:
Starts: semester 2
Campus: XMUT