I am currently teaching CS 428 (“Software Engineering”) at BYU this semester, and my students just finished their midterm a week ago. Most of the questions on the test posed a hypothetical situation on an IT project or at work and asked them to identify risks and/or solutions, with citations from the books and articles […]
ITSF White Paper
It seems that each year brings another story about a failed or very troubled IT project attempting to replace or re-engineer the computer systems for some state’s Department of Motor Vehicles. The latest is this well-researched and well-written article by Bruce Landis at the Providence Journal about the problems the state of Rhode Island has […]
[Adapted from Patterns in IT Litigation: Systems Failure (1976-2000)] Summary: The manufacturer makes some change in the functionality or configuration of the system, which is already in use. The change results in unpleasant or unintended consequences for one or more clients.
[Adapted from Patterns in IT Litigation: Systems Failure (1976-2000)] Summary: The client buys a system from the vendor. Some time later, the client discovers that the system either no longer meet its needs or that the vendor/manufacturer will no longer support it.
[Adapted from Patterns in IT Litigation: Systems Failure (1976-2000)] Summary: The client contracts with the manufacturer to develop and install a system. The project starts. The completion date slips. It keeps slipping. Each time the adjusted delivery date approaches, the project slips yet again. At some point, one of three things happens: the manufacturer/vendor abandons […]