The Final Year Project Process

3,606 views

Published on

Published in: Education, Business, Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
3,606
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
62
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

The Final Year Project Process

  1. 1. DT228 Final Year Projects
  2. 2. Timeline September April Christmas (Fixed) Easter (Variable)
  3. 3. Timeline September April Project Proposal October
  4. 4. Timeline September April Project Proposal October December Interim Report and Demo
  5. 5. Timeline September April Project Proposal October Dissertation submission December Interim Report and Demo
  6. 6. Timeline September April Project Proposal October Dissertation submission Final Demo December Interim Report and Demo
  7. 7. Timeline September April Christmas (Fixed) Easter (Variable)
  8. 8. Timeline September April Research and background reading
  9. 9. Timeline September April Research and background reading Software Design
  10. 10. Timeline September April Research and background reading Software Design Software Development
  11. 11. Timeline September April Research and background reading Software Design Software Development Testing and Evaluation
  12. 12. Timeline September April Write-up Research and background reading Software Design Software Development Testing and Evaluation
  13. 13. Timeline September April Project Proposal October Dissertation submission Final Demo December Interim Report and Demo Research and background reading Software Design Software Development Testing and Evaluation Write-up
  14. 14. Project Proposal <ul><li>Students must put together proposal based on a project idea. </li></ul><ul><li>Sources of project ideas include; </li></ul><ul><ul><li>Staff suggestions (collected on a web page) </li></ul></ul><ul><ul><li>Staff Research Areas </li></ul></ul><ul><ul><li>Work placement suggestions (tricky) </li></ul></ul><ul><ul><li>Their own idea (most useful) </li></ul></ul>
  15. 15. Staff Project Ideas
  16. 16. Staff Project Ideas <ul><li>Benefits </li></ul><ul><ul><li>In well understood research area </li></ul></ul><ul><ul><li>Easy to find supervisor </li></ul></ul><ul><ul><li>Can build on existing work </li></ul></ul><ul><li>Drawbacks </li></ul><ul><ul><li>Supervisor may have high standards </li></ul></ul><ul><ul><li>Supervisor may be unhappy that the students vision diverges from theirs </li></ul></ul>
  17. 17. Staff Project Research Areas
  18. 18. Staff Research Areas <ul><li>Benefits </li></ul><ul><ul><li>In well understood research area </li></ul></ul><ul><ul><li>Easy to find supervisor </li></ul></ul><ul><ul><li>Can build on existing work </li></ul></ul><ul><li>Drawbacks </li></ul><ul><ul><li>Supervisor may have high standards </li></ul></ul><ul><ul><li>Supervisor may be unhappy that the students vision diverges from theirs </li></ul></ul>
  19. 19. Work Placement Suggestions <ul><li>Benefits </li></ul><ul><ul><li>Industry relevant </li></ul></ul><ul><ul><li>Up-to-date technologies and techniques </li></ul></ul><ul><ul><li>Creates communications with industry </li></ul></ul><ul><li>Drawbacks </li></ul><ul><ul><li>Might be less emphasis on dissertation </li></ul></ul><ul><ul><li>Good industry application might not be academically suitable </li></ul></ul>
  20. 20. Student’s own idea <ul><li>Benefits </li></ul><ul><ul><li>Self-motivated </li></ul></ul><ul><ul><li>Doing things they are good at </li></ul></ul><ul><ul><li>fun </li></ul></ul><ul><li>Drawbacks </li></ul><ul><ul><li>Might be having too much fun </li></ul></ul><ul><ul><li>Hard to find supervisor </li></ul></ul><ul><ul><li>Might not be degree standard </li></ul></ul>
  21. 21. Project Proposal
  22. 22. Project Proposal <ul><li>First week or two in October </li></ul><ul><li>Written often with help of lecturer (project co-ordinator will suggest someone) </li></ul><ul><li>Drafted and re-drafted </li></ul><ul><li>Final draft signed by student and checked by lecturer other than co-ordinator </li></ul><ul><li>Submitted to Project co-ordinator and finally accepted or asked for re-drafting </li></ul>
  23. 23. Allocation of supervisors <ul><li>Following complete collection of proposals, co-ordinator allocates students to supervisors, this can be complicated </li></ul><ul><ul><li>Some lecturers have more free time </li></ul></ul><ul><ul><li>Some are interested in specific projects </li></ul></ul><ul><ul><li>Some will take students even if the don’t have hours to do it </li></ul></ul>
  24. 24. Allocation of supervisors
  25. 25. During Supervision <ul><li>Supervisors and students arrange to meet up once a week and discuss the project. </li></ul><ul><li>Supervisors have problems with students </li></ul><ul><ul><li>They come to the co-ordinator </li></ul></ul><ul><li>Students have problems with supervisors </li></ul><ul><ul><li>They come to the co-ordinator </li></ul></ul>
  26. 26. Supervisor Problems <ul><li>Students not attending meetings </li></ul><ul><ul><li>Co-ordinator e-mails them </li></ul></ul><ul><li>Students not doing agreed tasks </li></ul><ul><ul><li>Co-ordinator sit in on next meeting </li></ul></ul>
  27. 27. Student Problems <ul><li>Students with medical circumstances </li></ul><ul><li>Students with personal circumstances </li></ul><ul><li>Students with issues of understanding </li></ul><ul><ul><li>Ask them to study more </li></ul></ul><ul><ul><li>Find someone else in the School to speak to </li></ul></ul><ul><ul><li>Find someone else in the DIT to speak to </li></ul></ul>
  28. 28. Interim Report <ul><li>Last week of semester 1 </li></ul><ul><li>The student submits 2 copies, one for second reader, one for supervisor </li></ul><ul><li>30-40 pages long </li></ul><ul><li>First two months of work </li></ul><ul><ul><li>Background reading </li></ul></ul><ul><ul><li>High level design </li></ul></ul><ul><ul><li>Some low level design </li></ul></ul><ul><ul><ul><li>Architecture (client/server, 3-tier, n-tier) </li></ul></ul></ul><ul><ul><ul><li>UML Diagrams </li></ul></ul></ul><ul><ul><ul><ul><li>Use Cases </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Class Diagrams </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Interaction Diagrams </li></ul></ul></ul></ul><ul><ul><ul><li>ERDs </li></ul></ul></ul>
  29. 29. Interim Demo <ul><li>Last week of semester 1 </li></ul><ul><li>Supervisor, second reader and coordinator </li></ul><ul><li>Student does 10 minute PPT presentation </li></ul><ul><ul><li>Practice for final demo </li></ul></ul><ul><ul><li>Gets students reflecting on project </li></ul></ul><ul><ul><li>Creates a deadline for students </li></ul></ul><ul><ul><li>If student in trouble </li></ul></ul><ul><ul><ul><li>Helpful suggestions from 2 nd reader and co-ordinator </li></ul></ul></ul><ul><ul><ul><li>Warn them to hurry up </li></ul></ul></ul><ul><ul><ul><li>Co-ordinator can follow-up and sit in on meetings </li></ul></ul></ul>
  30. 30. <ul><li>Very often in February students get the blues, they get a bit depressed, a bit afraid, and want to defer or withdraw </li></ul><ul><ul><li>They just need to hear “ you can do it ” </li></ul></ul>February blues September April
  31. 31. Deciding on the submission deadline <ul><li>The Easter holidays vary from year to year, if Easter is early, the deadline happens after the holidays, if Easter is late the deadline happens before Easter </li></ul><ul><li>The deadline is never DURING Easter </li></ul>
  32. 32. Dissertation Submission <ul><li>The student submits two copies of their dissertation, one for supervisor, one for second reader. And e-mails an electronic copy to the co-ordinator, and the software. </li></ul><ul><li>The deadline is FIXED, a student cannot be late unless they have very serious circumstances. </li></ul><ul><ul><li>Like a read deadline in industry </li></ul></ul>
  33. 33. Final Demo <ul><li>Supervisor, second reader and coordinator, and anyone else </li></ul><ul><li>Students present PPT for 10 mins and demo software for 10 mins, a Q+A session follows in which the audience asks the students questions and clarifications </li></ul><ul><ul><li>To check students wrote software </li></ul></ul><ul><ul><li>To check students understand topic clearly </li></ul></ul><ul><ul><li>To check a good approach was taken </li></ul></ul><ul><ul><li>To assess the students presentation skills </li></ul></ul><ul><ul><li>To confirm marks assigned to project </li></ul></ul>
  34. 34. Finally <ul><li>Supervisor must keep a careful set of notes on all student-supervisor issues </li></ul>

×