CSE 303, Autumn 2009: Concepts and Tools for Software Development

• Lecture MWF 2:30-3:20PM in  BAG  154 [note recent change from JHN]
• Instructor David Notkin (notkin@cs), CSE 542,  x5-3798
• Office hours Monday 3:30-4:30PM (except November 9, 2009), Tuesday 2:30-3:30PM (except November 10, 2009) and by appointment.  (I am often in my office, and I am happy for people to swing by with questions; if I can't help then, I'll find a time I can.  Also, I may reschedule, decrease or increase the hours based on my schedule and on actual use of the hours by students.)
  
• Teaching assistants
• Hao Lu (hlv@u or @cs) -- office hours Thursdays 2:30-3:30PM in CSE 216 (or by appointment).
  
• Collin Zhang (clzhang@u or @cs) -- office hours Tuesdays 2:30-3:30PM in CSE 216 (or by appointment).
• Staff email cse303-staff@cs.washington.edu will send email to the instructor and teaching assistants.  It is strongly recommended to use this address if you want a quicker response.
  
• Anonymous email via Catalyst for complaints, concerns, ideas, etc. where you prefer to remain anonymous.
  
• Mailing list cse303a_au09@u.washington.edu
• Membership will be automatically managed based on official class lists
• Postings from other than your .u email account may be delayed until approved for posting
• Class discussion board: questions and answers!
• Books and readings -- assigned dates in calendar below
  
• Barrett, D. Linux Pocket Guide. ISBN 0596006284.
  
• Harbison, S., Steele, G. C: A Reference Manual, 5th Edition. ISBN 013089592X.
  Although technically required, no assignments or required readings will be given directly from these textbook, so you may choose not to purchase them if you like. There are a number of reasonable alternatives to these, although I don't know many of them first-hand.  In any case, the required books make useful references when learning Unix and C and are especially helpful for looking things up during on homework assignments. Also, the exams in this course will be open-book, so it may be advantageous to own the books to bring as a reference during exams.
• Other readings as assigned.
  
• Related materials
• National Academy of Engineering, Online Ethics Center, Computers and New Technology
• Forum On Risks To The Public In Computers And Related Systems, The Risks Digest
• ACM Code of Ethics and Professional Conduct
• Software Engineering Code of Ethics and Professional Practice (D. Gotterbarn, K. Miller, S. Rogerson.  Computer Society and ACM
  Approve Software Engineering Code of Ethics, IEEE Computer, October 1999.  Includes some background as well as the code itself.)
  
• Lectures
• Lecture notes will generally be linked in the schedule below after lecture.
• Podcasts will be available: Automated Audio Recording Service Terms of Use are located here: https://www.css.washington.edu/wiki/On-Demand_Audio_Content_Terms_of_Use
• Audio recordings of lectures are available here: http://www.css.washington.edu/course/CSE303A
  
• You will be prompted to logon with your UWNetID when visiting this web page. Adobe Flash Player is required to listen to the lectures. Visit the Adobe Flash Player Download Center if Flash™ is not installed on your computer: http://www.adobe.com/products/flashplayer/
• Listening to the lectures is easy: (a) Choose the lecture that you want to hear; and (b) Click the Play button on the Flash player. 
• Access to the on-line recordings is limited to instructors, teaching assistants, and students enrolled in the class. You will be prompted to logon with your UWNetID when you attempt to view the Web page where the audio recordings are located. 
• The recordings are only for the use of students enrolled in this course, for purposes associated with this course, and may not be retained or further disseminated. These recordings may be protected by copyright; any further use of this material may be in violation of federal copyright law.
• Please note: University personnel engaged in a job related function incident to employment may be monitoring classes, even if the class has been limited to instructors, teaching assistants, and students enrolled in the class.
• Anyone standing near a classroom microphone may be recorded.  Everything that happens during your class period may be recorded when the automated recording system turns on.  I am happy to turn off the microphones for a period if I want or if a student has any kind of reasonable request.  Classroom microphones may not record student questions very clearly unless they speak directly into the microphone. I'll try to repeat or summarize your questions to get the essence on the podcast. 
• Examinations
• The exams are open-book and open-notes. You may bring any written materials, such as textbooks, printed handouts, homework assignments, or programs. No electronic devices may be used, including calculators. Make-up exams are only for someone who is dealing with a serious emergency. If you must miss an exam, even if you are sick or injured, you must contact the instructor before the exam (or arrange for someone to do so).  Appropriate documentation may be required by the instructor.
  
