CSC 172
Homework 1
Assigned Jan. 28, due Feb. 11, to be done individually
- Fill out
the student survey on-line.
(You will not be graded on the answers, but you will be graded
on whether you do it or not.) Some of you may have filled out this
survey in a past semester; please fill it out again, as some of your
answers may have changed.
- Read through some of my Adages on Software
Design and Development.
Write a few sentences on your reactions --
points that you find particularly useful, points that contradict your
experience, points you don't understand at all, etc.
-
PSP recording:
- Before you start on the programming part of the assignment,
estimate how long the program will be and how long it'll take you to
write. Enter your estimates using the
PSP forms
(click on "Input" under "Product Plan Estimates").
-
While you work on the program,
keep track of all the error messages and other
defects you encounter
(click on "Input" under "Defect Removal Data").
(I recommend having a Web browser open while you work, so you can record
each defect as you find it, rather than trying to remember them all
later.)
-
While you work on the program, keep track of how much
time you spend on various phases of program development (click on
"Input" under "Time Management Data"). Again, I recommend recording
this stuff while you work rather than trying to reconstruct it after
the fact.
- The Programming Part:
Write a C++ program that takes in a sequence of numbers, separated
by white space, and computes and prints their average.
Your program will not be
told in advance how many numbers there will be; instead, the number 0
will indicate the end of the input.
Be sure to write down a good suite of test cases, with the corresponding
"correct" answers, before you write the program.
Turn these in as a separate file with the program.
-
How to turn this in:
The survey will be sent to me automatically when you click the "Submit"
button. The PSP records will also be available to me automatically, so
don't worry about them.
Run your program several times with different test data, logging the
output to a file.
Send me an e-mail, attaching this file
and your source code file(s).
The body of the e-mail should be the "few sentences about your
reactions" to the Adages page. You may also include commentary about
the process of getting this program to work.
Last modified:
Sun Jan 27 19:55:44 EST 2002
Stephen Bloch / sbloch@adelphi.edu