Assignments CISC 1115

You are expected to submit:

1. Program listing(s).

2. Contents of input and output files.

3. Contents of output window.

4. Memory trace: a list of the variables in the program and the values they take on during the execution of the program. Pretend you are computer.

5. Handcheck: the calculation that a human would do to solve the problem. The program should not influence the handcheck. Once the program has been run, compare the handcheck result to the output. If they aren't the same, find the error and correct it. Pretend you have no computer.

Please include the following at top of the listing and the output:

· name

· class and section

· assignment number

· date due

· date submitted

· Description of what the program does (and how).

Programs must be

· complete

· correct

· in good style (indenting, aligned braces, meaningful identifiers, a comment for each method, including main())

· well documented (comments in programs, headings on tables and labels in output)

Add the “handwritten stuff” to your program as a big comment at the end.

Assignments will be emailed to the class list. Join the list! It can also be used to ask questions and have discussions.

Email your assignments to
nethw5@sci.brooklyn.cuny.edu or nethw6@sci.brooklyn.cuny.edu . You’ll be told which in class. Get it right.
Subject: submitting assignment assignment_number your_name
When you do this correctly, you will get an acknowledgement e-mail.
 

Doing the exercises before the assignment you hand in will ultimately save you time. Writing pseudocode will save time, too. Don’t try to get away with it.

If tutors (or friends) are writing (or running) your program, you are not learning how to do it. Ask for help when you are stuck but do not let anyone write any code for you or touch your machine.

Adding extra print statements may help you find errors. Feel free to learn how to use the debugger.

Do a written trace before coming to me or to a tutor with questions.

Save your work every 10-15 minutes.