CPSC 480-020 Software Engineering (SE) Fall 2023

Week 13 Class 24 Thu Nov 30 Posted: Nov 30

Announcement Project 4: Streaming

• I did not include the GitHub Codespace configuration in the template used to create your repositories. This is in the file .devcontainer.json. I've since added it to all the branches of your repositories. Use a git pull before you do anything else in a branch. If you have a local branch you did not push, then push it immediately and let me know so I can update it. Any codespaces started before this change will have to be deleted.
• I see Waterfall approaches being used, e.g., trying to create all issues at the start, then examining all the code, then working on the issues. Create what issues you can easily see. Then, work on those issues by making commits. Do not have a special stage where you examine the code. You learn about code by working on code. And that means commits.
• The project explicitly states what to call the branch. Follow those instructions.
• I do not see many issue branches, with most projects having none. If you created the branch locally but have not pushed, do so immediately. Keep others in your project aware of what is happening in your branch by pushing often.
• This is not TDD. There is nothing to implement in terms of new features. The tests do not break the current implementation, but add tests so that the code's behavior will not change as you refactor.
• Reminder: Due Friday, Dec 15 at Noon

Class

• Notes: Software Evolution
• Exercise 59: Software Evolution Crossword
• Notes: Software Lifespan
• Exercise 60: Software Lifespan Crossword

• Exercise 61: Build Streaming

  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. It records the commands you enter and the output the command produces. asciinema is already installed in the GitHub Codespaces image. You can also install asciinema on Linux/WSL/macOS.

  asciinema is relatively straightforward to use.

  You can play, pause, skip, etc. You can also copy the commands as text. Note that the replay even includes your pauses and any delay as the command is run.

  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. Test your URL in a browser; an incorrect URL will receive a 0.

  The exercise is due by 3:30 pm on Fri Dec 01

• Exercise 62: Team Streaming Meeting III

  Have a "standup meeting" with your team. Go over:

  • What did you do previously?
  • What are you going to do next?
  • What (if anything) is holding you up?

  If a team member is going to do something next, make sure it is an issue and that they are assigned to it.

  Upload a text file, PNG, or PDF with a short paragraph describing what you discussed, and possibly accomplished, during your team meeting.

  This is due by the end of class.

Unless stated otherwise, all exercises are due by 3:30 pm on Monday, Dec 4.