Independent Engineering Project: Developing Technical Competency

Negotiate and execute a realistic plan to deliver to agreed project outcomes

The Independent Engineering Project is a major element of accredited engineering or technical degree. It provides the necessary evidence that you are technically competent and capable of entering the world of work as a professional engineer or technologist.

The aim is to develop your ability to work independently, in a chosen topic, using relevant technical research and design concepts, and analytical, test, measurement and evaluation techniques, in order to produce a finished artefact or product.

You will be expected not merely to collect, analyse and apply information, but also to exhibit other skills such as the ability to plan, manage and produce a significant technical piece of work.      

On successful completion of the module, you will be able to:

1.Negotiate and execute a realistic plan to deliver to agreed project outcomes, including structured approaches to planning, investigation and research, with due regard to the constraints of time, budget and available resources.

2.Maintain an ongoing record, and write a substantial final analytical technical report containing an extensive critical evaluation of the methods adopted and the final outcome of the project.  

3.Present and discuss in a viva voce setting your technical project in depth, clearly communicating the critical issues and key features of the project and be prepared to answer detailed questions.

Definition of a project, project life cycle phases, project planning tools, risk analysis, resource management, managing project delivery.

Design Methods

Applying structured design methods: clarification of need, conceptual design, embodiment design, detail design. Design for civil engineering, manufacture and sustainability.

You will be expected to identify a technical project related to your final year studies. The project could originate from a list provided by the Module Leader or from a relevant personal interest of yours. All projects originating from you must be approved by the Module Leader prior to commencement and be sufficiently technically demanding to justify inclusion in the final stages of an accredited degree.  

The project supervisor, allocated after submission of the proposal, is primarily responsible for monitoring your conduct and involvement as well as providing some guidance when deemed necessary.  A second supervisor is chosen to complement the expertise of the project supervisor and to provide internal moderation. You are expected to meet your project supervisors on a regular basis, ideally at least once a fortnight, throughout the year for guidance in strategy, implementation and report writing.

The project proposal, (Learning outcome 1) is based on a preliminary survey of the problem area. It includes an outline of the scope and objectives of the study such as expected project outcomes, a plan of work, an assessment of the resources required for completion and an evaluation of safety and ethical implications (the former expressed as a formal risk assessment).   

Maintain an ongoing record, and write a substantial final analytical technical report

The project supervisor may ask for revisions to the project proposal and must finally agree to it, within three weeks of it being submitted.  The proposal will form an important part of the subsequent management of the project and will contribute to establishing the criteria for the assessment of the project.  

A project logbook should be maintained on a continuous basis by you. This forms the agenda for the regular meetings between the project supervisor and you, and may be an e-log or a more traditional record.  During the course of the project, you will meet your supervisor regularly to discuss progress, as evidenced verbally and by the logbook. This allows problems to be dealt with at a retrievable point in the course of the project. It is the responsibility of you to ensure that these meetings occur. Practical work must be conducted in University premises, unless explicitly agreed otherwise by the project supervisor. Any practical work, whether on University or other premises, must not begin before the risk assessment and ethical clearance has been agreed.

The final technical report and project logbook evidence will depend on the nature of the particular project.

Projects may be classified as one of two types:

• An “investigative study” will include experiments or tests on equipment or systems already available. The main item of assessment is the analytical report of the investigation. The prescribed word count is not more than 7000 words (not including appendices or programme listings).

• A “practical project” where the main assessment weighting is for a hardware, software (or hardware/software) artefact, and a technical evaluative report where the conclusion/recommendation should be substantial and analytical.  The report word count is less than that for the ‘investigative study’ and should be no more than 6000 words (not including appendices or program listings).  

NOTE: Purely discursive projects ARE NOT allowed as this module forms part of an IET accredited programme and as such any project undertaken must contain significant practical or technical investigative work as the basis of the written report.

All practical work must be completed by the agreed deadline. The project report and project logbook will be submitted on the specified deadline. You are required to submit two bound, word-processed copies of a report of your work, and a version in electronic format.

Before the report has been submitted, you will be required to attend a viva voce session to present and discuss the project in depth, and clearly communicate its critical issues and key features.