CSE
442/542 Fall 2008
Phase 4 Demo Schedule:
Monday Dec. 1: F I J M P R
Wednesday Dec. 3: B D E L O Q
Friday Dec. 5: C G H K N S
Peer Review Forms (fill out for your team members and yourself, and submit them with you final exams): PeerReview.doc
CSE442/542 Final Exam,
Fall 2008
Please read the
directions carefully. This exam is due by 4 pm on Wed. 12/10 in Knox 109
(the site of our originally scheduled final exam), or by 12 noon on 12/10 by
any other means (hard-copy/post office mail to 137 Bell Hall, slid under my door, etc.). No late
exams will be accepted. The exam must be submitted in hard copy. No emails will
be accepted. There is a page limit of two pages (or 1 page, both sides).
Phase 1 grades: here
Phase 2 grades: here
Phase 3 grades: here
Lectures
and Notes:
CSE442/542
Syllabus
Day
1 Information
SW
Implementation Steps - reference "Essay On Objects and Modeling"
Eclecticism - reference Sept 15 reading list and McConnell pgs. 851-853System SpecThe Design of Everyday Things
Software Errors - reference Sept. 22 reading list, and McConnell Chapt 20. and Sect. 22.4, and Chapt. 33
Pre-Project Testing - read McConnell, Chapter 3.
Resumes
PartitioningCustomersDetails of the SRSProject Management
Critical Path
The Tao of EngineeringMetrics - grading software effectiveness
Legal and Ethical Issues
HardwareReading
Assignments (mandatory)
By Nov. 1: Please read the Tao of Pooh.
by Sep 15:
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)
by Sept. 22:
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 Failureby Oct 1:
If
Architects Had to Work Like Programmers
Data
wants to be freeYou
Aren't Gonna Need It
Space
Station computer crisis
Computer Viruses in Orbit
Feature
Creep
Telephone
for the blind
How to Write Unmaintainable Code
By Nov. 1: Please read the Tao of Pooh.
By Nov. 15:
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!
By Nov. 21:
They Write the Right Stuff
Team,
and Project Information:
Team Assignments: Instructions
to Teams Team Building and Trust Hopes
and Fears
Problem
Statements
a note about grades - teams are given
the maximum 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.
Project
Phase 1 - due Oct. 6 grades
Project
Phase 2 - due Nov. 3
Project
Phase 3 - due Nov. 12
Project
Phase 4 - due Dec . 1
Team Web Sites:
Team B - Badge Tracker
Team C - Screen Builder and Teaching Aid
Team D - City Tracker
Team E - Community Database
Team F - Badge Tracking
Team G - Socially Relevant Computing
Team H - Quadriplegic Enabling
Team I - GPS for the Blind
Team J - Badge Tracking
Team K - Firefighter
Team L - Adaptive Internet for the Disabled
Team M - Too Much Info Community Mapping
Team N - Video Conferencing
Team O - Badge Tracking
Team P - Digital Sensing
Team Q - Hospital and Nursing Home Alert
Team R - Smart Building
Team S - Remote Controlled Wheelchair
Map
to Center for Handicapped Children
Policy
on Academic Integrity
