CPSC 480-020 Software Engineering (SE) Fall 2026

Week 3 Class 5 Tue Sep 08 Posted: Sep 08

After Class

• Exercise 11: GitHub Username GitHub Classroom is no more. Instead, we are using Classroom 50. The process for allowing you to create a repository has changed and is as follows: 1) Add you to the UACPSC GitHub Organization, and 2) Add you to the roster for the course. To do so, I need your GitHub Username. If you don't provide it, you won't be able to do the projects and some exercises.

  The title of this exercise is a link to the form where you can enter your GitHub Username.

  I am posting this early since the deadline is earlier than normal. Due Friday, Sep 11 by 9 am.

Announcements:

• Team Exercises & Feedback Each team member gets individual feedback on the team exercises. This includes the work the team did as a whole, as well as your individual contributions. Feedback from the previous team exercise often relates to the current team exercise. Therefore, I am requiring you to view your feedback from the last team exercise via the Assignments page. Failure to do so will result in a large penalty to your exercise score. I suggest that the team remind each other about this at the start of the team meeting.
• Guide: User Story Title Candidates Feedback

• Action-Oriented Titles

  The primary goal of user stories is to capture a specific need or goal of a user in the context of software development. It's about "what the user wants to do" or "achieve" with the software.

  Benefits of Action-Oriented Titles:

  • Clarity Action-oriented titles make it clear what the expected outcome or behavior of the system should be
  • Focus on Value Emphasizing actions reminds the team to focus on delivering value and functionality rather than just creating artifacts
  • Facilitates Testing It is easier to derive test cases from action-oriented stories

• User Story Titles and the Number Grammatical Category

  Strongly consider using a title with a singular noun for a user story, instead of a title with a plural noun, because it emphasizes the atomic nature of the action.

  Plural	Singular
  Upload Documents	Upload a Document
  Send Messages	Send a Message
  Add Products to Cart	Add a Product to the Cart
  Register for Events	Register for an Event
  View Notifications	View a Notification
  Search for Jobs	Search for a Job

  In general, user stories with singular titles are going to be easier to implement. There can be exceptions, as "View Notifications" may be simpler than "View a Notification" due to not having to select just one.

  The most important aspect is clarity and understanding. If "Purchase Clothes" effectively communicates the intent without ambiguity and your team finds it more natural, it's also acceptable. The choice between singular and plural should ultimately be guided by what best serves the clarity and focus of the story in your context.

• Development Environment: Git Setup by next class.

Class

• HFSD Chapter 2
• Exercise 9: HFSD Chapter 2 Crossword
• HFSD Chapter 3
• Exercise 10: Team User Stories II

Unless stated otherwise, all exercises are due by 4 pm on Wed Sep 09