Report Submission

The Final Report content and structure (which should be followed precisely) are detailed in the Project Guide. This page describes how you submit your report. Make sure you read it well before your deadline.

Report Submission

All students must submit two copies of their project report to the Undergraduate Office by 16:00 on the date specified. Late submission will be penalised as for all other coursework and result in mark capped at 40%.or, if more than 7 days late, 0%, unless a mitigating circumstances form is submitted and accepted.  Students are strongly advised against leaving the printing and photocopying of reports until the last minute; the demand for departmental laser printers and photocopiers will be exceptionally heavy on the day of submission.

All students must also submit an electronic PDF of their project Final Report by 18:00 on the same day as the paper report. The PDF must be submitted twice, to TWO DIFFERENT WEB SITES as below. Note that submission of electronic copy is a requirement, but does not prevent the mark penalty for paper submission as above. PDFs must be printed with size no more than 20MB. Use lower resolution settings in your PDF printer as necessary to acheive this.

https://intranet.ee.ic.ac.uk/scripts2/UploadCW.aspx Submit PDF via EEE cousework entry page, Final Report item.

 https://bb.imperial.ac.uk/ Submit PDF to the EE3-FYPRJ Blackboard course via the Final Report link under "curse content"..

Project reports must be typed or printed and should be bound in  translucent & soft covers with paper backs available from the EEE level 1 stores. The table below specifies WHICH COLOUR YOU MUST USE.

A single cover page, in a standard format, should be used inside the front cover. The enclosed word file shows the format. There is also a latex equivalent. You should change project title, student name, supervisor and second marker, year & stream (EEE: 4T,4EM,3E, EIE: 3I, 4I) course (EEE or EIE) as necessary, and print this. If you prepend this to your report electronically, please be careful that page margins stay as in the enclosed file.

The precise typographical format of your final report - page margins, font size, etc, is not precisely specified, but should be neat and easy to read. Font size in the range 11-12 and line spacing 1-1.5 is normally acceptable.

Binding. Reports should normally be comb bound, using equipment available (see level 1 stores for more information and cost).

Students may wish to enclose floppy disks or CD-ROMs with their Report. The contents of these may, but will not necessarily, be read by your markers.

Demonstrations

Supervisors and 2nd markers of both software and hardware projects will normally wish to see a demonstration of your project. For a very few projects, where demonstrations can sensibly be integrated with the presentation this will happen during the end of term presentation. Otherwise you should invite your markers, either together or separately, to a demonstration. Please remember that staff are very busy during the last week of Term, so organise this in advance. There are no formal requirements for a demonstration, but you should check carefully with both your markers what they require.

If your project is software and has a deliverable that can easily be run as a standalone program on a PC you may want to submit this with your Final Reports. Note however that your markers will not necessarily have appropriate computer systems on which to run your software.

Plagiarism

Wherever your report contains someone else’s arguments and ideas then that person must be acknowledged in the text and a source reference provided at the end of the report. Passages copied directly must be placed in quotations: it is not acceptable to make a few wording changes and submit someone else’s work as your own. Intellectual borrowing is an essential part of scholarship and is perfectly acceptable so long as the debt is clearly acknowledged. Plagiarism will be detected and normally result in project (and therefore degree) failure. All Project Reports will be submitted for automatic plagiarism detection.

Tom Clarke, June 2013