University of Rochester Computer Science

Computer Science 171: Computer Programming

Home
Contacts
Labs
Lab Times
Lectures
Links and How To's
Projects
Programming Standards
(A.K.A. how to get a good grade on projects)
Schedule
Syllabus
Turn In (How to)
Workshop Times
WebCT

Projects

Project Specs are posted on the Schedule page as they become available. Please read these specifications thoroughly to understand the requirements. That will help to get good grades. If you have any questions concerning the project, post your questions to the newsgroups. Most of your classmates may already know the answer and the TA and Professor check the newsgroups regularly.

Contact the TA for questions regarding your grade.

 

Grading Guidelines (metrics) for Projects.

Project #1: National Pastime

  • Part 1 : How Far : 10% (for correct position calculation)
  • Part 2 : Basic Math : 10% (for both root calculations)
  • Part 3 : Flight Time : 10% (for both time calculations)
  • Part 4 : Flight Distance : 10% (for correct distance calculation)
  • Part 5 : Graphing the Trajectory : 30% (for proper graph drawing not necessarily a fancy one)
  • Coding Style : 10% (indentation, documentation, naming conventions, readability of the code, and so on..)
  • Architecture : 10% (How the different components of the program are organized.)
  • User Friendliness : 10% (How much convenient for the users to run the program)
  • Bonus : 20% (As much as you could do, good looking graph, nice font, detailed annotations, handling wide range of inputs...)

Project #2: Calculator

  • Part 1 : Calculator Engine : 30% (should be an idependent component)
  • Part 2 : GUI-based Calculator : 35% (should have proper layout design and use the Calculator Eengine (part 1) for doing operations)
  • Part 3 : Commandline Calculator : 15% (should use the Calculator Eengine for doing operations and the expression to evaluate is to take from console)
  • Coding Style : 10% (indentation, documentation, naming conventions, readability of the code, and so on..)
  • Architecture : 10% (How the different components of the program are organized.)
  • Bonus : 20% (As much as you could do, specially error handling, extra functionalities.)

Project #3: Game of Life

  • Part 1 : Game GUI and Engine : 60%
  • Part 2 : Save the Game in file: 10%
  • Part 3 : Load the saved Game from file: 10%
  • Coding Style : 10% (indentation, documentation, naming conventions, readability of the code, and so on..)
  • Architecture : 10% (How the different components of the program are organized.)
  • Bonus : 20% (Fancy GUI and Error Tolerance.)
Updated 26-Nov-2006 16:15