Software crisis
Software crisis is a term used in the early days of computing science for the difficulty of writing useful and efficient computer programs in the required time. The software crisis was due to the rapid increases in computer power and the complexity of the problems that could be tackled. With the increase in the complexity of the software, many software problems arose because existing methods were inadequate.
History
[edit]The term "software crisis" was coined by some attendees at the first NATO Software Engineering Conference in 1968 at Garmisch, Germany.[1][2] Edsger Dijkstra's 1972 Turing Award Lecture makes reference to this same problem:[3]
The major cause of the software crisis is that the machines have become several orders of magnitude more powerful! To put it quite bluntly: as long as there were no machines, programming was no problem at all; when we had a few weak computers, programming became a mild problem, and now we have gigantic computers, programming has become an equally gigantic problem.
Causes
[edit]The causes of the software crisis were linked to the overall complexity of hardware and the software development process. The crisis manifested itself in several ways:
- Projects running over-budget
- Projects running over-time
- Software was very inefficient
- Software was of low quality
- Software often did not meet requirements
- Projects were unmanageable and code difficult to maintain
- Software was never delivered
The main cause is that improvements in computing power had outpaced the ability of programmers to effectively use those capabilities. Various processes and methodologies have been developed over the last few decades to improve software quality management such as procedural programming and object-oriented programming. However, software projects that are large, complicated, poorly specified, or involve unfamiliar aspects, are still vulnerable to large, unanticipated problems.
See also
[edit]- AI winter
- List of failed and overbudget custom software projects
- Fred Brooks
- System accident
- Technological singularity
References
[edit]- ^ "NATO Software Engineering Conference 1968". Retrieved 26 April 2017.
- ^ "Report on a conference sponsored by the NATO SCIENCE COMMITTEE Garmisch, Germany, 7th to 11th October 1968" (PDF). Retrieved 26 April 2017.
- ^ "E.W.Dijkstra Archive: The Humble Programmer (EWD 340)". Retrieved 26 April 2017.
External links
[edit]- Edsger Dijkstra: The Humble Programmer (PDF file, 473kB)
- Brian Randell: The NATO Software Engineering Conferences
- Markus Bautsch: Cycles of Software Crises in: ENISA Quarterly on Secure Software (PDF file; 1,86MB)
- Hoare 1996, "How Did Software Get So Reliable Without Proof?"