CSC 2210, SPA 3: MeetingUp++

Description

This assignment will give you experience with implementing a class in C++.

Possibly motivated by the CREATE institute at MSOE, you have decided to build a general-purpose match-making application that takes the names of two groups of students and uses an algorithm to determine perfect matches for any activity from tandem kayaking to catching a musical at the Performing Arts Center. Unfortunately, you failed to realize the effort required to build a matching application and decide to use a trivial method: two students match if their names have a letter in common or they have the same day of birth. You are going to write C++ classes to solve your problem. This is an individual assignment.

This has been broken into steps with the idea that you can just start on the first step without reading the full writeup. But feel free to read it through if you want!

Stage 1: Getting your code to compile

1. First, set up a project in CLion:
   1. Open CLion and select New Project...
   2. Select C++ Executable, make sure the language standard is C++17 or later, and set the location
   3. Copy main.cpp into the folder. This will overwrite the old main.cpp with the new version.
   4. Create pool.h, pool.cpp, and add pool.cpp (but not pool.h) to the project. Do this by right clicking on the .cpp file and select Add filename to CMake Project
   5. Build - this will fail because you do not have any code in the new files yet.
2. Next, put two classes into pool.h: Student and Pool. For now, put no data in the classes.
3. Add constructors to Student. You will need to be able to create a Student object with just a string (the student's name) and also with both a string and an integer (the day of birth). You can use default arguments if you like - you will refine these below.
4. In addition, add prototypes for the following Student methods:
   • A method printableDescription which takes no arguments and returns a string.
   • A method matches which takes a pointer to a Student object and returns a boolean value.
     Warning: use *, not & to declare a pointer; declaring a reference instead will create problems throughout the assignment.
5. CLion users may see wavy yellow lines at this point. This is typically due to the CLang-Tidy assistant, which might produce good advice to professionals but produces very bad advice to students in this class. If you have not turned it off yet, visit exercise 1 to see how to turn off this assistant.
6. Add constructors to Pool. There needs to be a constructor with no arguments and a constructor with a string argument (representing a student's name) and an optional integer argument (representing the day of the month the student was born). The integer argument defaults to 0.
7. Add prototypes for the following Pool methods:
   • A void method add that takes a string as an argument.
   • A void method add that takes a string and an integer as arguments. You could combine this with the previous one and use default values.
   • A void method readStudents that takes no arguments.
   • A void method printMatches that takes a Student pointer as an argument.
   • A void method printMatches that takes a Pool pointer as an argument.
   • An empty method that takes no arguments and returns a boolean value.
8. Ensure there are no syntax errors. The code will not build because you have not yet defined the Student and Pool methods, but main.cpp should have no errors in it. You will likely need to include additional library code and make other changes. You should not change main.cpp.
9. Uncomment the second #include for pool.h in main.cpp. This will break the build. Fix it by adding the appropriate "#ifndef magic" to pool.h. See the phonebook project for an example.
10. Add implementation stubs for Student and Pool to pool.cpp. A stub is either an empty body or a body that returns a constant result (for example, always returns true).
11. Fix the project so it builds without errors. It will not do anything useful at this point, but you will have solved all of the key OO problems at this point and not be too far from getting things to work. You can get 20% credit for meeting just this goal.

Stage 2: Reading Data

Add code to read all data. This will require adding private data in the class definitions (in pool.h) and appropriate implementations in pool.cpp.

1. Implement Student so it holds a name and the day of the month the student was born. The day will be between 0 and 31 with 0 meaning "no information".
2. Implement the Student constructors. The constructor which takes arguments initializes the pool to contain a student with that name and day. Recall the day defaults to 0.
3. Implement printableDescription to return the name. If the day number is greater than 0, follow this by " born on day X" where X is the day number. Use std::to_string to convert the number into a string.
4. Implement matches to return true if the birth day numbers are both greater than 0 and they match or any character in one of the names is also in the other student's name (ignoring underscores).
5. Get this code to compile and build.
6. Add an array of student pointers to Pool. The array must allow up to 20 students. You will also need a counter of the actual number of students in the pool. Note: this must use regular arrays; no vector or similar container classes.
7. Implement the constructor with no arguments so it creates an empty pool.
8. Implement the constructor with the string and integer arguments to create a pool with one student in it.
9. Implement the add methods to create Student objects and add them to the pool.
10. Implement readStudents so it reads student names and birth days from standard input until either end-of-file is reached or the text "END" is read; note that names are written as single words with '_' used to separate parts of the name. Assume each name is followed by an integer, and read that integer as the birth day. You do not have to test for the birth day being out of range. Each of the first 20 students is to be added to the pool. You can assume that if there is a name in the input, it is followed by an integer. This includes the word END. See input1.txt for an example.
11. If readStudents finds more than 20 students before "END", ignore the additional students. That is, continue to read students until you reach END, but do not add them too the pool.
12. You can assume that if two students have the same name, they are still unique (even if their birth dates also the same). That is, there will be two Student objects in the pool with the same name.
13. Get this code to build.
14. Run your program on input1.txt. It will not do anything at this point, but it should at least run without crashing. See the directions from assignment 1 to set your run configuration to read from the file.

Stage 3: Printing Matches

This stage will lead you through printing matches for simple cases. More complex cases will be handled in later stages.

1. Implement empty to return the appropriate result.
2. Implement the version of printMatches that takes a Student argument and cycles through the whole pool, printing

           A perfect match for X: Y
   

   (where X is the name passed to printMatches and Y is a name in the pool) for each matching student. The rules for whether two students match are given below. When printing names, print a space instead of an underscore. This likely means changing printDescription to handle underscores. You might find it handy to create a printable version of the name and/or description as private data in Student.
3. Implement the second version of printMatches so it prints all matches between this and the second pool. Process the students in the current object (the one pointed to by this) in the order they are in the array, and for each one call printMatches on the second pool.

The order is a bit challenging to explain. The simple solution will be to take your best guess and use esubmit to adjust the order to match ours later.

When matching names,

• ignore '_' (underscore) when matching. For example, "a_men" and "y_xi" would not match.
• Allow matches anywhere in the name — "john" and "rebecah" do match on the h's.
• Ignore case — "John" and "jude" match on 'J' and 'j'.

Note your main is configured so if the first name is TEST, the program runs simple tests and exits without processing any additional input. You can use this to do some basic testing at the start.

Constraints

These should be satisfied by doing the above, but just in case...

• You will complete two files: pool.h and pool.cpp. All code you write will be in one of these two files.
• The classes will be defined in pool.h.
• You must add method documentation in pool.h for all Pool methods. The Student class is simple enough that additional documentation is not likely to be helpful.
• Implementations of all constructors and methods must be in pool.cpp.
• Since the goal of this assignment is to give you experience with built-in arrays, declare any arrays using [] rather than some container class such as std::vector. For instance, if your code has an array of integers, declare it as

          constexpr int MAX_NUMBERS = 100;
          int numbers[MAX_NUMBERS];
  

• You must use std::string (which you can write as string if you write using namespace std;) to store names.
• Do not add public data to either classes; all data must be private.
• Use pointers for all Student and Pool objects (since they have "identity"), but you do not need to use pointers for string values.
• Follow the DRY principle: do not repeat yourself. If there is a method that is doing an operation, do not repeat the code for the operation in another method. For example, consider calling the add method from readStudents.
• Do not use <algorithm> in your solution. (Most students would never be tempted, but it is easy to find code suggesting using this library online. However, we want you to do this lab using more standard programming techniques.)
• Do not add public methods to class Pool other than the methods discussed above. Likewise, do not add additional constructors except the one mentioned here. You can add private or protected methods.

Other Notes

• Note that your solution will probably use newer features of C++, so if your compiler defaults to a newer version then add the -std=c++17 option when building.
• The input files typically have a list of names followed by END followed by another list of names. main creates two pools, calling readStudents for both, so the first END marks the division between the pools.
• Given std::string x; and cin >> x;
x will be the next "word", a sequence of characters ending with a space or newline. You will not need to remove any trailing newlines.
• You will likely find the functions tolower and/or toupper useful for this assignment. The code

          char c;
          cin >> c;
          cout << toupper(c);
  

  will read any type of character and print it out. If it is any non-letter, it will print the character unchanged. If it is a letter, it will print the uppercase form of the letter. You can use these in a loop to convert all of the letters in a string to either upper or lower case.
• Do not use reference parameters in this assignment. A single & should not appear in pool.h or pool.cpp. Note you may need a double && when doing a logical and, but you will not need & to pass reference variables.
• If you wish, you can add const to the appropriate methods and parameters, but this is not required and will not change your score.
• You do not need to worry about memory management for this assignment. That is, you do not need to use delete.
• Do not change main.cpp.

Submitting

• Submit your solution to match3 on esubmit. Submit your pool.cpp as "Main" and pool.h as an extra file - esubmit will automatically compile the provided main.cpp and it will include your code.
  • Remember: do not submit files that esubmit already has! In particular, do not submit main.cpp for this assignment..
• Ensure your code meets the coding standard, including the banner comment for the file, documenting the methods as directed above, using named constants for any arbitrary values like the sizes of the arrays, and ensuring there are no compilation warnings.
• If requested by your instructor, answer the reflection questions in Canvas.

Sample Files

This is not a complete list.

• input1.txt generates output1.txt
• input2.txt generates output2.txt - the input is essentially ignored in this case because the "TEST" runs all of the test code.
• input3.txt generates output3.txt
• input4.txt generates output4.txt
• input5.txt generates output5.txt
• input6.txt generates output6.txt
• input7.txt generates output7.txt
• input8.txt generates output8.txt
• input9.txt generates output9.txt