Work to Learn. Don't work for marks.

• General Assessment Policy
  • Project Web Site - Progress Report - Group Meeting and Presentation

• Group Meeting and Presentation Schedule
  • Summer Group Meeting I (8 Jun. 2003, 2:30PM - 4:30PM, Room G5-430)
  • Summer Group Meeting II (6 July 2003, 2:00PM - 4:00PM, Room G5-317)
  • Summer Group Meeting III (3 August 2003, 2:00PM - 4:00PM, Room G5-214)
  • Semester A Project Background Presentation (Sept. 2003)
  • Semester A Group Meeting I (Oct. 2003)
  • Semester A Group Meeting II (Nov. 2003)
  • Semester B Porject Mid-Term Presentation (Jan. 2004)
  • Semester B Group Meeting I (First or Second week of Feb. 2004)
  • Semester B Group Meeting II (First or Second week of Mar. 2004)
  • 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)

• Final Year Project Deliverables (department requirement)

• Work Schedule Table

• Downloads and Useful Links

General Assessment Policy

* important date

1. Project Web Site:
   • Students are required to set up their project web sites on the EDA center Web Server (http://www.ee.cityu.edu.hk/) for reporting the progress of project.
   • Students are not recommanded to spend too much time on desgining the graphics and the outlook of their project websites. Simple design and clear presentation of the project related materials are prefered. Here are two good examples: Site 1, Site 2, Kevin(2002)
   • URL addresses of the project websites have to be sumbitted to Dr. Po before 11 July 2003.
   • The first version of the web site should include the background, motivation, necessary theory, and the planning of the project, which should be available on the Web before 30 August 2003.
   • The second version is about the progress of the project in Semester A (e.g. implementations, results, and demo), which should be available before 31 Oct. 2003. (Week 9 of Semester A, which is also the due date of the progress report)
   • The final version should be available on 22 May 2004. Final year project marks will be submitted to the department if the final version of the project website is not available before the deadline.

2. Progress Report:
   • The Progress Report is submitted on Friday, Week 9 Sem A to both the supervisor and your assistant assessor.
   • It may be similar to your web site's materials (background , motivation and objective, theory, etc) but submit it in formal report format. Moreover, we expected this report should be the first few chapters of your FYP final report.

3. 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

• EE FYP InfoNet: http://proj.ee.cityu.edu.hk/cgi-bin/w3-msql/student/studentframe.html

• Paper Searching:
  • NEC Research Institute Scientific Literature Digital Library - http://www.researchindex.com/
  • IEEE/IEE Electronic Library Online - http://www.ieeexplore.ieee.org
  • ACM Digital Library - http://portal.acm.org
  • ISI Web of Knowledge - http://isi2.isiknowledge.com/

• Presentation Help:
  • Oral Presentation Advice - http://www.cs.wisc.edu/~markhill/conference-talk.html
  • PowerPointers - Article : http://www.powerpointers.com/index.asp
    

• Latex Help:
  • Getting Started with LaTeX - very basic overview, with little example
    http://www.maths.tcd.ie/~dwilkins/LaTeXPrimer/
    
    
  • Beginning LaTeX - Many Tex file example
    http://www.cs.cornell.edu/Info/Misc/LaTeX-Tutorial/LaTeX-Home.html
    
    
  • LaTeX: from quick and dirty to style and finesse -Write right for research
    http://www.sci.usq.edu.au/staff/robertsa/LaTeX/ltxqstart.html
    
    
  • LaTeX Tutorial Contents
    http://www.ldc.upenn.edu/jms/latex/tableofcontents2_1.html

  • For the student who're using windows platform :
    Recommend these 2 free tools which are enough for learning Latex and writing your report.
    MiKTex - Latex core engine http://www.miktex.org/
    WinTeX2000 - Tex file editor http://www.tex-tools.de/
    
    

Downloads

Learning Latex :

• Introduction to Latex 2e : download here (.pdf)

Report Templates (MS-Word) :

• Final Report Front Title Template : download here (please refer to InfoNet for final update)
• Dr Po's FYP report template : download here

Report Templates (Latex) :

• The report template in latex version will be uploaded soon.

[Top]