MTRX1702: Mechatronics 1 (2016 - Semester 2)
|Unit:||MTRX1702: Mechatronics 1 (6 CP)|
|Faculty/School:||School of Aerospace, Mechanical & Mechatronic Engineering|
A/Prof Rye, David
|Session options:||Semester 2|
|Versions for this Unit:|
|Site(s) for this Unit:||
|Prohibitions:||ELEC1101 OR ELEC2602 OR COSC1002 OR COSC1902.|
|Brief Handbook Description:||This unit of study aims to provide a foundation for the study of systems and embedded programming for the degree in Mechatronic Engineering.
It is based around a systems engineering approach to requirements capture, software design, implementation, debugging and testing in the context of the C programming language. Problem definition and decomposition; the design process; designing for testing and defensive coding methods; modular code structure and abstract data types; best practice in programming. Programming in teams; documentation and version control.
The C language: preprocessor, tokens, storage classes and types; arithmetic, relational and bit manipulation operators; constructs for control flow: if, switch, for, do and while; arrays; pointers and character strings; dynamic memory allocation; functions and parameter passing; derived storage classes: structures and unions; file I/O.
Dr Balamurali, Mehala
Dr Ward, James
|Tutor/s:||Krishnamurthy, Kausthub; MacKay, Jacob; Phung, Dang Khoa; Pollard, Tyrone|
|T&L Activities:||Tutorial: Laboratory-based tutorials.
Independent Study: Students are expected to undertake at least five hours of independent study per week outside of formally-timetabled classes. Students are expected to commit to private study, which may include lab work, outside of the timetabled hours. It is expected that the appropriate reference books and web-based material will be read to supplement material presented during lectures.
Attributes listed here represent the key course goals (see Course Map tab) designated for this unit. The list below describes how these attributes are developed through practice in the unit. See Learning Outcomes and Assessment tabs for details of how these attributes are assessed.
|Attribute Development Method||Attribute Developed|
|Problem definition and analysis, systematic design, implementation and fault-finding in software.||Design (Level 2)|
|Theoretical foundations of software engineering.||Engineering/IT Specialisation (Level 2)|
For explanation of attributes and levels see Engineering & IT Graduate Outcomes Table.
Learning outcomes are the key abilities and knowledge that will be assessed in this unit. They are listed according to the course goal supported by each. See Assessment Tab for details how each outcome is assessed.Design (Level 2)
Assignment Extensions and Deadlines No extension of the published due dates and times will be given outside the formal Special Consideration process unless exceptional circumstances apply. In such cases, application for an extension must be submitted in writing (e.g. by email to the Unit Coordinator), citing those circumstances. A decision will be given in writing (email).
Late Submission of Assignments Late submissions will be penalized 20% of the full mark for every day or part thereof that the assignment is late.
Must Pass Examination To pass this unit of study it is necessary to obtain a mark of not less than 45% in the Final Examination. If you do not achieve a mark of at least 45% in the Final Examination the maximum mark you can get for the unit of study is 45%.
Similarity Detection Please note that all code submitted for assessment will be checked using similarity detection software as part of the University`s academic honesty processes.
|Assessment Feedback:||Students can expect feedback for this Unit of Study through discussion during lectures and computer laboratory sessions, through participation in the forums on the Ed online platform and through written responses to questions posed via email. Students can provide feedback to the Lecturer and Tutors by discussion during lectures or tutorial/ laboratory sessions, through the Ed forum, and by submitting comments and questions by email.|
|Policies & Procedures:||See the policies page of the faculty website at http://sydney.edu.au/engineering/student-policies/ for information regarding university policies and local provisions and procedures within the Faculty of Engineering and Information Technologies.|
Note: References are provided for guidance purposes only. Students are advised to consult these books in the university library. Purchase is not required.
|Online Course Content:||Course content can be accessed via Blackboard, but is actually hosted on the Ed platform at https://edstem.com.au/courses/288/|
|Note on Resources:||Library classifications: 005.133, 621.3819, 621.39|
Note that the "Weeks" referred to in this Schedule are those of the official university semester calendar https://web.timetable.usyd.edu.au/calendar.jsp
|Week 1||Introduction; fundamental data types|
|The character of a programmer|
|Week 2||Data types|
|Compiler and linker|
|Week 3||Arithmetic operations|
|Simple Makefiles and debugging|
|Week 4||Input and output; file I/O|
|Week 5||Decision making|
|Implementing decision structures|
|Function design and implementation|
|Week 7||Scope and extent|
|Module design and implementation|
|Assessment Due: Assignment 1|
|Week 9||Pointer arithmetic|
|Assessment Due: Assignment 2|
|Week 10||Arrays and strings|
|Week 11||Bitwise operators|
|Assessment Due: Assignment 3|
|Week 12||Dynamic memory|
|The C preprocessor|
|Assessment Due: Assignment 4|
|Exam Period||Assessment Due: Final Examination|
The following is a list of courses which have added this Unit to their structure.
This unit contributes to the achievement of the following course goals:
|Design (Level 2)||Yes||50%|
|Engineering/IT Specialisation (Level 2)||Yes||50%|
These goals are selected from Engineering & IT Graduate Outcomes Table which defines overall goals for courses where this unit is primarily offered. See Engineering & IT Graduate Outcomes Table for details of the attributes and levels to be developed in the course as a whole. Percentage figures alongside each course goal provide a rough indication of their relative weighting in assessment for this unit. Note that not all goals are necessarily part of assessment. Some may be more about practice activity. See Learning outcomes for details of what is assessed in relation to each goal and Assessment for details of how the outcome is assessed. See Attributes for details of practice provided for each goal.