CPSC 480-010 Software Engineering (SE) Fall 2025

Week 8 Class 15 Tue Oct 14 Posted: Oct 14

After Class

• Project 2 Feedback on your calculations is in Brightspace. This is not the entire grade or feedback that we will provide later. If your feedback was not "Iteration capacity calculation appears correct", I strongly suggest that you figure out what is wrong before the Midterm Exam. You are not allowed to exceed the iteration capacity.

Announcements

• Office Hours For today, Office Hours are 10:30 - 10:45 am and 3:15 - 4:15 pm

• Project 2 The checkmd required a file called Requirements.md. To use this with IterationPlan.md, we needed to remove this restriction from checkmd.

  This changed checkmd is now in the image mlcollard/checkmd, which you get when you run a GitHub Codespace. If you have an existing GitHub Codespace for Project 2, you will have to create a new codespace to get this change.

• Project 2 Keep in mind the following:

  • Each plan includes all user stories
  • Carefully check your calculations, including the numbers you are using
  • The unit of granularity for an iteration plan is an iteration, not day-by-day
  • Do not assign work to each developer
• Project 2 Grading I will post some type of preliminary feedback on your plans by end-of-day on Wednesday. See the "After Class" on Wednesday for details.
• Midterm Exam

• Exercise 33: Team Text Match

  In your repository the branch feedback in the file Feedback.md is a Claude (LLM) analysis of the team history for Exercise 33: Team Text Match. I suggest viewing it at GitHub.

  Some observations regarding team collaboration and outcomes:

  • All team members should have a basic understanding of the technology used. In this case, for building programs: compiling, linking, options, etc. For Make, how to write rules. Some research might be needed, and while some team members may know more about particular points than others, everyone must have a fundamental understanding.
  • All changes must be verified by any means necessary. Many commits included modifications that would cause an error when make is run. Not every team member did this.
  • It was necessary to coordinate who was doing what. The team was in person at the same time, so this should have been straightforward. Consider what would happen if the team were distributed across different work schedules.
  • Allowing the team to only work on the program sequentially wastes ^(n-1)/_n of the potential. There was no reason why the two executables, textmatch and regexCountTest, couldn't be worked on in parallel. Declarative languages are easier to work on independently than other types of languages due to simpler structures. E.g., make is easier to work on independently than C++.
  • The team cannot afford even one member who makes unverified commits, submits changes that aren't aligned with other work, or has limited foundational knowledge.

Class

• Make Prerequisites

  Makefile

  Make prerequisite graph for srcComplexity:

  

• HFSD Chapter 7

• Exercise 34: Team Text Match II

  • build-files-010
  • GNU Make
  • Make Rule Introduction What a rule looks like
  • Automatic Variables including $@, $<, and $^