learning objectives:
* define "software requirement"
* define "security requirement"
* explain functional and non-functional requirements
* identify the characteristics of good software requirements
* construct use and abuse cases for software
* use abuse cases to identify security requirements

activities:
* read SSBSI 8: Abuse Cases
* read SecurityRequirements.pptx slides 
* read https://www.cs.umd.edu/~atif/Teaching/Spring2010/Slides/3.pdf slides (pages 1-5, 9-12, 18-22)
* read: 3 ways abuse cases can drive security requirements (https://www.synopsys.com/blogs/software-security/abuse-cases-can-drive-security-requirements/)
* read: Are you making software security a requirement? (https://www.synopsys.com/blogs/software-security/software-security-requirement/)

extra:
* watch and review any [software] security requirements video
	- post title, link, review on Piazza

assignments:
* Quiz 1 (due 8:00am 27 Jan)
	- posted on eCampus at 2pm 21 Jan
* HW 1 (due 8am 27 Jan, 3,10 Feb)