CPSC 480-010 Software Engineering (SE) Fall 2025

Week 13 Class 25 Thu Nov 20 Posted: Nov 20

Announcements

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

• Project 4: Streaming Not going to show on the main page. There will always be a link in the Class Meeting, and it is in the Archive. The link to the refactorings to perform now works.

• Exercise 63: Team Streaming Meeting I Feedback

  Make sure to read over the feedback and fix anything noted. E.g., problems with issue titles, missing descriptions, vague issues.

• Guide: Development Environment - Tools

• Reminder

  This is a reminder that software engineering is about process, a process that leads to software that meets the actual requirements on time and within budget. Part of that overall process at a smaller level is workflow.

  In every workflow, we want to validate that what we have is correct. This means that as we implement:

  • Code compiles and builds
  • Code passes any tests
  • Code follows programming standards, e.g., indentation, overall formats, comments, design

  we want to validate each of these. Compiling and building are required to work on the code. Passing tests is automated, except for program behavior that we cannot easily test. E.g., output of error messages. Note that we do have to perform the tests. Following programming standards is not as easy to validate, so we expect the software engineer to follow these standards and reasonably attempt to verify this.

  While we may have code locally with these problems, we must ensure everything is correct when we commit.

  However, I often get:

  • Code that does not compile or build
  • Code that does not pass tests
  • Build directories in the repository
  • Poor commit messages
  • Incorrectly indented code
  • URLs that are not valid for the assignment

  I have no access to what you do locally as you implement. However, I, and your entire team, has access to what you commit.

  So, in all cases, validate before you commit. And validate that the central repository at GitHub has the commits that you think you made.

Class

• Exercise 64: HFSD Chapter 11 Crossword
• Notes: Software Engineering Paradigms
• Exercise 62: Software Engineering Paradigms I Crossword
• Notes: Waterfall Software Process Models

• Exercise 65: Team Streaming Meeting II

  During this team meeting you will:

  • Verify that you have built and run the tests
  • Make at least one commit to a branch of a test issue. This must be a new test case. Note that you can adjust the test case later, but make sure to get that commit in.

  Build and run the current tests for the Streaming project. This must include the following:

  • Clone the repository and move to the repo directory (Not required if already cloned or using GitHub Codespaces)
  • Create the build directory - If you already have a build directory, delete it first
  • Move to the build directory
  • Create the build using cmake
  • Build the project using make
  • Running the program with the demo make run
  • Running the test program make test

  To demonstrate this, you will record a terminal session using asciinema. Remember that asciinema is already installed in the GitHub Codespaces image, and easily installed elsewhere.

  A reminder on how to use asciinema:

  At the end of the terminal session, asciinema will show a URL. Anybody can use this URL to view the session. This is what you will submit for the exercise to the link in the exercise title. The URL should not contain "connect" or be a local file.

  To verify that it is correct, give the URL to another team member and have them verify it.

  An incorrect URL will receive a 0 on the exercise.

Unless stated otherwise, all exercises are due by 3 pm on Fri Nov 21