Note: This unit is an archived version! See Overview tab for delivered versions.
AMME4122: Engineering Project B (2018 - Semester 2)
| Unit: | AMME4122: Engineering Project B (6 CP) |
| Mode: | Normal-Day |
| On Offer: | Yes |
| Level: | Senior Advanced |
| Faculty/School: | School of Aerospace, Mechanical & Mechatronic Engineering |
| Unit Coordinator/s: |
Dr Fiford, Rod
|
| Session options: | Semester 1, Semester 2 |
| Versions for this Unit: | |
| Site(s) for this Unit: |
http://www.aeromech.usyd.edu.au/cgi-bin/show_unit?=AMME4121& |
| Campus: | Camperdown/Darlington |
| Pre-Requisites: | [AMME4121 and 30 credit points of at least third year units of study]. |
| Prohibitions: | AMME4111 OR AMME4112 OR AMME4010. |
| Brief Handbook Description: | To complete the research requirement for their engineering degree, students now have a choice of either completing Thesis A/B (AMME 4111/AMME4112) or Engineering Project A/B (AMME 4121/AMME4122). Engineering Project A/B is intended to be more practical in orientation while Thesis A/B demands extensive literature review and critical analysis of outcomes. Thesis is a program for individuals whereas Projects can be done by groups or by an individual. Engineering Project A/B is undertaken across two consecutive semesters of enrolment, in two successive Units of Study of 6 credits points each. Engineering Project A covers first steps of project work, starting with development of project proposal. Engineering Project B covers the second of stage writing up and presenting the project results. The fourth year engineering project aims to provide students with the opportunity to carry out a defined piece of independent design work in a setting and in a manner that fosters the development of engineering design skills. These skills include the capacity to define a engineering design problem, showing how it relates to prior art, identifying appropriate tools and methods, carrying out a design in a systematic way and presenting outcomes in a report that is clear, coherent and logically structured. |
| Assumed Knowledge: | Students will be expected to draw on their project plan, proposed outcomes and background research developed during Project A to allow them to complete the requirements for this unit of study. |
| Department Permission | Department permission is required for enrollment in this session. |
| Timetable: | AMME4122 Timetable | ||||||||||
| Time Commitment: |
|
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 |
| Ability to undertake problem identification, formulation, and solution for complex engineering problems. Ability to identify opportunities for innovation and improvement. Ability to apply creative approaches to identify and develop alternative concepts and procedures. | Design (Level 3) |
| In depth knowledge of a specfic subject area within the discipline. | Engineering/IT Specialisation (Level 3) |
| Students are expected to seek out information efficiently and effectively and to evaluate the relevance of this information and its sources to their project. | Information Seeking (Level 3) |
| Written communication will be exercised through the generation of the Progress Report and Final Report. The Seminar will give students an opportunity to practise their oral communication and presentation skills. | Communication (Level 3) |
| Confidence in own engineering judgments through the process of engineering research. Understanding of the ethical, social and professional implications of the work they are undertaking. Ability to plan and undertake a complex engineering project. |
Professional Conduct (Level 3) |
For explanation of attributes and levels see Engineering & IT Graduate Outcomes Table 2018.
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 3)
1. Ability to formulate and plan a personal project investigating an engineering problem.
2. Originality, ingenuity and initiative in dealing with critical engineering issues.
Engineering/IT Specialisation (Level 3)
3. In-depth knowledge of a specialised area within the discipline.
Maths/Science Methods and Tools (Level 3)
4. Ability to formulate an appropriate method for investigating a specific engineering question.
5. Ability to analyse data, draw appropriate conclusions and present those conclusions in context, with due consideration of methods and assumptions involved.
Communication (Level 3)
6. Ability to document and report project work undertaken in a professional format with appropriate referencing.
7. Ability to deliver a technical presentation that is clear, confident and engaging to an academic audience.
| Assessment Methods: |
|
||||||||||||||||||||||||||||||
| Assessment Description: |
Proposal: Project Proposal (Project A). The proposal should be about two pages in length and written in consultation with supervisor. The proposal includes a time schedule for the various tasks involved in the project work. In particular, if any workshop time is required (for building experimental equipment etc.). The proposal must include a statement that the job has been discussed with the Workshop Supervisor and the proposed time slot (give dates) and resources allocated to the job must be specified. The proposal must be submitted to your project supervisor by the date specified. The proposal does not carry any marks, but failure to submit a satisfactory proposal may result in discontinuation of the course for that semester. Presentation/Seminar: Seminar (Project B). This is an opportunity for students to present their work to other students and to staff. It is a compulsory part of Engineering Project. Evaluation will be based on the quality and coherence of the presentation, quality of subject matter and the handling of questions from the audience. Progress Report: Progress Report (Project A). The report should include an introduction and outline of the project context and relevant background research in a form similar to that which will appear in the final project report and a summary (not exceeding 1000 words) of work carried out thus far. The project supervisor should be contacted when preparing this report for advice regarding content and structure. The progress report must be submitted directly to the project supervisor. The progress report will be marked out of 10 by the supervisor and the marks will contribute 10% of the final Project mark. Late submissions will result in a penalty of 2 marks (out of 10) per working day up to a maximum of the mark awarded. Project: Project Delivery (Project B). A single soft-bound copy of the project report and any associated deliverables should be submitted to the administration office by the due date. Penalty 2% per day (including Sat, Sun) applies for late submission. Content requirements for the final report are set out in the Project Marking Sheet, which provides the basis for project marking. Undergraduate engineering projects are strictly limited to a maximum of 75 pages (approximately 25,000-30,000 words) excluding the pre-amble such as a title page, abstract, declaration of contribution, acknowledgements, table of contents and references. Appendices may also be included in addition to the 75 page limit but are for peripherally relevant information and are generally not assessable. The focus is on quality not quantity. Students should closely consult their supervisor as well as the Marking Sheet regarding the appropriate content, organisation and formatting. Where a team is involved, the report must contain a page clearly stating the contributions of each of the students and any other parties and signed by all students in the group and their supervisor. |
||||||||||||||||||||||||||||||
| Grading: |
|
||||||||||||||||||||||||||||||
| 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. |
| Online Course Content: | http://www.aeromech.usyd.edu.au/cgi-bin/show_unit?=AMME4121& |
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 | Description |
| Week 1 | Project work. |
| Week 2 | Project work. |
| Week 3 | Project work. |
| Week 4 | Project work. |
| Week 5 | Project work. |
| Week 6 | Project work. |
| Week 7 | Project work. |
| Week 8 | Project work. |
| Week 9 | Project work. |
| Week 10 | Project work. Project due for final delivery. |
| Week 11 | Project work. |
| Week 12 | Project work. |
| Assessment Due: Presentation/Seminar | |
| Week 13 | Project work. Submission of Final Report |
| Assessment Due: Project | |
| Previous Semester | Assessment Due: Proposal |
| Assessment Due: Progress Report |
Course Relations
The following is a list of courses which have added this Unit to their structure.
Course Goals
This unit contributes to the achievement of the following course goals:
| Attribute | Practiced | Assessed |
| Project and Team Skills (Level 3) | No | 0% |
| Design (Level 3) | Yes | 29.17% |
| Engineering/IT Specialisation (Level 3) | Yes | 20.84% |
| Maths/Science Methods and Tools (Level 3) | No | 29.17% |
| Communication (Level 3) | Yes | 20.84% |
| Information Seeking (Level 3) | Yes | 0% |
| Professional Conduct (Level 3) | Yes | 0% |
These goals are selected from Engineering & IT Graduate Outcomes Table 2018 which defines overall goals for courses where this unit is primarily offered. See Engineering & IT Graduate Outcomes Table 2018 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.
