CPSC 480-010 Software Engineering (SE) Fall 2023

Week 14 Class 25 Tue Dec 05 Posted: Dec 05

Announcements

• Final Exam Dec 12, 12:15 - 2:15 pm
• Project 4: Streaming Reminder: Due Friday, Dec 15 at Noon
• Project TDD Complexity
• WAGTime Therapy Dogs 10 am - Noon on Wednesday and Thursday

Class

• Notes: Software Change
• Exercise 63: Software Change Crossword

• Exercise 64: Maintenance Categories

  The quiz in the title link requires identifying commit types based on the commit message. Classifying changes into new features or particular maintenance categories based solely on the commit message is inaccurate. Accurately doing so requires considering the code changes (including added code comments), any related issues, and any related discussion to know the reason for the change, e.g.:

  • To tell the difference between adding a new feature and adaptive maintenance.
  • To tell the difference between preventive and corrective maintenance.

  In this exercise, all commits are not for new features but for maintenance, with the only categories considered being corrective, adaptive, and perfective.

  One other consideration is the purpose of the change:

  • Fixes to internal code documentation (e.g., header comments), pure test changes, changes to build files, etc., are not corrective but perfective because they do not affect the program's behavior for the user.
  • Fixes to build files are often for new versions of the build tools, e.g., cmake, and are not corrective but adaptive.
  • Removal of code can be perfective. However, if the code was removed because of a deprecated API, that is adaptive.

  You will see if you are correct as soon as you submit the quiz. You can make changes to your answer.

• Notes: Code Smells
• Exercise 65: Code Smells Crossword

• Notes: Scrum

• Exercise 66: Commit

  So far, your teams have created the following:

  • Issues The median is 6 per team.
  • Branches The median is 1 2 per team. And, over 1/3 almost 1/4 of the names do not follow the assignment guidelines.
  • Commits 0, zero, nil, zilch, nada 7.
  • Pull Requests Since there are no commits, no pull requests 1.

  So overall, all that the teams have accomplished on the project is to create issues. That is just the start. If you did not push, then push your commits. If you were "waiting" to do any real work until after all the issues are created, stop taking a waterfall approach.

  About the branch names that do not follow the assignment branch naming guidelines, git does not store who created a branch, just who made the first commit (a branch in git is just a pointer to a commit), so these naming issues reflect on the team, not just individual team members.

  Make a worthwhile commit to a branch. If you have any questions on how to do so, figure that out during your team meeting.

  If you have already made a commit to the project, you will receive full credit for your contribution.

• Exercise 67: Team Streaming Meeting IV

  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 part is due by the end of class.

Unless stated otherwise, all exercises are due by 3:30 pm on Wed Dec 06