Project Assignment

Due 2/5/2000: 1-2 page overview of topic (25 pts)

Due 2/26/2000: presentation (50 pts)

Due 2/26/2000: written report (125 pts)

46-941

Software Design & Engineering

1/15/2001

200 points

This is to be individual work.

For this assignment you are to identify and describe a computing or technology failure, determine what made that particular project a failure, and identify what could have been done to prevent the failure. To give you a starting point, several books have been put on reserve for the class in the Hunt Library. (The complete list is included on the syllabus.) Although several possibilities are given in these books, you are not limited to the cases discussed in them. You can also find information in IT and industry publications (InfoWeek, CIO, Datamation, Computer World, etc…) and general business publications (The Wall Street Journal, Businessweek, etc…). The web and other electronic data sources may also provide useful information. Remember that while private companies are not anxious to share information about their failures, governmental and quasi-governmental organizations usually must make information publicly available. You may also use something from your own experience.

The computing or technology failure to be considered does not have to be limited to computer software nor does the failure have to be a complete failure. Hardware, other computing related technologies, or standards could also be considered. A project may also have initially been a failure that later was either completely or partially successful. If this is the case, both the reasons for the initial failure as well as the eventual success should be considered. The failure could also be the implementation of a technology in a specific organization that failed at that organization but was successful elsewhere.

A report that earns full credit will incorporate at least some of the ideas contained in Terry Winograd's book Bringing Design to Software. If you are more interested in physical design failures, such as the MacIntosh on/off switch that Donald Norman discusses in chapter 12, you may also want to look at Norman's book The Design of Everyday Things (previously published as The Psychology of Everyday Things) which is also on reserve in the library.

This is not to be a "book report" or a simple summary of the material from a single source, like one of the books on reserve. You are to complete a more thorough analysis of a technology failure.

You are to complete three separate things for this project. The details of each are outlined below.

Overview (Due 2/5)

1-2 page overview of your selected failure that briefly describes the failure, the major players, and why you believe it was a failure.

A list of your reference sources (printed or web-based).

Presentation (Due 2/26)

A ten minute presentation on the failure you selected and the reasons identified. Allow a few minutes for questions.

 

Written Report (Due 2/26)

The written report should include at least the following:

1. Overview

2. Description of Project/Technology

Include anticipated benefits

3. Description of Failure

Include criteria used to determine failure

4. Causes of Failure

5. Preventing the Failure

6. Changes Made that Resulted in Success

Only include this section if appropriate

7. References

A complete list of references should be given. You do not have to provide footnotes or endnotes throughout the body of the report unless you are quoting directly from a source. Do not "cut and paste" your way through completion of this report or include material without quotes that should be quoted and referenced. This is to be your own analysis of the situation.