Reasons For Failure
The project demonstrated a systematic failure of software engineering practices:
- Lack of a strong blueprint from the outset led to poor architectural decisions.
- Repeated changes in specification.
- Repeated turnover of management, which contributed to the specification problem.
- Micromanagement of software developers.
- The inclusion of many FBI Personnel who had little or no formal training in computer science as managers and even engineers on the project.
- Scope creep as requirements were continually added to the system even as it was falling behind schedule.
- Code bloat due to changing specifications and scope creep. At one point it was estimated the software had over 700,000 lines of code.
- Planned use of a flash cutover deployment, which made it difficult to adopt the system until it was perfected.
Read more about this topic: Virtual Case File
Famous quotes containing the words reasons for, reasons and/or failure:
“Here we also see: what this divinity lacks is not only a sense of shame—and there are also other reasons for conjecturing that in several respects all of the gods could learn from us humans. We humans are—more humane.”
—Friedrich Nietzsche (1844–1900)
“The lore of our fathers is a fabric of sentences.... It is a pale gray lore, black with fact and white with convention. But I have found no substantial reasons for concluding that there are any quite black threads in it, or any white ones.”
—Willard Van Orman Quine (b. 1908)
“Sitting by a lamp more often brings
Not peace, but other things.
Beyond the light stand failure and remorse....”
—Philip Larkin (1922–1986)