• Grading  Catalyst gradebook (find your grades)
• 50% weekly homework assignments
• 5% written work(s) on societal impact of computing
• 20% midterm (Monday November 2, 2009, in class)
• 25% final exam (Tuesday December 15, 2009, in class) NOTE: corrected from Thursday TO TUESDAY
  
• I make no guarantee of grade breakdowns, but it's likely that 90% will produce a 3.5 or higher, 80% a 2.5 or higher, 70% a 1.5 or higher, and 60% a 0.7 or higher.
• Regrading requests: (a) any initial request should go to the TAs (unless I grade the assignment or exam, which I'll announce); (b) if necessary, I'll look at requests that you're no
  
• Assignments
• Homework #0: Answer the short questionnaire on Catalyst; it will be available from 9/30/09 @ 3:30PM through 10/2/09 @ 12 Noon.  It counts for 5% of your homework grade, and it is all or nothing -- if you turn it in during the window, you get full credit; if you don't, you get no credit.  I care about the content, but your grade does not depend upon the content. 
  
• Homework #1: 10% of your homework grade.  Due Thursday October 8, 11:30PM.  Hao's wild solution.
  
• Homework #2: 15% of your homework grade.  Part 2A is due Tuesday October 13, 11:30PM; Part 2B (announced on Wednesday, not Monday as initially promised) will be due on Tuesday October 20, 11:30PM.
• Homework #3: 10% of your homework grade.  Due Thursday, October 29, 2009, 11:30 PM.
• Homework #4: 15% of your homework grade.  Due Tuesday, November 10, 11:30PM.
• Homework #5 and #6: each is 15% of your homework grade.  HW#5 is done individually, and is due Sunday November 22, 2009, 11:30PM. HW#6 builds on HW#5, is done in pairs and is due on Tuesday December 1, 2009.  (See assignment for more details.)
• Homework #7: 20% of your homework grade.  Will be assigned on Wednesday December 2 and will be due on Sunday December 13, 11:30PM. (changed to PM due to popular demand)
  
• Ethics/Social Implications #1: one-third of your social impact of computing grade, due Monday, October 19, 2009, 11:30 PM.
• Late assignments
• An assignment can be submitted up to 24 hours late for a loss of 10% of its points. No assignments will be accepted more than 24 hours late or after the last day of class. Extensions will not be given except with extenuating circumstances or emergency as decided by the instructor. 
  
• In addition, each student receives two "late days" for use on homework assignments. Each late day allows you to submit one assignment up to 24 hours late without penalty. For example, you could use a late day and submit a program due Thursday 11pm on Friday by 11pm. Only one late day may be used on any particular assignment.  (You can choose between the 10% penalty and the late day, if you have a late day remaining, but you cannot change your mind afterwards.)
• Academic misconduct is a very serious offense and will be dealt with through the departmental, college and university processes. Copying others' work, including from this or previous quarters or from publicly available sources without attribution, is considered cheating.  If in doubt about what might constitute cheating, check with the instructor about the situation. For more details see the CSE Academic Misconduct web page.
  
• At the same time, it is really good to share problems and solutions about the technology itself with each other.  If you're really frustrated with trying to find, for example, a Unix command to perform a certain operation, ask around the lab.  If you can't figure out why your C program is failing in a particular way, ask around.  Indeed this can be a fine line, so all parties must be aware of when the line of academic misconduct is approaching, and then care must be taken.  As above, if in doubt about what might constitute cheating, check with the instructor about the situation.
• Schedule  Thanks to Wikipedia for the interesting computing, technology and other random things associated with each date.