CS 150 - Intro to Programming - Spring 2002

| CS150 | Labs | Projects | Assignments | CodeSamples | Help Resources | Style Guide |


Programming Projects


Preparation and Planning Your Work

To be ready for each programming assignment, be sure to read through it and relevant sections of the textbook before you begin. Do not immediately start coding. Plan and organize what you want to do first. Begin with pseudocode and/or partial code. Do this early so that you can get answers to any questions you have in plenty of time to complete the project. Don't rely on your imagination to do the hard work. Seasoned professional programmers spend much of their time planning and organizing. Doing it over, patching it up, and correcting extemporaneous mistakes always takes more time than executing a well developed plan.

Submitting Your Work

You must deposit an electronic version of your programming assignments in the appropriate folder by 6:45pm on the specified due date. In addition you must turn in a hard copy (printed) of your work. The hard copy is due at the beginning of lecture on the posted due date. Late work will not be accepted or graded. If you have not completed your assignment by the time it is due, you may turn in what you have completed for partial credit. Note that very little credit will be given for programs that still contain syntax errors and do not compile. In some circumstances, due dates may be negotiated with your instructor. It is your responsibility to make such arrangements before the work is due. To guard against clerical errors, retain all of your completed course work until after you have received your grade for the course. All work you submit for a grade must be your own - any program which does not show independent thought or work will be given no credit - see the Policy on Collaboration for details.

Programming Project Grading Criteria

The programming projects will be graded according to the following criteria:

Contains Required Documentation (see below) 10%
Follows Good Program Design and Style Guidelines 20%
Compiles and Links with No Errors 20%
Runs and Meets Project Specifications 50%

Required Documentation

Every source and header file you submit for this class must include at least the following documentation at the top:

  1. the name of the file,
  2. the author's name,
  3. the date the file was last modified, and
  4. a brief description of the contents of the file.

Every source and header file you submit for this class must follow the guidelines in the Style Guidelines document.


Programming Projects

Project 1 Due: Mon. Feb. 4th
Project 2 Due
Project 3 Due
Project 4 Due
Project 5 Due
Project 6 Due
Project 7 Due
Project 8 Due
Project 9 Due
Note: All project must be submitted before 6:45pm
on the date listed above


| Robert Hillyard | SSU | CS Dept | CS 150 |