informe mensual de proyecto

8/10/2019 Informe Mensual de proyecto

1/4

CBeST Final Year Project Final Project Report Layout

1. Introduction

The final version of your project report is the main way by which your work will be assessed.

The average student is expected to have put 240 hours of work into completing the project. It is thereforeimperative that the uality and structure of the report is a true reflection of the effort that you have put in! andclearly shows what you have achieved.

The final written report is expected to be between "!000 and #0!000 words! excluding appendices.

2. Documentation Standards

The following list defines the format of the written report that is expected of a final year honours degree student.

a. The report must be written in $% &nglish! you should spell check your work before submitting it.

b. Two hardbound copies of the report must be submitted in printed form on '4 paper.

(or $)& students! all binding must be carried out by *esign and +rint ,ervices as they have been briefedabout the binding reuirements for the project. The cost of binding is around -.0 per volume.

/ou are reuired to hand in two copies and may wish to print an additional copy for your own records asthere is no guarantee that projects will be returned.

c. The cover of the report must state the module title! student name! student I*! project title and date ofsubmission using the information laid out on the +1 +roject ,ticker3

e. The font used should be 'rial or elvetica! the si5e of the font should be #0 point.

d. The main body of the report must be have #.x or 2x line spacing. 'ppendices and code listings may besingle line spaced.

e. There must be a clear #.23 binding margin6 all other margins must not be less than #.03.

f. &ach page must be clearly marked with a uniue page number! this should be placed within the bottommargin of the page.

g. &ach chapter should be numbered! each appendix given a uniue identifier. It is recommended thatappendices be given letters 7'! 8! ) etc9.

h. &ach section within a chapter should be given a section number! ie #.#! #.2 etc. It is recommended that youdo not go below three levels of section numbering 7ie #.#.#9. /ou should use the section numbers to crossreference parts of your report 7ie see section 1.23! or see 'ppendix '39! rather than use page numbers.

i. &ach figure and table must be give a uniue reference number and meaningful title.

j. ' references to work which is not your own 7this includes diagrams and source code9 must be fully citedusing one of the standard referencing systems. (or more information see the &ssentials :uide3 on;eferencing.

2.1 lectronic !ersion o" Report

&ach copy of the printed version of the project report must have an electronic copy of the project on a )*securely attached inside the inside back cover.

The )* must contain an electronic copy of your project report in >, ?ord or ;T( format which will be used forautomated plagiarism detection. It must also contain copies of any source code you have produced for theproject.

The electronic version must be consolidated into a single file 7i.e. each chapter must not be in a separate file9.

'ny embedded images or diagrams should be stripped out so that the file can be easily be submitted by yourproject supervisor to the faculty@s plagiarism detection service.

(ailure to submit electronic copies in this format will mean that your project will fail.

#. Citation o" Sources

'll work that is described in the final report that is not your own must be fully cited using one of the standardreferencing systems. This includesA case studies6 source code6 tables and diagrams6 uestionnaires. /ou shoulddo this even where you have made changes to the original material B the $niversity considers paraphrasing asa form of plagiarism.

If your work contains material that is not fully cited then the $niversity may take action under the )heating and+lagiarism ;egulations3! or it may discount any work that is defined as being unduly derivative3.

Continues on next page

UCE, Department of Computing Page 1 of 4Version 1.3, April 200 23!"20"!.#o$


2/4


$. Structure o" Report

The front cover of every volume must have the following +1 +roject ,ticker3 attached to it.

/ou will need to alter the sections ,tudent Came! ,tudent Cumber! +roject Title! +roject ;oute and ,upervisorCame to contain your own details.

If each copy of your project comprises only # volume you can remove the @Dolume x of y@ section. =therwise you

should change this to denote the project volumes as appropriate.$)& students should give *esign and +rint ,ervices printed versions of these! they will copy these onto stickersfor the front of your project.

The layout of the report should beAanagement.

,taff may contact the client in order to confirm the details of hisEher association with your project.

4. !ia !oce amination

This is a 10 min! formally structured! interview in which the first and second project markers ask uestions toprobe the studentFs knowledge and seek to confirm that the marks allocated on the basis of the project report is atrue representation of the studentFs abilities on the key skill areas.

The uestions asked at the viva will be mainly led by issues raised through a reading of the project report! butcan refer to other activities < such as the demonstration of software.

The viva will normally be scheduled to take place within 1 weeks of the deadline for the submission of the finalversion of the project report.

'ttendance at the viva is mandatory. (ailure to attend the viva at the appointed time may lead to 5ero marksbeing recorded for your project module at the next examination board.

In the case where a student is being re


4/4


5. 6ey Dates

The specific dates will be published on ,)'C by the +roject )oordinator.

The dates below assume that the student is undertaking the project module over 2 semesters.

+roject ,election (orm submitted7students select / choices9

?eek #

+roject +roposal (orm )ompleted ?eek 1Interim report ?eek #2

*raft final report ?eek " of the second semester

*emonstration of software ?eek "

informe mensual de proyecto

Documents