engineering report

FIND A SOLUTION AT Academic Writers Bay

MANUKAU INSTITUTE OF TECHNOLOGY
TECHNOLOGY PARK CAMPUSSCHOOL OF PROFESSIONAL ENGINEERING
REPORT
Requirements
The final report is to be an engineering report that details the product and its creation. The reports must be emailed to the supervisor and moderator, and submitted via Canvas to Turnitin. Unless otherwise specified by the supervisor, the reports are individual and not group reports.
A reader should be able to determine the degree of success of the project from the contents of the report, which must include:
Detailed specifications for the product.
Explanation of the final design, together with detailed block diagrams, flow charts, or other supporting information.
References (to IEEE standard).
In Appendices:
A time plan (e.g. Gantt Chart) including actual time on the project to date.
A budget including the actual expenditure.
Where applicable, program files should be submitted to the supervisor. Do not paste the code into the soft copy of your document (except as short code segments, if required for explanatory purposes).
Contents
Students should put into practice the experience gained in their communication skills courses, and should pay attention to the previous feedback received from their supervisor.
Title Page, must include:
Project title
Student name and ID number
Supervisor name
Body of report, will be made up of:
Sections ‘Abstract’ through to ‘References’, as listed in the REPORT MARKING SCHEME – and in the sequence listed there.
The Abstract is to be a brief description of the major outcomes (150 words maximum).
Presentation
The Final Report is limited to a maximum of 30 pages excluding appendices, and must be word-processed in the format specified below. Note that handwritten versions are unacceptable.
A4 size paper. Make sure that the document is illegible when printed on A4 size paper.
All margins to be 25 mm (1 inch) with a gutter margin of 12 mm and mirrored margins.
Suggestion: use Arial font for headings, and Times New Roman for normal body text.
Use 11-point Courier New font for all code extracts / program examples.
Font size should be 11pt or 12 pt, and text must be in 1.5-line spacing.
All text must be written in third person passive.
Unless there are good reasons to do otherwise, use black text on white background, with images in grey scale.
Numberthe pages, sections, figures and tables. Give captions for figures and titles for tables.
N.B. Supervisors may set requirements at variance with the above provided that the students are informed in advance.
Mark procedure
The supervisor and a moderator will mark the report. The mark awarded will be the average of the two marks.
REPORT MARKING SCHEME
Aspect / Max Mark
Mark allocation
Presentation and language / 15
Title page /1 Font and font sizes /1 Spacing and margins /1 Page count /1 Numbering /1 Table of contents /1 Headings and subheadings /1 Figs & tables – format and legibility /1 Figs & tables – numbering and referring to /1 Grammar /3 Spelling / 3
Abstract / 5
Objectives given / 1 Main SW/HW features / 1 Short conclusion / 1 Length / 1 Relevant to the task / 1
Acknowledgements / 2
Not given (0) or OK (1) or excellent (2)
Introduction and Project Objectives / 10
Setting the scene / 2 Problem solving / 2 The main features / 2 Individual objectives and group objectives (if applicable) / 4
Final Design / 26
Details & research towards the design of the final solution / 4 Final specs / 4 Top level flowchart for solution behaviour / 4 Block diagram/circuit diagrams / 4 HW/SW/Technique description /10
Results and Their Description / 15
Test setup / 3 Repeatability of the results / 3 Number of tests / 3 Results’ meaning and significance / 3 Accuracy of results /
Conclusion / 6
Restating the objectives / 1 Restating the chosen design solution / 1 Restating current achievements / 2 Improvements / 2
References / 9
IEEE referencing / 3 IEEE citations in the text / 3 At least 5 credible sources / 3
Appendices / 12
Time plan and Gantt / 6 Graduate attributes / 6
TOTAL: 100
ORAL PRESENTATION AND DEMONSTRATION
Requirements
The final oral presentation will be supported by appropriate visual aids, and will give a demonstration of the product, its performance, and an overview of its design development.
It should include summaries or demonstrations of the key features of the product design, operation and performance, together with suitable graphics (e.g. block diagrams or flow charts, together with graphs illustrating performance features, etc.). In some cases, circuit diagrams may be appropriate, but they should, as a general rule, not be too detailed. Similarly, project involving software design, aspects such as the proposed GUI layout, etc., could be included – but not detailed listings of code.
Guidelines
Students should put into practice the experience gained in their communication skills courses, and should pay attention to the previous feedback received from their supervisor and colleagues.
Students will be expected to pay attention particularly to those aspects listed in the Oral Presentation and Demonstration Marking Scheme.
The recommended visual aid is a PowerPoint presentation using video projection.
N.B. The whiteboard should be used only in answering questions that arise after the presentation.
Oral Format
Students should discuss this with their supervisor since the projects generally cover a wide range of different areas of technology, and presentation styles may need to be tailored to suit specific situations.
The presentation must be timed to fit into a 10-minute timeslot according to a schedule to be published later in the semester. Each presentation will be followed by a short question and answer session. Following the questions will be a short demonstration highlighting three or four key outcomes from the project. This may entail a visit to the laboratory for a separate demonstration, as dictated by the product. Also, in some cases the demonstration can take longer. In those situations the duration for the demo will be discussed with the project supervisor(s).
The number and complexity of the slides will need to be limited if they are to be used effectively in the allocated time.
Mark procedure
Staff attending the presentations will each award a mark for each presenter. Other suitably qualified persons may be invited to attend (and to mark) the presentations. The mark awarded will be the average of all the marks.
ORAL PRESENTATION MARKING SCHEME Light blue – Presentation without Demo
Aspect / Max Mark
Mark allocation
Presentation with Demo / 30 / 50
Time management / 10 Quality of slides / 5 / 10 Clarity of speech / 5 / 10 Eye contact to audience / 5 / 10 Spelling/grammar / 5 / 10
Technical Content/ 40
Introduction / 5 Body / 5 / 10 Conclusion / 5 Pictures/diagrams/facts are IEEE referenced / 5 Adds verbal information over what is written / 10 / 5 Presentation outcome appears correct/sufficient / 10
Questions / 10
Understands the questions / 5 Answers are clear/accurate / 5
Demonstration / 20 / 0
About three or four key things shown
TOTAL: 100
FINAL PRODUCT MARKING SCHEME
Criteria
Max Mark
Performance of product (Meets the overall specifications)
50
Innovation and Creativity
10
Ease of Use and Quality (Workmanship/Good program layout etc.)
10
Verification and Testing
10
Performance of student (Meets standards of commitment, attendance and behaviour expected of a young engineer)
20
TOTAL: 100

READ ALSO...   Wireless phone company
Order from Academic Writers Bay
Best Custom Essay Writing Services

QUALITY: 100% ORIGINAL PAPERNO PLAGIARISM – CUSTOM PAPER