CSc 212 Assignment 1- Spring 2023
Computer Science City College of New York
CSc 21200 Data Structures, Spring 2023
Programming Assignment 1 – Implement and Test the Statistician Class
- The Assignment: You will implement and test a small class called statistician, which is similar to some of the small classes in Chapter 2 of the text.
- Purposes:Ensure that you can write a small class that meets a precise specification.Make sure you understand how to write a class that is separated into a header file and an implementation file. Give you experience in using a test program to track down bugs in a class’s implementation.
- Before Starting: Read all of Chapter 2. Know how to compile and run C++ programs on your system (Unix or Windows).
- Due Date: Thursday, Feb 09, 2023 before midnight. If you have problems, late work will be accepted before Friday with no penalties. Late work may be submitted on Saturday or Sunday with 5% penalty per day. No work will be accepted after Sunday.
- How to Turn In: Files to be submitted: source code (*.cpp, *.cxx, *.h) and the text file (a *.txt file or *.pdf file) showing the running output result of your implementation with the non-interactive test program statsexam.cxx (see below). Please don’t send your executable files. Please submit your files to firstname.lastname@example.org, with the subject line “CSc212 Assignment 1“.
- Integrity Policy: Please don’t forget to write your name and ID (last four digits) on top of each of your files (see below for files you need to turn in). Then under your name, please write this statement: “The work in this assignment is my own. Any outside sources have been properly cited.” Without writing this statement, you will not be able to get any score.
Files that you must write or generate:
- stats.h: The header file for the new statistician class. Actually, you don’t have to write much of this file. Just start with our version and add your name and other information at the top. If some of your member functions are implemented as inline functions, then you may put those implementations in this file too.
- stats.cxx: The implementation file for the new statistician class. You will write all of this file, which will have the implementations of all the statistician’s member functions.
- A text file (a *.txt file or *.pdf file) showing the running output result of your implementation with the non-interactive test program statsexam.cxx (see below).
Other files that you may find helpful: You shall compile one of the following files with your stats.cxx and link them to generate your executable:
- stattest.cxx: A simple interactive test program for you to test your implementations.
- statexam.cxx: A non-interactive test program that will be used to grade the correctness of your statistician class.
The Statistician Class
Discussion of the Assignment
As indicated above, you will implement a new class called statistician, using a header file (most of which is written for you) and an implementation file (which you will write by yourself). The statistician is a class that is designed to keep track of simple statistics about a sequence of real numbers. There are two member functions that you should understand at an informal level before you proceed any further. The prototypes for these two functions are shown here as part of the statistician class declaration:
void next(double r);
double mean( ) const;
The member function “next” is used to give a sequence of numbers to the statistician one at a time. The member function “mean” is a constant member function that returns the arithmetic mean (i.e., the average) of all the numbers that have been given to the statistician.
Example: Suppose that you want a statistician to compute the mean of the sequence 1.1, 2.8, -0.9. Then you could write these statements:
// Declares a statistician object called s
// Give the three numbers 1.1, 2.8 and -0.9 to the statistician
// Call the mean function, and print the result followed by a carriage return
cout << s.mean( ) << endl;
The output statement will print 1.0, since 1.0 is the mean of the three numbers 1.1, 2.8 and -0.9.
Once you understand the workings of the next and mean member functions, you can look at the complete specification of the statistician class, which is in the file stats.h . Notice that the statistician class in this file is part of a namespace called main_savitch_2C. You should use this namespace for your statistician. In this file you will find a precondition/postcondition contract for all the statistician’s member functions, including:
- A default constructor, which merely does any initialization needed for the statistician to start its work
- The next and mean functions, described above
- A constant member function called length, which returns the count of how many numbers have been given to the statistician
- Two constant member functions called minimum and maximum, which return the smallest and largest numbers that have been given to the statistician. (By the way, these two functions and the mean function all have a precondition that requires length( ) > 0. You cannot use these three member functions unless the statistician has been given at least one number!)
- A constant member function called sum, which returns the sum of all the numbers that have been given to the statistician. This function does NOT have a precondition. It may be called even if the statistician has NO numbers (in which case it should return 0).
- An overloaded operator == which tests to see whether two statisticians are “equal”. The prototype is:
- s.length( ) and t.length( ) are both 4
- s.mean( ) and t.mean( ) are both 2.5
- s.sum( ) and t.sum( ) are both 10.0
- s.minimum( ) and t.minimum are both 1
- s.maximum( ) and t.maximum are both 4
- An overloaded + operator which has two statisticians as arguments, and returns a third statistician, as shown in this prototype:
- An overloaded * operator which allows you to “multiply” a double number times a statistician. Here is the prototype:
Hints and Frequently Asked Questions
The Private Member Variables
Carefully read the class definition in stats.h. Notice how the private member variables are being used to keep track of information about the statistician’s sequence of numbers. The statistician does NOT keep track of all the numbers in the sequence. There is no need to do so, and trying to do so can get you into trouble. Instead, it keeps track of only the information that is relevant to its member functions: How many numbers have been seen? What is the sum of those numbers? If you have seen at least one number, then what are the smallest and largest numbers that you’ve seen so far? These four items should be your only private member variables.Be careful about how you set the private member variable that keeps track of the smallest number. My suggestion is that you do NOT have the constructor initialize this member variable (because when the constructor does its work, there have not yet been any numbers, so there is no smallest number). But part of the work of the “next” function is to correctly maintain the private member variables. This means that the first time that the next function is called, it should set the private member variable that keeps track of smallest values. Later, if next is called again with a smaller number, then the next function will change the member variable that is keeping track of the smallest value. (You’ll have a similar process for the member variable that’s keeping track of the largest value).
Check Boundary Values
Make sure that your + and * operators work correctly when the arguments are statisticians with no numbers.
Your implementations should use the assert function to check preconditions of all functions.
Input and Output
Your implementations must NOT produce any output to cout, nor expect any input from cin. All the interaction with the member functions occurs through their parameters.
Implement and Test Small Pieces
Don’t tackle to whole project at once. Start by implementing what you can, using “stubs” for the harder functions. A “stub” is the implementation of a function with the lines of the body omitted. For example:
void statistician::next(double r)
// This is just a stub, to be implemented later.
A first implementation might have only:
- The constructor
- A simple version of next that increments the private member variable to keep track of how many numbers have been seen
- The length function
Even with just stubs, your stats.cxx file will correctly compile and link with the interactive test program, stattest.cxx. For example, if you are using the g++ compiler with Linux in our student labs, you would compile and link the stattest program with these three commands:
g++ -Wall -c stats.cxx
g++ -Wall -c stattest.cxx
g++ stattest.o stats.o -o stattest
Frequently Asked Questions
1. I run the stattest (or statexam) and the program crashes with a failed assertion. Is it a good idea to remove the assertions (which I put in stats.cxx to check preconditions).
ANSWER: No, leave those preconditions in there! The TA will clobber you (and I will too) if you delete the checks of the preconditions. Instead, you must find out where one of your functions is violating a precondition. Here is a typical example: Some students started by implementing the operator == along these lines:
bool operator == (const statistician& s1, const statistician& s2)
(s1.length( ) == s2.length( ))
(s1.sum( ) == s2.sum( ))
(s1.minimum( ) == s2.minimum( ))
(s1.maximum( ) == s2.maximum( ));
The problem with this implementation is that the operator == is allowed to be called even if s1 or s2 or both are empty. In such a case, the function will eventually get down to the test (s1.minimum( ) == s2.minimum( )) and…assertion failed! because you cannot call minimum for an empty statistician.
How do you fix this problem? In your operator == you should start with a test to see whether s1 or s2 is empty (and handle those cases in a way that does not call minimum() or maximum() ).
MORAL: The functions you write can call other functions, but they must be careful to not violate preconditions.
2. How should my constructor initialize the private member variables tiniest and largest?
ANSWER: There are several solutions. One idea is to not initialize them at all. In this case, you must be careful to make sure of two things: (A) When the first number is given to the next function, it puts that first number into both tiniest and largest. (B) None of the other functions ever try to use tiniest or largest for an empty statistician.
3. What other functions might need special cases for an empty statistician?
ANSWER: Well, any function that accesses tiniest, largest, minimum() or maximum() probably needs a special case. Sometimes the special case can be simple. For example, the start of my operator + has two special cases:
if (s1.length( ) == 0)
if (s2.length( ) == 0)
…now the rest of my code doesn’t need to worry about s1 or s2 being empty.
4. What strange things happen in the operator * when the scalar is negative?
ANSWER: Here’s an example: Suppose that a statistician x has been given three numbers 10, 20 and 40, where y.minimum() will be 10 and y.maximum() will be 40. Then we execute the statement y = -1*x; The statistician y must act as if it had been given -10, -20 and -40 so y.minimum() will be -40 and y.maximum() will be -10.
5. I’m having trouble compiling or linking my stats.cxx with statexam.cxx or stattest.cxx
ANSWER: Make sure that all the code in your stats.cxx is in the namespace main_savitch_2C (look at the similar example of the point class on page 62). If you still have the compilation problem, send email to your TA for help. When you send messages for the Data Structures course, always remeber to include “CSC212” in your Subject line otherwise your messages could be ignored.
6. When I write a friend function, the compiler still won’t let the function access the private member variables of the statistician. Help!
ANSWER: See the the answer to the previous question.
7. Should I worry about warnings that occur when I compile.
ANSWER: Yes. At this point of the game, about 60% of warnings are errors. In any case, the TAs will beat you up if your code generates any warnings. Spotting the cause of the warnings is an important part of learning about C++.
8. Should I worry about putting lots of comments in my program.
ANSWER: Not much of that is needed until a function gets longer than 10-15 lines.
9. What causes these compilation errors:
// Problem 1:
s1.length( ) = s2.length( ) + s3.length( );
// You can’t assign to a function such as length. Try assigning to
// s1.sum (the variable) instead.
// Problem 2:
if (s1.length == s2.length)
// You have to call the function. Try (s1.length() == s2.length()).