1. ©Dr I M Bradley Doing the project and other things

2. ©Dr I M Bradley The Process Regular meetings with student - once per week ; lasts about one hour Student to keep log of meeting to record major decisions (see Log Book) Student to feed supervisor material for comment

3. ©Dr I M Bradley Student’s Responsibilities 1. To agree on a schedule of weekly meetings with the supervisor and to attend those meetings 2. To keep the project Log Book up to date and to take it to every meeting with the supervisor 3. To submit at the agreed dates all project deliverables 4. To inform the supervisor of any problems arising out of the work 5. To arrange the Terms of Reference review meeting with the supervisor and second marker 6. To arrange the final project viva and demonstration with the supervisor and second marker

4. ©Dr I M Bradley Supervisor’s Responsibilities 1. To give guidance about the nature of the project and the standard expected, about the production of the Terms of Reference, about literature, about techniques and methods, and about any problems of plagiarism 2. To ensure that the proposed project exhibits the appropriate attributes expected of a final year honours project on a computing degree 3. To hold regular weekly tutorials with the student 4. To ensure that the Log Book is kept up to date 5. To be accessible, within reason, at other times for giving advice to the student

5. ©Dr I M Bradley Continued 6. To request evidence of progress and to ensure that the student is aware of any inadequacy of progress or of standards of work below those expected 7. To provide constructive criticism on any work presented 8. To encourage the student to produce early draft chapters, to comment on them critically and return them promptly;( If the student does not do so it is the student’s responsibility) 9.To review with the second marker the student’s Terms of Reference

6. ©Dr I M Bradley The Log Book A record of student's work Must be kept up to date Contains ToR review form Contains Form for recording agreed changes to objectives Must be handed in with report at end of project Used by supervisor for justification of Performance Mark

7. ©Dr I M Bradley The Report Purpose present Analysis of problem describe work carried out to solve problem, Synthesis Evaluation of the work detail later in series detail later in series

8. ©Dr I M Bradley The Report Counts 60% Size about 50 pages Appendices extra - keep small Two copies submitted Try and produce as the work done Supervisors will give feedback on drafts Quality not Quantity

9. ©Dr I M Bradley Marking Scheme Report - 60% Components Abstract & Introduction - 5% Analysis - 25% Synthesis - 25% Evaluation - 25% Conclusions & Recommendations - 10% Presentation - 10%

10. ©Dr I M Bradley The Product Must be a product Not a survey! Most projects involve some software development Components requirements, design, implementation, testing Counts 30% Work done is described in Report so really 30% plus

11. ©Dr I M Bradley Marking Scheme The Product - 30% Fitness for purpose: Meeting of Requirements as identified during project Build quality : Design Implementation Testing Other features e.g. HCI

12. ©Dr I M Bradley Marking Scheme The Presentation / Viva - 10% Total ~40 minutes presentation ~ 20 minutes viva ~ 20 minutes to ensure student's understanding

13. ©Dr I M Bradley Activity Consider the project you have proposed. Identify the product. How would you expect to assess the items that constitute the product? What criteria would you use for fitness for purpose? How do you judge the build quality ? Consider the project you have proposed. Identify the product. How would you expect to assess the items that constitute the product? What criteria would you use for fitness for purpose? How do you judge the build quality ?