CompSci 165 Team Registration and Project Submission/Evaluation

Project Policy

• Each project is to be done by teams of size two (see Team Policy, below)
  IMPORTANT: "Done by teams" means that team members must each contribute substantially to the project submission.
  It is not acceptable for team members to independently develop the project and then decide which member's work is to be submitted.
• You may make use of ideas found in any book, journal, or website, or obtained from talking with any person.
  HOWEVER, you must be careful to give proper attribution to any such sources
  by indicating in your code and in your project write-up the full reference for each such source
  • book/journal title, author, and page number, or
  • full URL of the webpage, or
  • name of the person from whom you received a "private communication"
• Code must be original, and may not be copied or shared from any other source, except as provided by the class instructor

Team Policy and Registration

• Teams for each of the CompSci 165 projects consist of two CompSci 165 students
• For each project, students choose their teammates by mutual consent and agree who will be the team head member
• For each project, the head member of each team shall register the team members using the registration form found at this location
• Students who have not been registered for a team before 9:00am on the registration due date will be assigned to teams by the instructor
  • the instructor will also designate who is to be the head member for assigned teams
  • students on assigned teams will receive email notification of their team membership roster

Project Submission

• Projects are to be submitted to the class dropbox before 9:00am on the submission deadline date listed on the Class Schedule.
  Instructions for using EEE dropbox can be found at https://eee.uci.edu/help/dropbox/students/
• No late submissions will be accepted
• For each project, the team head member should submit a zip file containing all required deliverables
  IMPORTANT: Submit only one zip file that contains all files you wish to be considered. Do not submit any other files.

Project Evaluation

• Correctness — the program system works according to project requirements
  • C/C++ source compiled using gcc/g++ on Linux
  • no syntax errors, no run-time errors, and the correct output must be produced
  • improper input gracefully handled, allocated space returned after it no longer is needed,
    and error-checking performed after calling any system or library function
• Program structure — modularized, concise comments, indentation, descriptive variable names, explain "magic" numbers
• Documentation — keep this very short please
  • how to compile and use the program
  • description of data structure implementation
  • theoretical resource complexity analysis of the underlying algorithms
  • production of a function (based on empirical observations and analysis)
    to predict resource complexity for larger instances of the problem
• Efficiency — each project may specify special features or competitive characteristics