Projects

Turning in Projects

All projects are team projects in this course. For each project, all students must form teams of two (or three in the case of an odd number of students). Students are permitted to select their own teams; however, no two students may partner up for more than one project. In other words, each team will be different for each project. Students should select their teams through Brightspace.

Teams are responsible for dividing their workload. Except under extreme circumstances, all members of the team will receive the same grade for each project. One member of each team is designated the leader. The files for each project should be zipped up and uploaded by the team leader using Brightspace before the due date. If the project is late, the group will receive a score of 0. If the project does not compile, the team will receive a score of 0.

Projects will be graded based on the following criteria:

  1. Correctness
    Finding the right answer

  2. Efficiency
    Efficiently using processor and memory resources

  3. Formatting
    Displaying the right answer according to instructions

  4. Style and Documentation
    Producing readable code with appropriate comments

Late projects will not be accepted, with the following exception. Each student has 3 grace days. These grace days may be used together or separately to allow a 24-hour extension of the project deadline per grace day. A team wishing to use a grace day must inform the instructor via e-mail before the normal deadline. Both students in the team will have the appropriate number of grace days deducted. If the members of a team have different numbers of grace days available, the team will be treated as if it has the maximum number of grace days of any of its members.

Under no circumstances should a team member look at the code written by another team. Tools will be used to detect code similarity automatically.