CS100J Projects
Project Assignments
Grading
Philosophy
Style and Commentary
Submission Rules
Retrieving Graded Projects
Partners
Academic Integrity
Home
Announcements
Staff&Help
Material
Exercises
Exams
Information
Syllabus
Times&Places
Examples
Projects
Grading

Project Assignments
Programming projects will consist of larger programs to develop that help you build your problem-solving skills. You can download the assignments, provided below:
 
#
Due Date
Assignment
Code/Tips/Hints
Solutions
Viewable
1
 Tuesday 1/30
p1sp01.pdf
p1PartB.m | p1PartC.java
p1sp01sol.html
p1sp01sol.html
2
Thursday 2/8
p2sp01.pdf
Grading Form: p2sp01gf.htm
Use to obtain input: UserIO.java
Run DIS's solution: p2NumberGuess.class
p2Policies.txt
p2Operations.java
p2FindMin.java
p2Charge.java
p2NumberGuess.java
p2PartQuestions.txt
p2sp01gg.pdf (the grading guide)
p2Policies.txt
p2Operations.txt
p2FindMin.txt
p2Charge.txt
p2NumberGuess.txt
p2PartQuestions.txt
p2sp01gg.pdf (the grading guide)
3
Tuesday 2/27
p3sp01.pdf
Unreadable solution: p3sp01.class
To run it, see FAQ -> How
Grading form
p3sp01.java
Rimon's solution: TicTacToe.java
Grading Guide
p3sp01.txt
TicTacToe.txt
Grading Guide
4
Tuesday 3/13
p4sp01.pdf
Grading Form
p4sp01.java
Scovetta's solution: Cafe.java
Grading Guide
p4sp01.txt
Cafe.java
Grading Guide
5
Tuesday 4/10
p5sp01.pdf
Grading Form
TicTacToe.java
Simulation.java
InsertionSort.java
Complex.java
Grading Guide
TicTacToe.txt
Simulation.txt
InsertionSort.txt
Complex.txt
Grading Guide
6
Thursday 5/3
p6sp01.pdf
Grading Form
Java Files:
Belt.java
Disposable.java
Plate.java
Tray.java
Bowl.java
Fork.java
Quality.java
Utensile.java
Cup.java
Glass.java
Vessel.java
Sharpness.java
Definitions.java
Item.java
Size.java
Washable.java
Difficulty.java
Knife.java
Solid.java
Worker.java
Dish.java
Liquid.java
Spoon.java
p6sp01.java
Dishroom_blanks.java  MyMath.java
Thing.java
Due to popular demand: 
zip file: P6Classes.zip

MATLAB Files:
p6sp01.m getUserInput.m
restart.m getInputFile.m
welcome.m onesize.m

Grading Guide
Dishroom.java
matlab_files
Grading Guide
Dishroom.txt

Back to Top



Grading
Each programming project will receive three distinct grades for
  • correctness (C)
  • style (S)
  • bonus (B)
  • You can score 0-5 on both correctness and style. For example, you might receive a score of C5 and S5 for one project where you satisfy a majority of the requirements of the assignment. Graders might assign bonus points to reward additional/exceptional work. Look here for more information. We record your score in the form C/S/B. For instance, a 3/4/1 indicates a score of C3, S5, and 1 bonus point.

    If you work with a partner, both you and your partner will receive the same correctness and style grades for that assignment. See below for information about having partners.

    At the end of the semester, we add the style and correctness points from ALL projects to yield a total amount of core points for your project score. We will drop the equivalent of one project. So, if the maximum number of project points is 60 (from doing 6 projects), we will count the first 50 points you acheive. For example, suppose you score the following for 6 projects: 4/5/0, 4/5/0, 4/5/0, 4/5/5, 4/5/1, 4/5/0. You would have a total of 54 core points for your projects. A score of 54 ot of 50 gives you a pefect score of 50! (We'll also throw the "left-over" 4 points into your bonus score...nothing gets wasted!)

    Back to Top


    Philosophy
    Since projects "count" for a relatively small percentage of the total score, some students are tempted to skip them (or let their partners do most of the work) and plan to learn the material by reading the sample solutions.  This process does not work for most people. This material is learned by actively doing the projects, not by passively watching a partner or reading the sample solutions.  Thus, failure to actively do the assignments will likely hurt your grade.

    We expect projects to teach you how to solve more complex/larger problems. We grade mostly for feedback to let you know how you are doing. To reduce stress, projects are worth a relatively "small" percentage of the course score. Plus, we will not require you to do all the projects perfectly to get a perfect project score (see Grading, above).  Thus, as long as you make a sincere effort on most of the projects, you should get a good project score.

    Back to Top


    Style and Commentary
    Your comments and overall style will greatly affect your score on all work: Back to Top

    Submission Rules
    You have two options for submitting your work:
  • Submit homework in lecture on the due date. You may submit in either lecture, but no later!
  • Submit homework in Carpenter Lab for early submissions only. You must give the project to a consultant, personally!
  • Submit only ONE copy of your project, even if you work with a partner.
  • We do not accept late submissions. Homework will not be accepted after lecture, and if there are too many disruptions with students submitting homework in the middle of lecture, homework will be accepted only at the start of lecture.

    For each project you must do the following:

  • Print all your work as hardcopy, such as programs, output, and discussion answers. Please, no disks!
  • Include the grading form posted along with each project. Print and fill out one for each partner.
  • Include a title sheet and table of contents (you may combine on 1 sheet of paper) after the grading form(s).
  • Staple or bind together all sheets of paper. "Bind" means ring or folder, not twist-ties, string, or such nuisances
  • Submit entire code unless directed otherwise.
  • Type all work and responses to discussion questions.
  • Include the following comment block (e.g., % for MATLAB and // for Java) with your information filled in at the top of each program:
  • Name:  your name Partner:  partner's name
    ID: your ID ID: partner's ID
    Section: your section's instructor, day, time  Section: partner's section's instructor, day, time
    Date: due date
    Project: number and title
  • Ensure correct alignment of tab stops in programs with no "chopped"  line of code.
  • Note: Submit work as hardcopy, not as e-mail or on disk! We are considering adopting electronic submission later in the semester, however.

    Back to Top


    Retrieving Graded Projects
    Where's your work?
  • Projects are usually graded in about 1 week.
  • We usually return graded assignments in section, athough sometimes we choose Carpenter because of due date near prelims.
  • You may retrieve unclaimed assignments from the consultants at Carpenter Lab at the end of the week in which they were returned in sections.
  • Look here if you wish to request a regrade.

    Back to Top


    Partners
    We encourage you to work with a partner on the programming projects. (Why, or why not? Look here.)
    If you work with a partner, you must adhere to the following rules:
  • You can have only one partner for each project.
  • You cannot have different partners for different parts of the project.
  • You can pick a different partner for each project.
  • You and your partner receive the same correctness and style grade for the entire project.
  • You and your partner may attend different sections.
  • You must submit only one project with both your names, IDs, signatures, and section information, as specified in the Submission Rules.
  • You cannot take your exams with a partner.
  • You should avoid "divorcing" partners before submitting your project. Why? What if your partner submits a duplicate version of your programs? All the graders will see is an academic violation, so be careful.
  • If you have any questions, please do not hesitate to ask the staff.

    Back to Top


    Academic Integrity
    Respect academic integrity! Please review the Code and notes for CS100 here.

    Back to Top


    Back to CS100J Home