Congrats on passing the first of the several 'final submission' hurdles i.e., submitting the product v1.4! If you faltered near the deadlines, not to worry so much. Take it as a learning experience -- you could have avoided it with better planning. While those problems may be penalized, we are generally lenient and the penalties are not very big.
Some points to note at this time:
We start the evaluation process tomorrow (Wednesday). Any problems in your submitted files need to be fixed today! (note: such post-deadline fixes are liable to a late-submission penalty). We recommend you download your own submissions from IVLE and double-check to ensure your jar file works and all files are of the correct version. You may have uploaded the wrong version due to the deadline rush.
You may wish to look at the PPP (and the RepoSense link in the PPP) of your team members to confirm that what they have claimed as their work is in fact their work. Any incorrect claims, intentional or accidental, needs to be corrected ASAP. Please notify the relevant member and us too.
There are two peer evaluations now open on TEAMMATES. Both are compulsory. Furthermore, both you and reviewees are graded based on your responses to those sessions. In particular, Final Peer Evaluation (Part 1) needs to be submitted before the PE on this Friday as it is a precursor to the PE. You have one extra day to submit Part 2.
Please read demo instructions and prepare as instructed before coming to the demo.
See this message from AB-4 dev team. They are keen to hear your inputs, negative inputs in particular (don't hold back š). You can help the dev team and future students by sharing your views.
IMPORTANT
Final Peer Evaluation (Part 1) requires you to estimate the effort by team members on a scale of 0-30. It also asks you to evaluate the effort of a sample PR. In the PE you will evaluate the efforts of another team. All three of these should be done using the same scale given in the practical exam instructions -- screenshot given below. This is a serious matter; your estimate for each person will be cross-validated against 10 other estimates for the same person (given by tutors and peers), and you will lose marks if your estimates are far off from the consensus. In particular, your estimate for the sample PR is of critical importance because it will be used to normalize your estimates before comparing them with other estimates. Bottom line: 1. do your very best to use a consistent scale for all three questions 2. try to ensure your scale is similar to the scale given in the insturctions.
Congrats on passing the first of the several 'final submission' hurdles i.e., submitting the product v1.4! If you faltered near the deadlines, not to worry so much. Take it as a learning experience -- you could have avoided it with better planning. While those problems may be penalized, we are generally lenient and the penalties are not very big.
Some points to note at this time:
IMPORTANT
Final Peer Evaluation (Part 1) requires you to estimate the effort by team members on a scale of 0-30. It also asks you to evaluate the effort of a sample PR. In the PE you will evaluate the efforts of another team. All three of these should be done using the same scale given in the practical exam instructions -- screenshot given below. This is a serious matter; your estimate for each person will be cross-validated against 10 other estimates for the same person (given by tutors and peers), and you will lose marks if your estimates are far off from the consensus. In particular, your estimate for the sample PR is of critical importance because it will be used to normalize your estimates before comparing them with other estimates. Bottom line: 1. do your very best to use a consistent scale for all three questions 2. try to ensure your scale is similar to the scale given in the insturctions.