2004 Final Year Project Assessment Policy

Work to Learn. Don't work for marks.

  • General Assessment Policy

  • Group Meeting, Progress Report and Presentation Schedule

    • Summer Group Meeting I (June 2004)
    • Summer Group Meeting II (July 2004)
    • Project Proposal Meeting (August 2004)
    • Semester A Project Progress Presentation (Sept. 2004)
    • Semester A Group Meeting I (Oct. 2004)
    • Semester A Group Meeting II (Nov. 2004)
    • Semester Break Project Progress Report (Dec. 2004)
    • Semester B Porject Mid-Term Presentation (Jan. 2005)
    • Semester B Group Meeting I (Feb. 2005)
    • Semester B Group Meeting II (March 2005)
    • Start preparing FYP Presentation (Week 9 of Semester B)
    • FYP Presentation (Week 10 of Semester B)
    • Start drafting final year project report (Week 11 of Semester B)
    • Final report sumbission and Demo (Week 13 of Semester B)

General Assessment Policy

  • Project Proposal:

    • Students are required to submit a project proposal by email on 15 August 2004.
    • The proposal should include the following items:
      • Project Title
      • Abstract (A summary not more than half page)
      • The Project Objectives and long-term significance (Max 1 page)
      • Background of research (Max 5 pages)
      • Methodology and Schedule (Max 3 pages)
      • References
    • We provided a proposal template to student for reference.

  • Progress Report:
    • The Progress Report is submitted on 22 Dec. 2004 during the Semester Break to supervisor by email.
    • The progress report is similar to the project proposal but more details on what you have done in the semester A. The progress report should include the following chapters:
      • Project Title
      • Abstract
      • Introduction (with the motiations and objectives of your project)
      • Background (This chapter may not be called background, which cover the related theory and technologies of your project)
      • Methodology (What you have achieived in the last semester)
      • Revised Plan
      • References
      We expected this report should be the first few chapters of your FYP final report.

  • Progress group meetings and presentations:
      • Progress group meetings for discussing major problems on the project development will be arranged about one or two weeks before the progress presentations.

      • A 30 to 45 minutes presentation on your progress, which is arranged in schedule. Students are required to update their project websites before the presentation. Here are some good resources about oral presentation.

      Grading will be based on the results of the work (that is, "did it work?"), the degree of innovation, and the quality of the written report (included the project website) and oral presentation.

    [Top]

    Final Year Project Deliverables

    1. Final Report 

      • We provided a report template to student for reference.
      • Final Report has to be completed in before the end in the semester B. Details of submission will be noticed in our department website.
      Suggested contents (not exclusive)
    • a. One page abstract summarizing (1) the aims, scope and significance of the work, (2) techniques and tools used, (3) results and performance of the product (4) brief conclusions.
    • b. Introduction giving the background, motivation of the project.
    • c. Chapters describing necessary theory, implementations, and results of your work.
    • d. Conclusions summarizing the output/product of the project, and achievement.
    • e. References
    • f. Appendix, e.g. Definations about standards, specification of your defined file format, H/W model no./specificaitons as well as S/W used in your project
    • Don't include listings of source code. These are only suggested contents. They MAY NOT be suitable for all projects.

    2. Demonstrations 

    Grading will be based on the results of the work (that is, "did it work?"). A project demonstration to your assistant advisor should be done in the mid of semester B. And there is also a final demonstration to your supervisor at the end of your project.

    3. CD-R

      Contents of the CD-R
    • a. project preparation/data collection about your project. (papers/transactions/standards files in pdf/ps format.)
    • b. software files of your progress reports, final report (word, postscript or pdf files)
    • c. project website (It should be relative by the local path, don't use absolute reference!)
    • d. source codes of any programs / applications (Difference version shold be separate by different directories.)
    • e. demonstrations / results (A new directory called "demo" is more suitable. It should only contain a new updated version of your project executable as well as all required files in the same directory. A file may be required for description of the demonstration procedures, required H/Ws, since there may be required a copying action on some DLLs' files into x:\win\system.)
    • f. an index file describing the contents of the CDROM.
    • (It should describe the contents of each directory. In addition to further development, the programming languages used in your project should also be identified, or recorded together if u have the corresponding liscensed s/w. Since there may be involved some 3-rd party win32 APIs or other OLE/COM/DLL written in other languages, you should also record these 3-rd parties or downlaoded plug-ins in order to make your program more stable and compatible instead of newer version in the future.)

    4. Hardware Prototype of your project

    The CD-R is record of your project result and will be assessed for your final grading. Thus, you should ensure the data is well organized and all your related documents, source codes/programs, simulation results should be retrievable from the virus-free CD-R! Otherwise, un-retrievable CD-R is assumed to be empty

    [Top]
     

    Useful Links and Helps


    [Top]  

    [ Back to FYP website]

    Last updated: May 27, 2003