1. #in-class
Take a look at the A2 assignment description Respond to the poll on #in-class Post questions you have about A2 on #in-class, or emoji a question that you like

2. Agenda
A1 post-mortem
A2 – event handling
Requirements Gathering

3. Comments about A1
SENG 301

4. A1: Some notes on grading
Grades should be in by Friday By the end of day, I will post: (a) a working solution, and (b) the test scripts that we used to assess your code Test scripts: Check, Check +

5. Lessons from A1: Meta
It’s hard when you don’t really “control” execution It’s hard when the system is big It’s hard when you don’t get to write from a blank sheet of paper But, this is real life!

6. Lessons from A1 Handle exception cases by throwing Exceptions
Scripts  ScriptProcessor  Parser  VendingMachineFactory
Handle exception cases by throwing Exceptions
Handle non-exceptional cases by handling input logically
The specification is everything! The principle learning objective: learn how to write to a spec. Problem: it’s a living document.
Are there ambiguities or contradictions?  Resolve these ASAP.

7. Lessons from A1: Process
Assignments in SENG 301 are not throwaway; they are learning experiences that we designed purposefully—I want you to get something out of these: (a) exercise something that we’ve learned in class, and (b) learn something about how to wrangle with code Avoid the “I can do it all at once in one concerted push” mentality—instead, chip away Use the resources that we have made available: #A1, office hours, your classmates, etc. Don’t worry about your grade. Instead, consider: Did you learn what you were supposed to? Did you get something out of the exercise? How can you learn what you were supposed to?