CPSC 480 Software Engineering (SE) Fall 2026

News

---

• Week 6 Class 12 Thu Oct 01 Posted: Oct 01

  Before Class

  • If you haven't already created the GitHub Classroom repository for "Build Files" you should do so before class. You can also set up a GitHub Codespace for the project, as it takes some time to start up initially and when restarting.

  • Exercise 25: Build Tools Background

    Please complete before class starts. There are no wrong answers, and not much to write.

  Announcements

  • Project 1 I will allow you to earn some points back by correcting what you submitted. To count:

    • Each item in the feedback must be in a separate commit
    • Each commit message must follow the guidelines we went over: 1) Start with an action, 2) Imperative form, 3) Use the one-line form, 4) Do not end in a period, and 5) Keep it a reasonable length.
    • If an error was made, then create an issue at GitHub in your repository
    • Due at 4 pm on Friday, Oct 2
  • Project 2: Iteration Plan
  • Post Page The main course page is getting quite long. A reminder that the title of each post is a link to a separate page of that post.
  • Version Control We have only covered a high-level view of version control. During the rest of the semester, we will cover it in much more detail as part of dedicated notes and the overall workflow.

  Class

  • Notes: Version Control
  • Exercise 23: Version Control Overview Crossword II Due by 4 pm on Fri Oct 2
  • HFSD 6.5

  • Make

    Build Files GitHub Organization Invitation Link - Create your own repository for this example (and future exercisese)

    • GNU Make
    • Make Rule Introduction What a rule looks like
    • Special Note: recipes are indented using a tab character, not spaces. Using spaces (or an editor that expands tabs to spaces) will result in an invalid Makefile.
    • Automatic Variables including $@, $<, and $^
    • NMake Microsoft's version of Make
    • srcML Playground Generate new srcML of source code, input format for srccomplexity

    build-files-f26-010 Example I will demonstrate with

  • Exercise 26: Makefile

    Code along and make the same commits with the same commit messages as I do in class.

    I suggest you use GitHub Codespaces as all necessary packages are installed.

    Remember that you can access my commits as I make them.

  • Exercise 27: HFSD Chapter 6.5 Crossword
  • Exercise 28: Team Iteration II

  Unless stated otherwise, all exercises are due by 4 pm on Mon Oct 05

• Project 2: Iteration Plan Posted: Oct 01

  Project 2 is due on Friday, Oct 9 at 11:59:59 pm. The GitHub Organization Project 2 Invitation.

  For Project 2, take all the user stories from Project 1 and create a series of iteration plans.

  Use the examples in the book to show which parts of the user story you should show in your iteration plan (e.g., do not restate descriptions in the plans). Also, clearly state the entire new iteration plan for each plan, not just the changes. However, make sure to thoroughly discuss what the change was and what effect it had.

  This is an individual project. Each member of a team has different user-story priorities. To get individual priorities for Project 2, select the number of user stories:

  User Stories:
  

  Put these in the Priority field in the order in which you listed the user stories. In the report, do not discuss how you generated your report's priorities, i.e., pretend that the customer gave them.

  The following plans may require you to add additional user stories. This violates our rule that only the development team can create estimates. However, as part of the exercise, put in an estimate.

  Each plan is a point in time. For each plan, show the entire iteration plan, including the iterations already completed.

  Plan	Events
  1	Create an initial iteration plan: 2 Weeks (14 calendar days) iteration, 2 developers, 0.6 velocity
  2	The customer adds two new user stories of the highest priority at the end of the first iteration. For the two new user stories, one is a new feature, and one is an emergency. Create a non-trivial estimate (i.e., an estimate that makes the planning interesting) for these new user stories.
  3	A user story with a non-trivial estimate takes twice as long. Assume this occurred right before the last iteration.
  4	At the beginning of the last iteration of your current plan, the other developer leaves for another project, and it is up to you to finish the project.

  After the plans, create a section with all of your user stories, including their titles, descriptions, estimates, and priorities. You will need estimates for all of your user stories.

• Exercise 28: Team Iteration II Posted: Oct 01

  Your team completed the first iteration. Despite inexperience with determining estimates, you did complete the all the planned user stories.

  For some of the remaining user stories, not part of the first iteration, the customer updated the priorities of 4 user stories. Get new priorities for these user stories:

  User Stories:
  

  Now, design a second iteration. Use the principles in the book to decide which of the remaining user stories belong in the second iteration.

  Individually, each team member will turn in to Brightspace notes with the following:

  • Details of the calculation of the capacity of the iteration, i.e., how many days of work can be accomplished
  • Set of user stories in the revised first iteration with title, estimate, and priority
  • Set of user stories in the second iteration with title, estimate, and priority
  • Any observations

  Do not assume any dependencies between user stories.

  The notes are due by the end of class. They can be a PDF (print to file from a computing device) or a JPG (picture taken via phone).

  If you finish early, work on real estimates for your user stories.

Archive