CPSC 480 Software Engineering (SE) Fall 2024

News

• Week 15 Class 27 Tue Dec 03 Posted: Dec 03

  Announcements

  • Project 3: TDD

    Scores are in Brightspace, along with individual part scores in a table.

    • Cyclomatic Complexity is the number of simple conditions plus 1
    • Each rule test case at most requires the addition of 1 simple condition, either in a new if-statement, or added to the condition of an existing if-statement
    • This complexity tells us the minimum number of test cases needed for complete code coverage
    • Other "rules" (or features) may require the addition (or change) of multiple conditions. Handle this by multiple test cases implemented one at a time.
    • The role of the Oracle
  • Final Exam Tuesday, Dec 10, 2:30 - 4:30 pm

  • Course Evaluation

    • Open until Dec 8
    • Individual answers are always anonymous
    • I do not see the overall scores until after I submit the course grades

    Bonus: I will drop your lowest Exercise score if at least 80% of the class fills out the course evaluation. We are currently at 60% of the class.

  • Project 4: Streaming Due Friday, Dec 13 at Noon

    Streaming	Sum	Min	Max	Mean	Median	Mode
    Issues	85	2	17	7.1	5	3
    Branches	87	3	16	7.2	6	6
    Commits	98	0	32	8.2	4.5	0
    Authors	12	0	5	1.0	0	0
    Pull Requests	32	0	10	2.7	1	0
    Pull Requests Merged	20	0	10	1.7	0	0
    Pull Requests Open	11	0	8	0.9	0	0

  Class

  • Exercise 70: Project 4 Commit

    For many teams, all they 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 were 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 about how to do so, discuss them during your team meeting.

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

  • Notes: Software Change
  • Exercise 71: Software Change Crossword

  • Exercise 72: 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: Scrum

  • Exercise 73: Team Streaming Meeting III

    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 pm on Wed Dec 04

• Final Exam Posted: Dec 03

  
  The Final Exam is in our regular classroom Final Exam: Tuesday, Dec 10, 2:30 - 4:30 pm.

  You are responsible for what we have covered since the Midterm:

  • Types of Testing - black box, white box, grey box, whose view they represent and the kinds of things they test for
  • TDD - Principles and process
  • Process Models - standard process models, Waterfall, Agile, requirements volatility
  • Software Evolution - greenfield and brownfield development, main conclusions of Lehman's Laws
  • Refactoring - basic definition, terminology, process. Be able to perform a "Replace Nested Conditional with Guard Clause" refactoring and discuss it.
  • Git Workflow - The main git commands, understanding of branches, and pull requests. GitHub issues.
  • Git commit messages - proper form
  • Software Lifespan Models - stages and characteristics of each stage, code decay, and reengineering
  • Software Change - types of change, concept location, impact analysis. Be able to identify the maintenance category from a commit message.
  • Scrum - fundamental steps, terminology, and time limits

  The exam has various problem types, including short answers, definitions, comparisons, and application to a code example/scenario.

  If I did not cover it in class, it is not on the exam.