TopIn this section, you will find instructions regarding submission of your Final Report, your Code as well as information about the Final Project Presentation.
Submission of Final Project Report and Code
The deadline for submission of your Final Project Report and Code is 4pm on 11 November (Wednesday).
If you submit report between 4 pm Wednesday and 4 pm on Thursday, penalty is 5 points (final submission has a maximum of 100 points).
If you submit code between 4 pm Wednesday and 4 pm on Thursday, penalty is 20 points (final submission has a maximum of 100 points).
We won't be able to accept your report and/or code after 4 pm on Thursday.
For multiple submissions received from the same team we will mark the most recent one.
Report and code softcopy submission: IVLE (see Section IVLE Submission).
Report hardcopy submission: Cristina's office (COM2-2-07).
Final Project Requirements
- Your report should comply with the Project Report Format given in Assignment 4.
- Avoid repeating material contained in the Project Handbook; instead, such material can be referenced. It is important to make your report clear and readable. Make it as concise as possible, but also complete. Use good examples to illustrate your design.
- 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.
How to submit:
Create a folder called Team<XX> with your code, documentation and supplementary information. Archive this folder in an archive called Team<XX>.zip, where <XX> is your team's number.
Submit the archive via IVLE:
What to submit:
As we only use the source code from your submission archive for testing, please ensure that you have included all required files. In the folder called Team<XX>, include the following:
File Team<XX>.pdf cotaining the final report.
Sub-directory called Code<XX> containing (at least):
Source code of SPA.
Solution file (.sln) for Visual Studio 2010/2015 (and additional project files). The solution (and all project included) should build and run without errors in "Release" configuration.
Readme.txt file with instructions on how to compile and run the auto-tester on your SPA, the name of your solution that has to be built and the path to the executable produced. Mention also which Visual Studio version to use and which configuration to use(Release/Debug). In case no VS version and configuration are mentioned, we will build and run using VS2010 in Release configuration. Do ensure that the solution files from your submission build and produce the correct executable.
The files you used to compile and run your auto-tester (mainly your TestWrapper class). Put them in a sub-directory called AutoTester.
Test programs (projects) you used for testing your SPA (unit and integration). For example, your cppunit test files and/or any test files you developed for your own testing. Put them in sub-directories called UnitTesting and IntegrationTesting.
- Contact.txt file with names of all team members and their contact information.
If you implemented any extensions (Assignment 4 or other notable features), then include code for extra features in a sub-directory bonus as follows:
If your source code of SPA with additional features is different from the basic SPA, then put source files in a sub-directory called source. If your extensions are integrated with the Basic SPA implementation, there is no need to have a separate sub-directory source.
Readme.txt file with instructions on how to compile and run your SPA, and any other information we may need in order to test your SPA.
Sub-directory called Tests<XX> containg your test you used for System Testing. These tests should be written in AutoTester format. Organize your tests in a logical way and write a README file to explain how to run them. In adidtion, include testcases for your extensions and bonus features in a sub-directory called test_bonus.
We use AutoTester to test your submission. Ensure that your code is integrated and works correctly with AutoTester (see Workbin->Tools->AutoTester for documentation).
We will test your implementation with a set of SIMPLE source codes and PQL queries. Failed test-cases will be discussed after presentation.
Please use the sample SIMPLE code on IVLE Workbin -> Tools to verify your parser will be able to parse our test cases. Also, note that the source code and queries are case-sensitive, so check that your SPA accepts and computes results according to correct casing (see AutoTester examples). In case we cannot compile your code or run SPA at all, we will contact you so that you can fix the problem. For that, please do not forget to include your contact information (see above) and be available after submission.
If the SPA does not return an answer for a PQL query after 5,000ms, we assume an 'infinite loop' situation and the test-case is considered failed.
We evaluate your code organization and the match between your implementation and the abstract API calls described in the report.