> /cad2/ece297s/public/testsubmitece297s 3
This script does not submit your code. You may use it as a check before you are ready to submit your code. Once you get the positive confirmation from the
We highly recommend that you continue to use the
Save the output of the Testsubmit script as follows.
> /cad2/ece297s/public/testsubmitece297s 3 > testsubmitAss3.log
Please make sure that you include the output file
Make sure the FINAL versions of all your changes are added and committed to the Subversion repository. Don't forget to
You will be submitting two files: storage-asst3.tgz will contain your complete source code, and storage-asst3.diff will contain a record of the changes you've made to the code since the initial checkin.
> mkdir ~/ece297/submit > svn export ~/ece297/storage ~/ece297/submit/storage-asst3 > cd ~/ece297/submit > tar zcf storage-asst3.tgz storage-asst3 > rm -r storage-asst3 > submitece297s 3 storage-asst3.tgz
Refer to this page for a list of common submission problems and how to solve them.
> mkdir ~/ece297/submit > cd ~/ece297/storage > svn diff -r 1:HEAD > ~/ece297/submit/storage-asst3.diff > cd ~/ece297/submit > submitece297s 3 storage-asst3.diff
Be sure to do a final check by running your tests on your submission.
> mkdir ~/ece297/tmp > cd ~/ece297/tmp > tar zxf ~/ece297/submit/storage-asst3.tgz > cd ~/ece297/tmp/storage-asst3/test/query > make run > cd ~/ece297/tmp/storage-asst3/test/set > make run > cd ~/ece297/tmp/storage-asst3/test/get > make run
If you haven't already done so, you can also run some of our tests. Some of the marking tests are available at
> cd ~/ece297/storage/test > tar zxf /cad2/ece297s/public/assignment3/a3-partial.tgz > cd a3-partial > make clean run
We only mark the files submitted by member of the teams. You can see which submitted files will be marked by entering below line at all team members' command prompt:
> checksubmit 3
In particular check the file size and latest submission date to confirm the correct file was submitted. Carefully examine the .tgz and .diff files to make sure all your changes are there, including the unit tests you added.
Refer to the page here for some common submission problems and how to solve them.
Your assignment will be marked based on the code and the design document you submit.
The code you submit for this assignment will be evaluated as follows. We will build your system and test it for correctness based on a set of test cases. For example, we will issue get/set calls and check for the return values and error conditions.
It is therefore critically important that you adhere to the Makefile template and code template we provide for you, as our build scripts will be based on these files. At the very least make sure the test suites given to you pass.
Marks will be allocated to a flawless build of your system. Should your build fail, we would try to fix the problem with reasonable effort, but would deduct some marks. Should our intervention not lead to successful build of your system, we will inspect your submission and allocate marks based on an assessment of the development effort, the documentation, the clarity and cleanliness of your code.
Marks will also be allocated to the number of test cases your system correctly passes.
A perfect score for your code submission can be achieved if your system builds correctly and passes all test cases.
As with the M2 Design Document: Basic Storage Server, the fundamental basis of evaluation for the M3 Design Document are principles laid out in the course text book. That is, we will not be grading on the basis of qualitative judgments of what makes good or bad writing, but rather how well you are able to implement awareness of purpose and audience, overall organization, rhetorical tools, paragraph and sentence level clarity, as well as visual elements.
You are expected to be able to analyze the instructions in order to determine the design decisions pertinent to the assignment and to discuss these decisions in an orderly fashion. Information must be easy to find, and language must be precise, efficient and correct.
A perfect score is possible if your document is thoughtful, technically accurate, economically and clearly written, supports every statement meaningfully with either logic or data (your own or from research sources), has absolutely no padding of any sort, and contains very few to no errors in grammar, syntax or usage.
Here is the marking scheme for the coding portion:
In this assignment you may obtain the following bonus marks.
Milestone 3 >