2. 1 Project Information and Acceptance Testing Integrating Your Code Final Code Submission Acceptance Testing Other Advice and Reminders

3. 2 Integrating Your Code In the next few weeks, group members will Write code for their modules Get their modules compiling and tested Submit their compiling, tested code to the group for integration We suggest that you set an integration deadline within your group for submission of code to the group We suggest that this integration deadline be AT LEAST 2 WEEK BEFORE THE CODE SUBMISSION DEADLINE! At the integration deadline, if a member has not submitted their code: Other members of the group should feel free to write their own version of the code based on the contents of assignment 2

4. 3 Avoid Submitting Bad Code You should try to submit code to your group which: Compiles without syntax errors Is free of obvious bugs Everyone makes mistakes Even good programmers will have bugs in their code We all tend to judge our own code less harshly than others’ However, if you submit bad code to your group (e.g. code which doesn’t compile, code which doesn’t even begin to do what it is supposed to do): Don’t be surprised if it is reflected in your peer evaluations Do comment your code so that others can modify it if they need to Realize that those who are integrating the modules are working under a deadline, so modifications may be necessary

5. 4 Final Code Submission You will be required to submit all final code to us electronically THERE ARE NO LATE SUBMISSIONS ALLOWED FOR THE CODE SUBMISSION DUE DATE! We must be able to compile the code, etc. All code must be in one directory (or in subdirectories within it) Submit your jar files containing all your.class files and.java files BUT you don’t have to submit your.java files and.javadoc till assignment 4 (thus your comments don’t have to be perfect) Doesn’t matter who from the group issues the command, however, please don’t have multiple people submitting versions submit will send you a confirmation message The last version submitted before midnight of the code submission due date is the one we will do acceptance testing on i.e. the midnight between the Saturday and the Sunday

6. 5 Acceptance Testing Acceptance testing of your finished projects will take place the Tuesday and Wednesday following the Saturday that the code was submitted CS2212 classes will be cancelled for all of that week Each acceptance test will be about 1 hour long Your instructor will be present at each test A teaching assistant will also be present, though not necessarily the one assigned to your group during the term Your group will have to sign up for a time slot: See the web site for the available slots and the date you can start to sign up on. Sign up by emailing me your pick time slot from: http://www.csd.uwo.ca/~lreid/cs2212/TimeSlots.html http://www.csd.uwo.ca/~lreid/cs2212/TimeSlots.html

7. 6 Other Thing to Remember You don’t need to continue submitting minutes after the code submission due date Your t.a. will no longer attend meeting after the code submission due date Peer Evaluations are due after Assignment 4 (not after the submission of the project code): Check to see when the peer evaluations are due, THERE ARE NO LATES ACCEPTED FOR PEER EVALUATIONS You lose 5% off your final project mark for NOT submitting peer evaluations! Submit the a peer evaluation form via the CS2212 web site The peer evaluations are confidential Please take the peer evaluation form seriously when you fill it in, as the form could cause a person to fail the course, if for example, all other members gave one person poor evaluations

8. 7 Hints from Teaching Assistants & Faculty For A Successful CS212 Project Below is a list of quotes from T.A’s and faculty giving you hints for a successful project in cs2212: Take ownership of your project, if someone has promised you code and you don't see the code, don't assume it has been done. Make sure everyone shows their work to everyone else in the group. Remember if you are too trusting, it is YOUR mark that is on the line as well as the person who didn’t finish their portion of the code. Address small issues immediately before they become major issues. If the group encounters a problem, let your T.A. know immediately. It can be difficult when dealing with peers to insist that they do their fair share, but if you don't all your other courses may suffer. It is your responsibility to see that the group works as a whole. If you don't take responsibility don't expect to have your mark adjusted at the end because a group member did not participate fully. Check each other's work to be sure it is done correctly. Be helpful. This is a learning experience: whether you are learning how to help co-workers or whether you are learning how to improve the quality of your work. Working successfully with team members is an important real world asset and knowing how to learn from others will help you to be a success. Usually the successful groups are the groups that have created an environment in which everyone feels free to give input, ask questions or ask for help with a problem.

9. 8 Hints Continued… Remember that compromises may have to be made. Not everything has to be done your way (“There are only two ways to do things my way or the wrong way”  is not a productive attitude) Attend lectures. You may think that they are unnecessary but lectures give added information and stress what you need to know. Work ahead of deadlines, or at least as soon as the assignments are given out. It's hard to do, but you'll be happy when you pass your acceptance testing because of it. I mean the obvious ones are  start coding early, and integrate early, but they never listen. Utilizing the T.A.s you have available for advice on how to do things may also not be a bad idea. We make you take 2210 for a reason, so that you can learn how to make proper data structures. You should ask yourself early "how efficient is this". Do not program for the test data An unsorted Linked List is always inappropriate. I think the other hint is start early. It's difficult to take ownership in the last few days. TAKE OWNERSHIP OF YOUR PROJECT Fill in the blanks: Take ________________ of your ____________

10. 9 And… We (Laura and her T.A.s) want ALL the groups to be successful!