CSE
442/542 Software Engineering Spring 2010
Announcements:
The FINAL (TAKEHOME) EXAM - FinalExam.doc / FinalExam.pdf
This exam is due by 11:59:59 PM on Tuesday May 4, to be emailed to
Peer Evaluations - Please complete and bring hard-copy to your demo.
Demo schedule:
Tues 4/20: A B C D
Thurs 4/22: E F H Z
2/17/2010 - Changes to the CSE442/542 Syllabus
a. The attendance grade is removed as a requirement. Instead, up to 5% extra credit will be awarded based on random attendance taken throughout the semester. This essentially rewards those who attend class but does not punish those who don't. History with this class shows that attendance correlates strongly to final grade since many exam topics are discussed in class independent of the published notes. Please attend.
b. The 5% is replaced by a "relevant topic discussion grade". Essentially, each student OR TEAM is required to offer a topic for discussion. No individual classroom presentation is required beyond the introduction and background on the topic (you will, however, need to explain why the topic is relevant and interesting). The class will take it from there. Especially desired are multimedia presentations of current events related to Software Engineering.
Grade Inspector (click here to check your grades)
Lectures and Notes:
CSE442/542 Syllabus
Day 1 Information
SW Implementation Steps - reference "Essay On Objects and Modeling"
Eclecticism
The Design of Everyday Things
Writing the System Specification
Software Errors
Pre-Project Testing
Critical Thinking
Resumes and Interviewing
Critical Paths and Phase 4 Robot.mpp
Tao of Engineering
Reading Assignments (mandatory)
5 ways to fail
Billions spent on SW errors
People cause SW errors
Poor interface design
Therac 25 Error
PowerPoint Brings Down Shuttle
The Color of the Cosmos?
Software Glitch Grounds F-22
Software Turns Mars Orbiter Into Space Junk NASA Report
worse than failure: http://worsethanfailure.com/
Long Distance Failure
Reading List 3: due 3/17
If Architects Had to Work Like Programmers
Data wants to be free
You Aren't Gonna Need It
Space Station computer crisis
Computer Viruses in Orbit
Feature Creep
Telephone for the blind
How to Write Unmaintainable Code
Please read the Tao of Pooh, by Benjamin Hoff, by 4/4
Reading List 4:
The Capability Maturity Model (The CMM)
Ellen Goodman on complexification
The Master, the Expert, and the Programmer
Who coined the word "bug" (alas, it was not Grace Hopper)
Drop and Code Me Twenty!
They Write the Right Stuff
Team, and Project Information: Instructions to Teams Team Building and Trust Hopes and Fears
Problem Statements
Map to Center for Handicapped Children
A note about project grades - teams are given the AVERAGE of two letter grades: one calculated by the graders (instructor and two TAs) and one assessed by members of local industry. The letter grade is then translated into points reflecting that letter grade, and those points are given to each individual of team. The letter grade-to-points scale is set based on relative complexity of the project phase and your expected level of skill and work.
Phase 1: Preliminary Requirements – 2/3 – Your team must post (to the team web site) a list of requirements and a narrative describing the problem to be solved. These are NOT the formal requirements, but a preliminary list to merely evaluate whether you are on the right track. Simply answer the question: What will our system do? No need to write more than 2 pages.
Phase 2 - The System Specification - due 2/24 - Grades here: Phase2GradingSheet.xls
Phase 3 - The Software Requirements Specification - due 3/24 - Grades here: Phase3GradingSheet.xls
Phase 4 - The Project Plan - due 4/2 - Grades here: Phase4GradingSheet.xls
Phase 5 Instructions
Team Web Sites: CSE 442/542 Project Teams (CSE442Teams.pdf)
Team A - Air Quality Control Sensor
Team B - Blind Information System
Team C - CHC Web Site
Team D - Socially Relevant Computing
Team E - Wheelchair-based Flight Simulator
Team F - UB Talker
Team H - Firefighter Monitoring
Team X - Nursing Home Alert 2
Team Z - Nursing Home Alert 1
Office Hours: MWF 12-2 and 3-4, usually in Baldy 19Announcements:
The FINAL (TAKEHOME) EXAM - FinalExam.doc / FinalExam.pdf
This exam is due by 11:59:59 PM on Tuesday May 4, to be emailed to
Peer Evaluations - Please complete and bring hard-copy to your demo.
Demo schedule:
Tues 4/20: A B C D
Thurs 4/22: E F H Z
2/17/2010 - Changes to the CSE442/542 Syllabus
a. The attendance grade is removed as a requirement. Instead, up to 5% extra credit will be awarded based on random attendance taken throughout the semester. This essentially rewards those who attend class but does not punish those who don't. History with this class shows that attendance correlates strongly to final grade since many exam topics are discussed in class independent of the published notes. Please attend.
b. The 5% is replaced by a "relevant topic discussion grade". Essentially, each student OR TEAM is required to offer a topic for discussion. No individual classroom presentation is required beyond the introduction and background on the topic (you will, however, need to explain why the topic is relevant and interesting). The class will take it from there. Especially desired are multimedia presentations of current events related to Software Engineering.
Grade Inspector (click here to check your grades)
Lectures and Notes:
CSE442/542 Syllabus
Day 1 Information
SW Implementation Steps - reference "Essay On Objects and Modeling"
Eclecticism
The Design of Everyday Things
Writing the System Specification
Software Errors
Pre-Project Testing
Critical Thinking
Resumes and Interviewing
Critical Paths and Phase 4 Robot.mpp
Tao of Engineering Reading Assignments (mandatory)
Reading List 1: due 1/27
Essay
On Objects and Modeling
A's
for Everyone! not exactly software related, but relevant
Steve
McConnell on the goto Debate
The
Quote Garden - programming pearls
The
Dumbing Down of Programming Pages 1 & 2
The
Dumbing Down of Programming Pages 3 & 4
Steve
McConnell's chapter on Eclecticism
5 ways to fail
Billions spent on SW errors
People cause SW errors
Poor interface design
Therac 25 Error
PowerPoint Brings Down Shuttle
The Color of the Cosmos?
Software Glitch Grounds F-22
Software Turns Mars Orbiter Into Space Junk NASA Report
worse than failure: http://worsethanfailure.com/
Long Distance Failure
Reading List 3: due 3/17
If Architects Had to Work Like Programmers
Data wants to be free
You Aren't Gonna Need It
Space Station computer crisis
Computer Viruses in Orbit
Feature Creep
Telephone for the blind
How to Write Unmaintainable Code
Please read the Tao of Pooh, by Benjamin Hoff, by 4/4
Reading List 4:
The Capability Maturity Model (The CMM)
Ellen Goodman on complexification
The Master, the Expert, and the Programmer
Who coined the word "bug" (alas, it was not Grace Hopper)
Drop and Code Me Twenty!
They Write the Right Stuff
Team, and Project Information: Instructions to Teams Team Building and Trust Hopes and Fears
Problem Statements
Map to Center for Handicapped Children
A note about project grades - teams are given the AVERAGE of two letter grades: one calculated by the graders (instructor and two TAs) and one assessed by members of local industry. The letter grade is then translated into points reflecting that letter grade, and those points are given to each individual of team. The letter grade-to-points scale is set based on relative complexity of the project phase and your expected level of skill and work.
Phase 1: Preliminary Requirements – 2/3 – Your team must post (to the team web site) a list of requirements and a narrative describing the problem to be solved. These are NOT the formal requirements, but a preliminary list to merely evaluate whether you are on the right track. Simply answer the question: What will our system do? No need to write more than 2 pages.
Phase 2 - The System Specification - due 2/24 - Grades here: Phase2GradingSheet.xls
Phase 3 - The Software Requirements Specification - due 3/24 - Grades here: Phase3GradingSheet.xls
Phase 4 - The Project Plan - due 4/2 - Grades here: Phase4GradingSheet.xls
Phase 5 Instructions
Team Web Sites: CSE 442/542 Project Teams (CSE442Teams.pdf)
Team A - Air Quality Control Sensor
Team B - Blind Information System
Team C - CHC Web Site
Team D - Socially Relevant Computing
Team E - Wheelchair-based Flight Simulator
Team F - UB Talker
Team H - Firefighter Monitoring
Team X - Nursing Home Alert 2
Team Z - Nursing Home Alert 1