Editing Software Engineering (Winter 2026) (section)

=== February 10 (Tuesday) --  Evidence Part 1:  Static Analysis, Fuzzing, and Scanning  ===

'''Before Class:'''
* Read [https://canvas.uw.edu/courses/1878637/files/folder/Week%206?preview=145213435 Reading Note 10]
* Watch my mini-lecture on [https://canvas.uw.edu/courses/1878637/files/folder/Week%206?preview=145213486 Static Analysis, Fuzzing, and Scanning]
* Watch this lecture from [https://youtu.be/_HUcBzYuWmM?si=rfGRBEFz3PpY3q08 Marcel Bohme: "On the Surprising Efficiency and Exponential Cost of Fuzzing"]
* Read [https://canvas.uw.edu/courses/1878637/files/folder/Week%206?preview=145213587 Chapter 9] in Oram & Wilson's '''Making Software: An Automated Fault Prediction System''', chapter written by Weyuker and Ostrand

'''Class Goals:'''
* Discuss Reading Note 10
* Standup
* Run [[ESLint]] on your code or an equivalent code analysis tool (pylint?). What issues did you find? Any good user stories? This might help you with task 5! This is Lab 6.
* Introducing planning poker
* Getting started with Task 5

<!--
'''Class Materials:'''
* [ Discussion board]
* [ Panopto recording]
-->

'''Optional Resources'''
* If you didn't follow the Fuzzing video, try this [https://www.youtube.com/watch?v=17ebHty54T4 overview of Fuzzing from David Brumley] and then give the Bohme lecture another try :)
* The [https://en.wikipedia.org/wiki/Fuzzing coverage of Fuzzing on Wikipedia] is also quite good.
* [https://faculty.washington.edu/lagesse/publications/ICSE2023.pdf This great paper describes using architectural and specification documents in predictions] of vulnerabilities -- written by Poozhithara, Asuncion, and Lagesse here at UW Bothell

<!-- Ch 10-11 in making software -->