CPSC 421-020 Object-Oriented Programming (OOP) Spring 2026

Week 12 Class 19 Thu Apr 02 Posted: Apr 02

Announcements

Office Hours My Office Hours on Thursday, Apr 2 are from 12:45 - 2 pm.
Project 2 Scores and feedback for the Class Diagram are posted in Brightspace. If you want to make changes in Project 3 to the Class Diagram, go ahead and do so. I will grade the most recent version. I also gave a total grade for Project 2, and the part scores now do not add to the final score (only the overall score).
Exercise 64: Names The UML Class Diagram shows the class Name with attributes that are single-value optionals.

Convert the class Name in the source code to use std::optional<std:string> instead of the pair of std::string and a boolean flag. The link for GitHub Classroom is in Brightspace.

Due by 4 pm on Fri, Apr 3.

Reminder The type String in a UML Class Diagram does not necesarily map to a std::string in a C++ program. It could map to a std::string_view, an optional std::string, or even a c-string. Which source-code type a UML type maps to is part of the code implementation, and not part of the model.

Exercise 64: Names Some of the already-submitted Names have some issues:
- Dereference without checking (even those some of the Constructors do not provide parts of the name)
- Assuming that a call to first() should return an empty string

Agenda

Notes: UML Generalization
Exercise 67: UML Generalization Crossword
Notes: Design Patterns
Exercise 68: Design Patterns Crossword
Notes: Dispatch
Exercise 69: Static Dispatch Worksheet
Exercise 70: Dispatch Crossword
Exercise 71: Static Dispatch

The repository Base has a set of various method call situations, and a way at run time (using assert()) to verify which method is actually called. Each assertion needs to have one of the following done:
- If the call is performed using static dispatch then complete the assert() in the code that indicates (via a string) which method is called, e.g., for m1() is it "Base::m1()", "Derived::m1()", or "DerivedDerived::m1()"?
- If the call is performed using dynamic dispatch then do not fill in the answer for the call, but instead comment out the assert(), e.g.,
Handle each assertion one at a time in order, compiling and running the program (i.e., make run) after each assertion is completed. The assertion you edited should pass, and you should be onto the next assertion.

You are required to separately commit for each block of statements in the main program.
- All asserts involving static dispatch must be filled in correctly
- All asserts involving dynamic dispatch must be commented out
The GitHub Classroom Invitation Link for Base is in Brightspace.
Notes: VTables

Unless otherwise noted, exercises are due by 4 pm on Mon, Apr 6