Submission of Final Report

If you submit report:

• Between 2 pm Monday and 2 pm on Tuesday, penalty is 5 points
• Between 2 pm Tuesday and 2 pm on Wednesday, penalty is 10 points

 Please submit a hardcopy of your report to Prof Stan's office. There will be a box placed outside his office in case he is not in.

Please email a softcopy of your report to all the teaching staff of CS3215.

Your report should comply with the required format given to you. The report should avoid repeating material contained in the handbook; instead, such material can be referenced. We recommend (not require) fonts Times Roman 12 pt single spacing. It is important to make your report clear and readable. Make it as concise as possible, but also complete. In any case, do not exceed 100 pages. In fact your report may be much shorter than 100 pages if you plan well what you want to say in the report. Use good examples to illustrate your query evaluation and optimization strategy. Include appendix only if you have a good reason to do so. Do not include code.

As the presentation time is only 35 minutes (including Q&A), your report becomes a crucial resource from which we can assess your performance. Don't let your months of hard work go to waste because of a poorly written report. Putting in that extra effort will definitely help you a lot in your overall grade. Emphasize in the report whatever you think is a strong point in your project that may affect your grade (e.g., good design solutions or extra features you implemented). Be brief about things that we already know well.

Final Project Presentation

• Presentation:  plan for 20 minutes
• Q & A : 15 minutes
• Defense of failed cases: 25 minutes

• Summarize your achievements. Define the scope of implementation, e.g., did you complete all the required functionalities? Which functions are not implemented? Any additional features implemented?
• Convey clearly to us any achievements that you feel are important and that make your project special.
• Describe the query evaluation strategy. Give a general description of your query evaluation strategy (plus optimization, if any) and illustrate with examples.
• Do NOT present things we already know (e.g. what is SPA). You do not need to explain the design of each component e.g. parser, AST, etc. However, if you feel that your design of certain components is unique and special enough to warrant our attention, feel free to present those.

Note: As the presentation is short, please do not go into too much detail. Basically, you will want to make use of this time to sell your SPA and convince us that your hard work this semester deserves a good grade. Therefore, concentrate mainly on your achievements and those special features of your SPA.

Project CD Submission

1. Source code of SPA. Put them in a subdirectory called source.
2. Test programs you used for testing your SPA (unit, integration and validation). For example, your cppunit test files and/or any test files you develop for your own testing. Put them in a subdirectory called test
3. Softcopy of the report. Put this in a subdirectory called doc.
4. Those files you used to compile and run your auto-tester (mainly your TestWrapper class). Put them in a subdirectory called auto.
5. Readme.txt file with instructions on how to compile and run the auto-tester on your SPA.
6. makefile (if you have one) in the submitted CD should have the following targets:
7. • autotester - to build the Auto-tester version of SPA
   • trial - build the Auto-tester version of SPA and run it against the sample testcases (distributed with the Auto-tester)
   • clean - delete all generated object/binary files

Important:

• As we only use the source code from your CD for testing, please ensure that you have put all required files on your CD.
• Remember to label your CD and the cover with your team number (at least).
• The deadline for CD with your code is 13 April 12 noon. Grace period - 2 hours, we accept your code without penalty until 2 pm.
• If you submit code:
• between 2 pm today and 2 pm on Thursday, penalty is 5 points
• between 2 pm Thursday and 2 pm on Friday, penalty is 10 points
We won't be able to accept your code after 2 pm on Friday

24 Hour Code Resubmission

You will be given opportunity to fix SPA problems encountered during final testing of your programs. Each team will be given 24 hours to resubmit SPA, which will be counted from the end time of team's presentation. Late re-submissions will not be accepted.

1. SPA source code (just like your earlier CD submission).
2. Explanation of errors that you expect to be fixed in resubmitted SPA
3. Explanation of what was causing errors in your initial submission and what you have done to fix the errors
4. List of source files that have been changed and explanation of detailed changes

Important Notes...

• Configuration of the test machine is similar to machines in the lab where we had the trial run. You can use these machines for performance testing your SPA.
• SIMPLE program we use for testing is over 350 lines of code. We do not limit the time you take for parsing. However, we record the parsing time. This data may be considered during grading. Your program should be prepared to work with much longer SIMPLE sources although for longer programs of course the query evaluation time might be longer.
• The default time limit Autotester allows for evaluating each test query is 5000ms. If the SPA does not return an answer after 10s, we assume an 'infinite loop' situation and the testcase is considered failed.