CPSC 480-020 Software Engineering (SE) Fall 2024

Week 4 Class 7 Tue Sep 17 Posted: Sep 17

After Class

• Exercise 15: Team User Stories III If you participated in the team meeting, but were not able to fill out the form or upload a photo of your coded potential user story titles due to a technical error, then send me an email.
• 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.

Announcements:

• Resume

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

• Individual Posts Small web improvements
• Project 1 GitHub Classroom I added gh to the image. Create a new codespace if you need it and it is not there.

• Windows File Explorer & WSL

  To open the Windows File Explorer on the current directory in WSL:

  If you open a path it has to be in Linux format, e.g., C:\Users\JohnDoe\Documents would be /mnt/c/Users/JohnDoe/Documents.

• Dependencies

  I see a lot of user story estimates where the assumptions include the completion of a previous user story. This is a dependency. Avoid dependencies at all costs. For example, Add … does not have to be completed before Delete …. Obviously there will be some dependencies, but they are to be at the user-story level, not the implementation level.

• Estimates

  • Estimation in software development is not about finding the minimum time it would take you to complete a user story. It's about understanding and predicting the genuine effort required in the context of your regular 5-day workweek and 50 weeks of work in a year. Remember, an estimate is not a speed challenge but rather a measure of how long it will realistically take to thoroughly implement a user story.
  • Avoid the trap of only considering the quickest or simplest implementation. Proper estimation requires thoughtful consideration of all possible complexities. Moreover, completing a user story quickly doesn't mean the rest of the day is free; there's always another user story waiting. This is not a class assignment or a lab exercise where once you are finished you are done for the day.
  • Refrain from using phrases like "All we have to do…” when discussing software tasks. Such assumptions often oversimplify the complexities inherent in coding.
• Project 1: Requirements Report Change in due date

Class

• Creating the Report
• Git Commands

• 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 3
• Exercise 13: HFSD Chapter 3 Crossword
• HFSD Chapter 4
• Exercise 15: Team User Stories III

Unless stated otherwise, all exercises are due by 3 pm on Wed Sep 18