Home

Announcement: order for final presentations -- all on Monday June 7, 8:30-10:30AM.  10-12 minutes each.
1.c 
2.a 
3.h 
4.d 
5.e 
6.f 
7.b 
8.g 

Lecture    MWF 10:30-11:20AM in More 230
Section    Th 9:30-10:20AM in EE 037

Staff           Instructor David Notkin (notkin@cs), CSE 542, 206-685-3798
                   Teaching Assistants Abe Friesen (afriesen@cs) and Nicholas Brekhus (gu13@cs)
                    Cse403-ta@cs to email all three

Mailing list cse403a_sp10@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 (and you are responsible for looking at your.u email directly or via forwarding or however you prefer).

Discussion board for comments, questions, etc. about software engineering and CSE403 on Catalyst

Anonymous feedback Comments, complaints, kudos, etc.

Assigned work (percentages subject to change a bit until May 14)
  • Group project (70%): a six-person quarter-long project selected from (a) a co-authorship network explorer or (b) a software clone detector.
    • Teammates usually receive the same grade for the project, except in special circumstances.
    • A partial schedule with milestones is posted, including the initial and revised requirements documents.
      • A status report is due from each team every Sunday by 11PM.  Submit these via the Catalyst dropbox -- instructions on the format and who should submit are found there.
    • Each group may be required to make a presentation to the class on a particular milestone of their project.
    • By Wednesday March 31 @ 5PM, submit your preferred teammates!
    • SRS (software requirements) information
    • SDS (software design) information
  • Two exams (12.5% each)
    • Exam 1: In class, Friday April 30.
    • Exam 2: In class, Friday June 4.
  • Readings (5%)
Lecture Slides

Notkin will be in Cape Town for ICSE 2010, missing lectures on April 30, May 3-5-7, and in Portland for NCWIT, missing lecture on May 19.  Plans will be announced soon.
  • March 29, 2010: Introduction (pdf, ppt)
  • March 31, 2010: Software lifecycle (pdf, ppt)
  • Section on April 1, 2010: Tools (pdf, ppt)
  • April 2, 2010: Teams (and a brief on requirements) (pdf, ppt)
  • April 5, 2010: Requirements (pdf, ppt)
  • April 7, 2010: User interface prototyping (pdf, ppt)
  • April 9, 2010: Version control (pdf, ppt)
  • April 12, 2010: Software architecture (pdf, ppt)
  • April 14, 2010: UML class diagrams (pdf, ppt)
  • April 16, 2010: UML sequence diagrams (pdf, ppt)
  • April 19, 2010: Information hiding (pdf, ppt)
  • April 21, 2010: Information hiding continued (pdf, ppt)
  • April 23, 2010: No lecture due to Engineering Discovery Days)
    • BUT I will be in the basement labs from 10:30-11:20 to look at draft SDS documents, answer questions, etc.
  • April 26, 2010: Design patterns (pdf, ppt)
  • April 28, 2010: sample SDS presentation (pdf, as a model for your presentations the following week), more information on the first midterm (pdf, ppt)
  • April 30, 2010: First midterm (Notkin absent)
  • May 3, 5 and 7: SDS presentations from each group (Notkin absent, TAs will lead), 10 minutes each + questions.  
  • May 10, 12 and 14, 2010: Quality assurance (pdf, ppt)
  • May 17 and 21, 2010: Mutation and symbolic evaluation (pdf, ppt, Cute Examples pdf, ppt)
  • May 24, 2010: Software IP (pdf, ppt)
  • May 26, 2010: Reviews and refactoring (pdf, ppt)
  • May 28, 2010: Debugging (pdf, ppt)
  • May 31, 2010: Holiday, no class
  • June 2, 2010: 2nd midterm review (pdf, ppt)
  • June 4, 2010: 2nd midterm
Assorted Information
  • [Thanks,  Nick!] The UW Library system has lots of useful reference materials available.    Among these are a large number of the O'Reilly series of books on various technical topics (e.g., the rhino book for javascript, a multitude of books regarding C#, ASP.NET, Java, Ruby on Rails, Python, etc.).  They are not authoritative, but generally serve as agood supplement to the diffuse and often contradictory information and advice you'll find on the web. These are found on the library web site -- with other materials of value! -- at Safari Online (offcampus link)

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, send the instructor email describing the situation. For more details see the CSE Academic Misconduct web page.