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

Week 7 Class 12 Thu Feb 26 Posted: Feb 26

Auca Coyan Maillo [AddTest Invitation Link]: https://classroom50.org/UACPSC/cpsc-480-se-fall-2026/assignments/add-test/accept [first 5 chapters]: https://crascit.com/wp-content/uploads/2026/01/ProfessionalCMake_22nd_Edition_GettingStarted.pdf [Professional CMake: A Practical Guide]: https://crascit.com/professional-cmake/ [AddTest Invitation Link]: https://classroom50.org/UACPSC/cpsc-480-se-fall-2026/assignments/add-test/accept [first 5 chapters]: https://crascit.com/wp-content/uploads/2026/01/ProfessionalCMake_22nd_Edition_GettingStarted.pdf [Professional CMake: A Practical Guide]: https://crascit.com/professional-cmake/ [AddTest Invitation Link]: https://classroom50.org/UACPSC/cpsc-480-se-fall-2026/assignments/add-test/accept [add-test-f26-020]: https://github.com/UACPSC/add-test-f26-020 [Mock Clock Invitation Link]: https://classroom50.org/UACPSC/cpsc-480-se-fall-2026/assignments/mock-clock/accept [sort-tdd-f26-020]: https://github.com/UACPSC/sort-tdd-f26-020 [sortTDD Invitation Link]: https://classroom50.org/UACPSC/cpsc-480-se-fall-2026/assignments/sort-tdd/accept [Mock Clock Invitation Link]: https://classroom50.org/UACPSC/cpsc-480-se-fall-2026/assignments/mock-clock/accept

After Class

• Project 2 See the adjusted due dates

Announcements

• Midterm Exam
• Project 2
  • Guide: Coding Standard - Classes

• Exercise 37: Create a UML Class Diagram Scores in Brightspace. Common issues:

  • Invalid UML types
  • static operator
  • Missing type separator, i.e., :
  • Displays with commas, i.e., input is not separated by ; and may require to be on one line
  • School and process related comments, e.g., // Exercise ... and // Add ...

• Exercise 39: Utilities Scores and feedback in Brightspace. I took off for:

  • Objects passed by value instead of const reference, e.g., std::vector<int> v
  • Scalar values passed by const value, e.g., const int
  • Doxygen comments that are missing, incomplete, or contain errors
  • @TODOs that are incomplete or not completed
  • Poor naming

  Notes: Utilities Feedback

• Zero-Tolerance Policy

  The following are fundamental design choices at the C++ level that we have spent more than enough time on. To make sure the message is received, any violations of the following will receive a 0 on the exercise, project, or test question:

  • Passing std::string by value, e.g. void f(std::string);
  • Passing std::vector<> by value, e.g., void f(std::vector<int>);
  • Passing by const value, e.g., void f(const int n);

  For why we do not pass large objects by value, see the Benchmarks

Agenda

• Exercise 41: min min min In class

• Exercise 42: Utilities II

  If you received a non-zero score for Exercise 39: Utilities, your score on that exercise will be replaced by this score if this score is higher. So if you got a 7/10 on Exercise 30, and you get a 10/10 for Exercise 33, your Exercise 30 score will change to a 10/10.

  Using the feedback in class, improve your function declarations for the Utilities code. I suggest a commit for each change of a function name, e.g., Rename ..., and each change of a parameter type, e.g., Change ....

  Other changes to consider:

  • Make sure to correctly identify [in],[out], and [in/out]. I saw some [in/out] that is really [out]. If the previous contents of a parameter are not used in the function, and the parameter value is changed, it is an [out].
  • You can pass data out from a function via a parameter or the return value. Do not use both for the same data.
• Notes: Iterator
• Exercise 40: Iterator Crossword
• Notes: Cohesion
• Exercise 43: Cohesion Crossword

Unless otherwise noted, exercises are due by 4 pm on Fri Feb 27