Marking Criteria

The final year project is usually based on the design and implementation of a substantial software system. The topics vary widely in scope and difficulty, and the project assessment has to take this into account. Assessors must also consider issues including

The tables below gives a broad indication of the factors leading to a given mark, but it should be recognized that the mark is obtained by combining the assessment of a number of these factors. Comments refer to marks around the middle of each range.

Also, please be aware that ALL undergraduate Informatics projects are now weighted 45 credits.

Interim Reports

  • 85% -- 100%: An outstanding report. The student will have performed a detailed analysis of the problem area leading to initial high-level designs for the system and a detailed feasible project plan. There should be clear evidence of relevant background research. The report should be superbly organized and presented and lucidly written.
  • 70% -- 84%: Students will show a thorough understanding and appreciation of the project material. The student will have performed a detailed analysis of the problem area and a feasible project plan. There should be some evidence of relevant background research. The report should display excellent organisational and presentational skills.
  • 60% -- 69%: Students will show a clear understanding of the technical and professional issues involved and have analysed the problem area. Some issues may have been overlooked but there should be a project plan which suggests the likely success of the project. The report should be organised and written to a reasonable standard.
  • 50% -- 59%: The report should demonstrate that the student has some familiarity with the project area. The presentation and organization of the report should be reasonably clear. There may be some signs of weakness, but overall the grasp of the topic should be sound.
  • 40% -- 49%: The report will indicate a basic understanding of the methods to be used and how to organize and present the work in the report, but will not have gone much beyond this. There may well be signs of confusion about more complex material.
  • 30% -- 39%: There should be some work towards understanding the problem area, but significant issues are likely to be neglected. There may be significant errors or misconceptions in the project.
  • 15% -- 29%: The project may contain some correct and relevant material, but most issues are neglected or are covered incorrectly. There should be some signs of appreciation of the project requirements.
  • 0% -- 14%: Very little or nothing that is correct and relevant and there is no real appreciation of the project requirements.

Final Reports

  • 85% -- 100%: An outstanding project. The system should be essentially faultless, well-structured and carefully tested. There should be excellent achievement of the objectives and evidence of original thought. The report should be superbly organized and presented and lucidly written.
  • 70% -- 84%: Students will show a thorough understanding and appreciation of the project material, producing work without significant error or omission. Project objectives achieved well. The report should display excellent organisational and presentational skills.
  • 60% -- 69%: Students will show a clear understanding of the technical and professional issues involved with good work towards the project objectives. The system and/or the report may have minor omissions but the report should be organised and written well.
  • 50% -- 59%: The project should be competent in most respects. The project objectives should at least be partially achieved. The presentation and organization of the report should be reasonably clear. There may be some signs of weakness, but overall the grasp of the topic should be sound.
  • 40% -- 49%: The project will indicate a basic understanding of the methods to be used and how to organize and present the work in the report, but will not have gone beyond this, and there may well be signs of confusion about more complex material. There should be fair work towards the project objectives.
  • 30% -- 39%: There should be some work towards the project objectives, but significant issues are likely to be neglected. There may be significant errors or misconceptions in the project.
  • 15% -- 29%: The project may contain some correct and relevant material, but most issues are neglected or are covered incorrectly. There should be some signs of appreciation of the project requirements.
  • 0% -- 14%: Very little or nothing that is correct and relevant and there is no real appreciation of the project requirements.