CSc212 Assignment 2 – Spring 2023

Computer Science City College of New York
  CSc21200 Data Structures, Spring 2023

Programming Assignment 2:

Implement and Test the sequence Class Using a Fixed-Sized Array (Chapter 3)

Modified from projects of Chapter  3  at
of Data Structures and Other Objects Using C++  by Michael Main and Walter Savitch

  • The Assignment: You will implement and test the sequence class using an array to store the sequence’s items.
  • Purposes: Ensure that you can write a small class that uses an array as a private member variable.Familiarize yourself with the sequence container class (which may also be part of future assignments).Give us a chance to evaluate your programming skills on a small class.
  • Before Starting: Read all of Chapter 3.
  • Due Date: Thursday, Feb 16, 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 sequence_exam.cxx (see below). Please don’t send your excutable files. Please submit your files to, with the subject line “CSc212 Assignment 2“.
  • 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 and turn in:

  1. sequence1.h: The header file for the sequence 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. Also, decide on appropriate private member variables, an declare these in the sequence class definition at the bottom o the header file If some of your member functions are implemented as inline functions, then you may put those implementations in this file too.
  2. sequence1.cxx: The implementation file for this first sequence class. You will write all of this file, which will have the implementations of all the sequence’s member functions.

Other files that you may find helpful:

  1. sequence_test.cxx: A simple interactive test program.
  2. sequence_exam.cxx: A non-interactive test program that will be used to grade the correctness of your sequence class.

The sequence Class Using a Fixed-Sized Array
Discussion of the Assignment

Many of the features of this class are similar to the bag class from Section 3.1, so start by thoroughly reading Section 3.1 and pay attention to new features such as static constant members and the use of a typedef. The sequence class itself is discussed in Section 3.2 of the class text. Notice how the sequence differs from a bag (see page 119). The interactive test program sequence_exam.cxx  is discussed in Section 3.3 of the class text.

Start by declaring the sequence’s private member variables in sequence.h. Then write the invariant of your ADT at the top of sequence1.cxx. The invariant describes precisely how all of your private member variables are used. All of the member functions (except for the constructor) may count on the invariant being true when the member function is activated. And all of the member functions are responsible for ensuring that the invariant is true when the function returns.

As always, do your work in small pieces. For example, my first version of the sequence had only a constructor, start, insert, advance, and current. My other member functions started out as stubs.

Use the interactive test program and a debugger to track down errors in your implementation. If you have an error, do not start making changes until you have identified the cause of the error.

The ability to initialize and use a static member constant within the class definition is a relatively new feature. If you have an older compiler that does not support static const members, then you may use

enum {CAPACITY = 30};

instead of

static const size_type CAPACITY = 30;

After  this definition, the name bag::CAPACITY is defined to have the integer value 30. Although this is not the intended use of an enum definition, the result is the same as using a static member constant.