This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| final_report [2013/09/18 14:03] – scmfcl | final_report [2015/09/24 16:43] (current) – removed scmfcl | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Final Report ====== | ||
| - | If you are doing the CM0343 or CM3304 40-credit project module you will need to submit and final report worth 70% of the total project mark, which should cover the overall project findings and achievements. The report should not repeat the contents of the interim report, but may refer to it and expand on it. You will also have to submit a complete set of the deliverables developed for the project, as specified in your initial plan (this includes any source code and soft system models). This involves the development of some tangible piece of software, hardware, system design or theoretical result. It need not necessarily be a usable finished product. Instead it could be, for example, an extension to an existing system or a prototype built as part of a feasibility study. Deliverables do not necessarily have to be programs, but could be in non-executable form, for example, an SSM conceptual model. The final report forms part II and the deliverables form part III of the project. Both parts must be submitted towards the end of the second semester. See your project details in PATS for the submission deadline. | ||
| - | |||
| - | Please see your initial plan in which you should have clearly outlined the deliverables for the final report. Your supervisor and/or moderator may have left additional comments on your plan on PATS to tell you whether these deliverables are suitable and what they expect for the interim report. Check the comments on PATS for your report. Also discuss carefully with your supervisor what you should be including in the final report. | ||
| - | |||
| - | For information about how to submit your final report via PATS please see the [[Submission Guide]]. You can only submit a final report if your initial plan has been submitted and approved (if there is any problem with this contact the project coordinator). Note that in order to get an extension to the submission deadline the general coursework submission extension guidelines apply. So please follow this in case you have a valid reason to ask for an extension, and make sure to keep your supervisor, moderator and project coordinator informed. | ||
| - | |||
| - | ===== Structure and Contents ===== | ||
| - | |||
| - | The final report should be at most 15,000 words long. General guidance on project report | ||
| - | structures is available in [[Arranging Material and Structuring the Project Report]]. | ||
| - | |||
| - | The general structure for your final report should be: | ||
| - | | |Title Page |Support | ||
| - | | |Abstract | ||
| - | | |Acknowledgements | ||
| - | | |Table of Contents | ||
| - | | |Table of Figures | ||
| - | |1.|Introduction | ||
| - | |2.|Design | ||
| - | |3.|Implementation | ||
| - | |3.|Results and Evaluation|::: | ||
| - | |4.|Future Work | ||
| - | |5.|Conclusions | ||
| - | |6.|Reflection on Learning|::: | ||
| - | | |Glossary | ||
| - | | |Table of Abbreviations|::: | ||
| - | | |Appendices | ||
| - | | |References | ||
| - | The Introduction should relate the final report to the interim report and discuss any changes, extensions or new insights since the interim report to the material. In some cases this may also go into a separate section if the material is quite extensive. | ||
| - | |||
| - | If you are implementing a piece of software the " | ||
| - | |||
| - | Then present the results of your work and evaluate these results with suitable evidence, discussing the advantages and weaknesses of your approach. The Conclusions section should conclude your project overall and your report should end with a reflection on learning. | ||
| - | |||
| - | ===== Final Report Assessment ===== | ||
| - | |||
| - | After the submission deadline your supervisor and moderator assess the final report independently of each other. In addition a [[project viva]] will be held to demonstrate and discuss your project after the complete project has been submitted. The format of the viva varies depending on the project, but generally consists of a demonstration or presentation of the deliverables followed by a discussion of various questions from the supervisor and moderator relating to the project. | ||
| - | |||
| - | A mark out of 75 is given on the Final Report, representing 75% of the total mark. The mark awarded for the Interim Report will be carried over from the Autumn Semester, and will be added to the marks given for the Final Report to give a total mark from each assessor. The final mark for the project will be the average between the supervisor' | ||
| - | |||
| - | The criteria for assessing the final report are listed below. Please read these carefully as it will help you to see what your assessors will be looking for in your report. Also take into account what you promised to produce for the final report in your initial plan, and your supervisor' | ||
| - | |||
| - | You can resubmit your final report at any time until the deadline and your supervisor and moderator will not be able to mark this or make any comments online before the deadline. Please discuss your final report with your supervisor at your regular meetings. You can upload parts of the report onto PATS so that your supervisor can look at these (or give the report in any other way to your supervisor). Just upload the files in the file upload section and your supervisor and moderator can see these there (you can, but do not have to submit them until you have the final version). | ||
| - | |||
| - | ===== Assessment Criteria ===== | ||
| - | |||
| - | Your supervisor and moderator will assess your final report according to the following criteria: | ||
| - | |||
| - | * Solution to the problem | ||
| - | * Approach and design | ||
| - | * Implementation | ||
| - | * Use of and justification for appropriate tools/ | ||
| - | * Evaluation | ||
| - | * Testing and validation | ||
| - | * Critical appraisal of results | ||
| - | * Communication and project management skills | ||
| - | * Written (final report) and oral (viva) communication skills | ||
| - | * Project planning, control and reflection | ||
| - | * Interaction and work with supervisor | ||
| - | * Achievement of agreed overall deliverables given in initial plan for the final report | ||
| - | * The amount of work reported in the final report in combination with all deliverables should be about 75% of the total work required for the module (in total 40 credits/320 hours of work for CM0343 and CM3304) | ||
| - | * Extensions since the interim report on | ||
| - | * Understanding of the problem | ||
| - | * Approach towards a solution | ||
| - | * Interim report deliverables | ||
| - | on the following scale: | ||
| - | * Third class (>= 40%): The student has clearly defined the problem and made progress towards a solution... | ||
| - | * 2.2 (>= 50%): ...and demonstrated a disciplined approach and adequate solution... | ||
| - | * 2.1 (>= 60%): ...and an appreciation of best practice with a full justification for the solution... | ||
| - | * First class (>=70%): ...and evidence of originality and professionalism and/or scholarship. | ||