CPSC 480-020 Software Engineering (SE) Fall 2026

Week 11 Class 22 Thu Nov 05 Posted: Nov 05

Announcements

• Exercise 49: Project 3 Feedback 2 Check for two rules implemented.

  Overall observations:

  • if-statements that do not follow the coding style
  • Violations of the one call to addAttribute() per attribute, e.g., only one call to addAttribute("filename", /* ... */).
  • Number of if-statements more than the number of rules
  • Unnecessary else's
  • Inconsistent identation that does not follow the coding style

Class

• HFSD Chapter 9
• Exercise 50: HFSD Chapter 9 Crossword
• Notes: Refactoring

• Exercise 51: Team Mock Clock III

  In this course, we try to balance two goals: helping you learn the concepts clearly and giving you experience with how real software development is done. In this exercise, some parts are designed to feel closer to real-world practice:

  • Instead of being told exactly what change to make, the required change is written up as an issue—just like it would be in a real project.
  • Your commit messages do not include which approach you are using (dip or mock); they focus only on the change itself.
  • The updates to the CMake build system are provided as a pull request, and you review and work with it like you would on a real team.

  Other parts of the exercise are included mainly for learning purposes:

  • You use two separate branches (dip and mock) to explore different approaches. In an actual project, you would pick one of these approaches and use it on a single branck that is not named after the approach.
  • In real development, you would create a feature branch for the issue and submit a pull request to merge your work into main. For the exercise, the structure is simplified so you can focus on the concepts.

Unless stated otherwise, all exercises are due by 4 pm on Fri Nov 06