2002 Final Year Project Assessment Policy

Learning is like picking shells on the beach,
It is hard but exciting. ~Einstein



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 14 July 2002.
    • 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 2002.
    • The second version is about the progress of the project in Semester A (e.g. implementations, results, and demo), which should be available before 1 Feb 2003.
    • The final version should be available on 22 May 2003. 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 Presentation:
    • 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.

  3. Progress Report:
    • The Progress Report is submitted on Friday, Week 7 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.
    • Recommend to use Latex in writing your report. Learn Latex here .
  4. Progress group meetings:
    • Progress group meetings for discussing major problems on the project development will be arranged about one or two weeks before the progress presentations.

    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]


Meeting Schedule

Date
Time
Location
Remark
6 Jun. 2002
3:00p.m.- 4:00p.m
G6302
-
16 Aug. 2002
1:30p.m.- 2:20p.m.
Y5202
-

[Top]

Progress Presentation

Students should attend at least one other group's presentation, but you are encouraged to attend all presentations. Each student will have 30 min. for presentation.

- First Progress Presentation -
Date
Time
Location
Remark

5 Sept. 2002 (Thu)

2:30- 4:20
Y5403
Session One:
1. Mobile Agent-Based e-commerce System
2. LinSpy: A Linux based Digital Security System
13 Sept. 2002 (Fri)
2:30- 4:20
P1808
Session Two:
1. Web Based E-logistic System
20 Sept. 2002 (Fri)
2:30-4:20
G6302

Session Three:
1.Image Database Indexing and Retrieval System with Parallel Computing Engine
2. Fault-Tolerant Cluster Manager for Beowulf Class PC Cluster

 

- Second Progress Presentation -
Date
Time
Location
Remark

13 Jan. 2003 (Mon)

2:30- 4:20
P1808
Student present: Edger and Horace
22 Jan. 2003 (Wed) 3:30 - 5:30 P1808 Carrie, Sam, Christy, Sald


TBC - To Be Confirmed


[Top]


Final Year Project Deliverables

1. Final Report 

    • You should follow the standard front title provided by EE department -
      Download a Word front page template (should be available in the mid of sem. B)
    • 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]
 


Work Schedule

The timetable for the major stages of the project is set out below.

Stage
Date
Summer Group Meeting I 6 Jun 2002
Summer Group Meeting II 16 Aug 2002
First version of FYP website 30 Aug 2002
Progress Presentation I Sep 2002
Progress Report Oct 2002 (Week 7 Friday)
Semester A Progress Meeting Dec 2002
Progress Presentation II 1st session 13 Jan 2002
Progress Presentation II 2nd session 22 Jan 2002
Semester B Progress Meeting Mar 2003
Start preparing FYP Presentation Week 9, Semester B(recommended)
FYP Presentation Week 10 , Semester B
Start drafting final report Week 11 , Semester B (recommended)
Final Report Submission & Demo Week 13 , Semester B

The precise dates and times for the presentations will be notified to you by email.

[Top]


Useful Links and Helps


Downloads

Learning Latex :

Report Templates (MS-Word) :

Report Templates (Latex) :

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


[Top]  


[ Back to FYP website]

Last updated: Aug 05, 2002