CPSC 480-010 Software Engineering (SE) Fall 2024

Week 4 Class 8 Thu Sep 19 Posted: Sep 19

After Class

• Project 1 Include all user stories, even those without estimates. If a user story does not have an estimate, leave the estimate value blank.

Announcements

• Engineering, Engineering Technology, and Computing Career Fair Looking for student volunteers, Resume Workshop

• Resume

  If you bring a printed copy of your resume to me during my Office Hours on Thursday, September 19, I can review it and provide suggestions for improvement.

• Project 1: Requirements Report

  • Project 1 is not a team project. They only thing that you share with your team is the user story cards. Everything else originates from you. Do not set a team template for this.
  • This is a report about the team results and process, not your individual results and process.
  • The first two sections will be shown to the customer. Those sections should only contain information the customer is allowed to see. You will lose a significant number of points if you do not follow this rule.
  • All user stories belong to the team. This is a report of the current state of your team project.
  • There is no "my user story". All user stories belong to the team, actually the customer.
  • The customer is not interested in tasks, only the user stories.
  • The report should be readable and consistent both in markdown and displayed as a web page at GitHub.
• Exercise 16: Commit to Project 1 Repository I did not mention this in one of the sections, so I will extend the due date to after the next class.
• Project 1 asciinema session I added the link for submitting your asciinema session

Class

• Exercise 16: Commit to Project 1 Repository

  Following the procedure given in the assignment and demonstrated in class, contribute at least one commit to the Project 1 repository. This must be a valid and useful commit.

  • Use the git CLI to make the commit. You can do this wherever you have the repository cloned. You can even do this in a GitHub Codespace
  • Good commit messages follow certain patterns, and you need to follow them on all git commits:
    • Start with an action, e.g., Add
    • Capitalize the subject line (the only line we are using)
    • Use the imperative mood, e.g., Added, Adding, Adds, Add
    • Do not end the subject line with a period

  You can see your commit messages with the git log command.

• HFSD Chapter 4
• Exercise 17: HFSD Chapter 4 Crossword Due after next class meeting
• Exercise 18: Team User Story Estimates II

Unless stated otherwise, all exercises are due by 3 pm on Fri Sep 20