MECH8020 Module Project Report Guidelines

As part of the MECH8020 module assessment, it is required that a comprehensive professional engineering  project report is submitted, which is produced in accordance with the following guidelines, except where  specific permission to deviate from these guidelines is given by the academic supervisor. The submitted  report will be a project overview and progress report which builds on the previously submitted executive summary and project plan. It will include the clearly defined aim of the project, the objectives of each project element, the methodologies employed to achieve each objective, e.g. experimental, design, analytical and/or numerical, and a detailed description of the work completed to date. It is expected that this description will include preliminary engineering analysis, although validation of this analysis may not yet be complete. This report will be supported by a significant Literature Review which will underpins all project work described.

The report is assessed in line with the following learning outcomes:

1. Undertake a review of relevant and appropriate literature to become familiar with current knowledge in the project area.

2. Outline a number of viable methodologies to address the identified project area.

3. Develop and present a project plan to implement the proposed methodology.

4. Justify the rationale for the chosen methodology on the basis of preliminary engineering analysis, design calculations and/or experimental design.

5. Exercise professional judgement in evaluating potential courses of action against appropriate design, safety, commercial and ethical criteria.

6. Demonstrate the appropriate written communication skills required of the professional practitioner.

The overall report structure should be in line with the following:

Title Page, Abstract, Table of Contents/Figures, Nomenclature and Abbreviations

Introduction
Literature Review
Methodology
Project Planning and Management
Discussion
Conclusions/Recommendations
References
Appendices (If required)

The following provides guidance for the content and format of each report element listed above.
Note: Since these guidelines must suit a very varied range of project types, significant judgement is required to ensure the report content is best suited to each project. Consult with your academic supervisor regarding your specific content detail.

A brief (8 to 12 lines) and accessible overview of the context of the work, the work carried out and  the main findings/conclusions. On a page of its own, page i (one in lowercase Roman numerals).

Section and sub-section headings with page number on which they first appear.
Note: Page number for the page on which the Table of Content appears should be. There is no need to list "Table of Content" in the table of content.

Nomenclature and Abbreviations: All symbols and abbreviations used in the report to be detailed including symbol/abbreviation (in the same font and style as they appear within the report main body), meaning, units if relevant. A 3-column table can be useful for this. A list of definitions/glossary of terms can also be included in this section if required. Page number continues in lowercase Roman numerals.

Report Structure

Introduce a context to the project work by explaining relevant background to the subject/topic, giving examples of relevant real-world engineering applications/technology. The project aim should be introduced by first presenting a problem statement or research question, followed by a concise project aim. 
The problem statement or research question should be presented in the context of the current state-of-the art and clearly justified including in the context of availability of resources. The description of thisstatement/question, along with the aim should describe the specific engineering challenge, context, scope, 
objectives and expected deliverables, i.e. deliverables at the end of semester 2, for the current project work. The project work carried out to-date should be introduced by providing an overview description of all work completed, including mention of significant challenges encountered and achievements. The above will provide a more detailed introduction of the project work compared to that of the abstract, and should finish with a brief narrative introduction to the contents of the report. It is expected that this report section will include some referenced material

The function of this report section is to present the information that the author has identified as being relevant and has studied in connection with the project work. This may include for example, some background history of relevant technology, applications, standards/regulations, theory and current developments related to the project subject/topic. It is very important that clear links are made between the information presented in the literature review and the current project work. This section has far more depth than the introduction section and should show that the author is knowledgeable of the subject matter based on the literature reviewed and detail presented. All areas of the project should be represented, including for example, background to the methodologies selected, measurement, theory, analysis and validation techniques, and relevant hardware/software.

Note: It is not appropriate or acceptable to copy the work of others and make slight adjustments in the wording, nor should this section be a list of quotes. Quotes are very infrequently useful/used in professional engineering documents. What is required is that author studies a topic from a number of relevant sources and then from this formulate their own perspective on the topic, which then informs their writing. This writing should make up the vast majority, if not all of the report, other than descriptions of the author's own work, e.g. experimental, analysis, design, numerical. The sources studied are then referenced to indicate the basis on which the information presented is founded, in either the Harvard or IEEE referencing style. Therefore, the literature review should be a presentation of the author's understanding based on their review of the relevant, referenced literature.

Report Structure Detail

It is expected that this report section will include considerable referenced material and this material must be in the public domain (e.g. class notes should not be referenced), should be currently relevant with up to date information and MUST be from reliable sources, e.g. relevant peer-reviewed journal papers, product information from original equipment manufacturers, high quality text books and other reputable sources.The number of references can greatly vary from project to project. As a guideline only it would be normal for 
between 30 and 40 unique references to be used in generating this section. (Generally 12 - 18 pages.)

With the project overview of the introduction section and the detail of the literature review section as a foundation to build upon, the function of this methodology section is to detail how the engineering methodologies selected to achieve the project objectives, are being and will be implemented in order for the project aim to be achieved, including validation methods also. This may include, but is not limited to, the 
following:

Experimental: The specific experimental techniques are described to a level of detail for such work to be repeated on the basis of the detail provided. Design of experiments are described. Experimental procedures and equipment are detailed.

Analysis: Analysis of experimental readings and/or software output is described. Calculations carried out, and the analytical/numerical basis of such calculation are described.

Design: Design techniques and methodologies used are detailed, including the specific rationale on which these are selected and how they are used for the current work.

Software development: The programming approach taken is described and the specific rationale on which approaches are selected, e.g. choice of programming language, software applications used, hardware selected, if applicable, e.g. use of Arduino technology and/or electronics breadboard.It is expected that this report section will include some referenced material, e.g. equipment/software 
specifications. (Generally 10 - 15 pages.)

The function of this section is to detail all project planning and management for the entire project period, i.e. from the start of semester 1 to the project report submission in semester 2. This detail should build on the previously submitted executive summary and project plan, and similarly include a current Gantt chart detailing the project elements, tasks and milestones, complemented by description of project management, i.e. changes made, rationale for planning decisions, resource matters, along with risk-based contingency planning allowing for changes in project direction and/or methodologies to be employed, e.g. if access to currently available resources is reduced or removed. It should be clear from this report section how the progress of each element supports the achievement of objectives, influences other elements and leads to project aim achievement and deliverables, including in the event of changes to resource availability. This project planning and management section should detail time input and timing for the entire project period, i.e. from the start of semester 1 to the project report submission in semester 2, and should clearly link with the Methodology section information.

The function of this section is to present the information resulting from the work completed by providing:
• A critical analysis of the most salient literature review material.
• A synopsis of the outcomes from the employed methodologies.
• Consideration regarding alignment of the project with relevant ethical codes (e.g. Engineers Ireland Code of Ethics and UNESCO Sustainability Goals).

The function of this section is to present the information resulting from the work completed by providing a critical analysis of the most salient literature review material, a synopsis of the outcomes from the employed methodologies and discussion on the effectiveness of the project planning and management decisions made. 

The information presented here will clearly outline the progress so far achieved, and how this will shape the direction of the work planned for the remainder of the project. This should build on the resources and time focussed planning and management section detail.This report section will generally include some referenced material, mainly in connection with mention of literature which has been reviewed.

Conclusion:

This section summarises the report detail by including the most important information presented in the preceding sections. This information will align well with the project objectives, with a clear focus of the project aim and deliverables. Specific recommendations for the future project work will be presented here. This report section will generally not include referenced material.