Term Project Requirements
Ming-Hwa Wang, Ph.D. Department of Computer Engineering
Santa Clara University The Group Term Project The purpose of term project is to guide students going through the research process. As a graduate student (or senior undergraduates), this exercise can prepare her-/him-self for paper/patent publishing, thesis/dissertation writing, etc. The Project The term project need to be typed and should include the following 6 steps: 1. Problem presentation: Each student sends an email of your own idea
for term project topic, and present “what” and “why” (but not “how” yet) in a few minutes in class to attract your teammates. If your topic is chosen as the group project, you will get a little more credits.
2. Team forming (each team has 2 or 3 people): Find your team members, negotiate/decide the title of the group project and the team lead. Each team lead sends an email (to me and cc to all teammates) containing topic and names of teammates, and soft copies of 2 different papers (related to the team topic, if soft copy is not available, you can hand in hard copies before presentation) assigned to each member before due date.
3. Paper presentation: Each team lead sends email containing members’ paper presentation slides before class begins, and each person presents one of the two papers read. Different members in the same team need to present different papers. Each presentation takes about 5-10 minutes. The papers can be any journal/conference paper (prefer very recent papers instead of old/obsolete ones.)
4. Proposal presentation: Each team writes a formal proposal of “how” your group is going to do, the proposal contains parts 1, 2, 3, 4, 5 and part 9 in the project format below. Each team lead sends an email containing the proposal in PDF format and presentation slides before class begins. Each presentation takes 10-15 minutes, and is shared by all teammates in the team.
5. Project defense: Each team implements the project and makes discussion, conclusion and suggestions for future study, this contains parts 6, 7, 8 and 10 in the project format below. Each team lead sends
an email containing the whole project document in PDF format and presentation slides before class begins. Each presentation takes 10-15 minutes (including 5 minutes of demo to show your program runs and give correct results), and is shared by all teammates in the team. To save time, do not present whatever presented in the proposal presentation.
6. Each team lead submits your project as PN (N = last program assignment number + 1) using the “Submit” script (but Autotest is not needed) before project defense. The submission should include: • your source files (if you use free download source files, put the information and procedure of how to download in the README file, but don’t submit the original downloaded source files; only your own code and modified downloaded files need to be submitted),
• a README file for how to build and how to run, • Makefiles for Unix/Linux, .sln and .vcproj file for
Visual Studio on Window, and/or Eclipse working directory • sample input files Note: Please no executable, no binary files, no compressed files (e.g., zip, gzip, etc.) and no output files in the submission. If you need binary tools to run your project, please put how you download the tool in the README file instead of submit them (I can download it myself).
Project Format 1. title page, preface (for book only), acknowledgements, table of
content, list of tables/figures, abstract (at most a page) 2. introduction
• objective • what is the problem • why this is a project related to this class • why other approach is no good • why you think your approach is better • statement of the problem (optional) • area or scope of investigation
3. theoretical bases and literature review • definition of the problem (if you have mathematic formulation) • theoretical background of the problem (if needed) • related research to solve the problem • advantage/disadvantage of those research
• your solution to solve this problem
• where your solution different from others
• why your solution is better
4. hypothesis (or goals) • single/multiple hypothesis • positive or negative (only for proof correctness) hypothesis
5. methodology • how to generate/collect input data • how to solve the problem
• algorithm design • language used • tools used • a prototype (optional if time permit)
• how to generate output • how to test against hypotheses • how to proof correctness (required by dissertation only)
6. implementation • code (refer programming requirements) • design document and flowchart
7. data analysis and discussion • output generation • output analysis • compare output against hypothesis • abnormal case explanation (the most important task if you have it) • static regression (if you have complex curve to fit) • discussion
8. conclusions and recommendations • summary and conclusions • recommendations for future studies
9. bibliography 10. appendices
• program source code with documentation • input/output listing • other related material
Discussion, Presentation, and Questioning You need to actively participate the discussion, the presentation and questioning. Discussion is the best way to fully understand a problem, presentation is the best way to express your idea to others, and questioning is the best way to find problems.
The Group Term Project • problem presentation (2%) • questioning and discussion (10%) • paper presentation (10%) • proposal presentation (8%) • project defense (10%) • quality of work (60%) Policy and Information • The open project policy: any student can freely get copies of previous
student’s projects (but not the implementation code) by sending request email to me, and agrees to share her/his own project for future quarter’s students.
• Please read /home/mwang2/tips//projects for previous projects.
• Please read /home/mwang2/tips//www for related research.
• Please read /home/mwang2/tips/common/paper for where to find all research papers