1. Week 2 Agenda Reaction paper due Thursday Keep up with readings –SE Code (25 min) –10 Commandments (10 min) –To Engineer is Human (3 hours) –Johnson Ch 1 and 2 (1 hour) –Cal Poly Policy on Cheating (30 min) –Cal Poly RUP (30 min)

2. Week 2 Agenda Form teams for CSC 300 Lab Projects Have a 2 minute talk ready –I’ll choose you randomly to give them Registration reminder (ADD’s, etc.) Work on Paper/Presentation topic choice start your research early suggestions for topics

3. Petroski Reaction Paper Format: modified from my “tips sheet” on the CSC 300 Termpaper webpage –Facts - what unarguable facts underlie this book? –Issue(s) -choose one you’d like to investigate –Arguments - make his arguments succinctly, bring in counter arguments you may know (and cite) –Analysis - use facts, arguments and analysis to tell me the “real answer” according to your best thinking Emphasize your analysis, but do it on basis of the facts, issue and argument. 4 - 5 pages double spaced, 12 font, small margins

4. Paper writing Use Strunk & White “Elements of Style” Use spell checker Check grammar Ideas should logically flow You should have a point Have a friend read it over for you –is it interesting, does the reader learn something?

5. Paper writing Use at least one quote, proper format, –Fully functional specification languages are “an industrial imperative …” according to Professor Fisher [Fish04] –later, in bibliography: [Fish04] Fisher, “RSL, the Right Way to Specify Requirements,” Vol 23 IEEE Transactions in Formal Specifications, January 2004. Look up a definition of plagiarism fyi

6. Petroski’s Book What are the “facts” that give rise to the book? What are some of the issues or themes Petroski highlights? Any issues match with SE Code, 10 commandments, RUP, Johnson? What are some of Petroski’s arguments about the issues (match issue with argument) Are there counter arguments? How do YOU analyze an issue? –NOT what you “feel” - you must logically back up your analysis with facts and arguments

7. Possible General Paper Topics Intellectual Property in software Online gaming Military use of software Expert Systems and personal responsibility Spyware Database / Network privacy Software Engineering - to license or not?