CSE
442/542 Software Engineering Fall 2009 - Syllabus here
Phase 4 Grades: Use the Grade Inspector to check your grade. A correct sumission was worth 92 pts., up to 4 pts. were added for insight (demonstration of a real understanding of the process), and up to 4 pts. were added for creativity (anything done extra, like plotting a spending curve).
Grade Inspector
Peer Review Form
Lectures
and Notes:
Day
1 Information
Software Implementation Steps
Eclecticism
The Design of Everyday ThingsThe System Spec (and Phase 2)Software Errors
Pre-Project Testing
Resumes
The Software Requirements Specification (SRS)
Partitioning and Modularity
Critical Thinking
a sample commercial maintenance plan
Legal and Ethical Issues
books:
The Tao of Pooh (required)
Code Complete (optional)
Reading
Assignments (mandatory)
Reading List 1: due 9/14
Essay
On Objects and Modeling
A's
for Everyone! not exactly software related, but relevant
Steve
McConnell on the goto Debate (or read Code Complete, pgs 398-408)
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 (or read Code Complete, pgs 851-852)
Reading List 2: due Oct. 2
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 Nov. 22
The Tao of Pooh by Benjamin Hoff ( here )
If
Architects Had to Work Like Programmers
Data
wants to be freeYou
Aren't Gonna Need ItSpace
Station computer crisisComputer Viruses in Orbit
Feature
Creep
Telephone
for the blind
How to Write Unmaintainable Code
Reading List 4: due TBD
Interesting Videos, etc.
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
Your team assignnments here: CSE442Projects.xlsA note about 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 – 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. - Due by Midnight Wednesday 9/23.
Phase 1 commentsPhase 2 - The System Specification - due Oct. 7 - Phase 2 grades: here
Phase 3 - The Software Requirements Specification - due Nov. 2 - Phase 3 grades: here
Phase 4 - The Project Plan - due Nov. 13
Phase 5 Instructions - The Demo - due Dec. 7 - Peer Review Form
Team Web Sites:
Team A - Badge Tracking
Team B - Firefighter Vital Signs Monitoring and Locator
Team C - Video conferencing for the Classroom
Team D - Relational Agent Talking Head
Team E - Community Information Access
Team F - Computer and Internet Access via a Single Switch
Team G - Portable Indoor Air Quality Sensor
Team H - Firefighter Safety
Team I - CHC Website
Team J - Sim City Simulation
Team K - DISCO
Team L - Portable Indoor Air Quality Sensor
Team M - Community Database Information
Team N - Remote Controlled Wheelchair
Team O - Relational Agent Talking Head
Team P - Single Switch Internet Access
Team Z - Blind Obstacle Avoidance
Policy
on Academic Integrity
