1. 1. Course Assessments

1. Project Proposal

A project proposal (1-2 pages) outlines what system or application you wish to develop, the motivations or aims, user requirements or required functions, system structures and a rough plan. What you need to submit is a standalone Word or PDF file. A template for the proposal is provided.

2. Project Progress Report

The project progress report aims to provide an opportunity for students to reflect what they have achieved in the process of the project development. For the progress report, please submit a ZIP file containing the following:

- Your updated proposal (Word or PDF). You can take this chance to update project proposal. The project proposal is named "Proposal.doc" or "Proposal.PDF" ;

- A project progress report (Word or PDF) named "Documentation.doc" or "Documentation.PDF". The document is typically 5-10 page long and must at least contain the following sections:

o Architecture. A diagram showing the overall architecture of the project. This diagram should clearly display the different functional modules involved in the system and their interaction and relationships;

o Snapshots. All the snapshots of the system interfaces that you have developed. You can capture the screen using various screen capture softwares;

o Classes. A detailed documentation of all the classes (including their fields and methods) involved in the system. You need to provide detailed description of each class, field and method regarding their meaning, usage and relationships. A hierarchy diagram of classes may be included.

3: Final Project Report

The final project submission is expected to be lodged at the end of the semester. Both documentation and source code need to be submitted. Specifically, the final submission should include the following four (4) items:

- The finalized project proposal (Word or PDF). It will be used for the assessor as a summary of your project in the final submission. The project proposal is named "Proposal.doc" or "Proposal.PDF" ;

- A project report (Word or PDF) named "Documentation.doc" or "Documentation.PDF". The document is typically 15-20 page long and must at least contain the following sections:

o Background and Motivation. Please discuss the background of the project and motivation behind your decision for carrying out the project;

o Architecture. A diagram showing the overall architecture of the project. This diagram should clearly display the different functional modules involved in the system and their interaction and relationships;

o Snapshots. The complete set of snapshots of the system interfaces. You can capture the screen using various screen capture softwares;

o Classes. A detailed documentation of all the classes (including their fields and methods) involved in the system. You need to provide detailed description of each class, field and method regarding their meaning, usage and relationships. A hierarchy diagram of classes may be included;

o Features. Please state how do you particularly implement the feature(s) of Java language you have chosen in your project. For example, if you choose to use JDBC to develop database applications, you need to state how do you use JDBC to establish connection to the database and how do you use the database in your system;

o Use instructions. A document contains instructions as to how to compile and execute the java code. Please be as specific as possible in the instructions;

o Lessons and experiences. Please discuss any lessons you learn from this project and any experiences you would like to share from this work;

o Conclusion. Conclude the whole project and possibly identify the limitation of the current system and any future work.

- A separate directory, named "SouceCode", containing all the Java source code. Please make sure to provide adequate comments within the programs for help assessor to better understand your code. A script file (e.g. a .bat file or a makefile) may also be included in the folder.

- A short video clip to demonstrate your system. Please see the following for the detailed instruction for the video clip.

The final project proposal, project report, the source code and the video clip need to be zipped into a single file for submission. You can also provide a link for the video clip if it is available somewhere on the Internet.

2. Instruction for the Demonstration Video of your system One of the most important assessment items that you need to submit is a short (3-5 min.) video clip that shows how your system is executed and working. This video is important as it provides a good opportunity for training your skills in presenting your good work to others and significantly facilitate the evaluation of your project by the marker. Your video should cover the whole operation of your system, from the start of the system until finishing going through all the major functions/features that are developed. You can use ANY existing on-screen activity capturing softwares to produce this video. One of the good candidates is Camtasia Studio or Camtasia Mac (www.techsmith.com/Camtasia). This software is not free though but you can download a trial version for producing your video.

Your video shouldn't be fancy and doesn't need to have any (sophisticated) editing. A simple recording of running your system is sufficient. It is required to record voice in the video at the same time for any explanations you may want to provide. Please export the video using thelowest resolution in order to keep its size minimum. Please submit the video in some commonly-used formats such as MP4 or AVI. You can submit the  video together with other documentations and source code of your project to Studydesk or you can upload your video to some other websites such as YouTube and provide a link in your submission.

Please kindly note that, irrespective of how well you develop your system, you will lose a significant portion of your mark if you fail to provide this video demonstration for assessment.

3. Bonus Projects

Bonus projects are created particularly to help students quickly grasp ideas of project for this course. A small portion of bonus points are given as an incentive for students to take up the bonus projects. Students can feel free to choose one of the bonus projects as their project for this course. They can also choose other projects designed by themselves. The detailed instructions for the bonus projects can be found on the course homepage.

4. General Notes and Suggestions

Some notes and suggestions are given for the course, as follows:

1. Please note that the Project Progress report is the Assignment 1 referred in the course specification.

2. The project must be implemented predominately in Java. Of course, you can use other languages such as HTML for Java Applet.

3. Start the project as early as possible. Feel free to discuss the project with other students or examiner.

4. Please stick to the deadline for submission. Please contact examiner if you are not able to submit the assignment on time and seek an extension.