Software crisis is a term used in the early days ofcomputing 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 thecomplexity 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.
The term "software crisis" was coined by some attendees at the firstNATO Software Engineering Conference in 1968 atGarmisch, Germany.[1][2]Edsger Dijkstra's 1972Turing 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.
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:
The main cause is that improvements in computing power had outpaced the ability of programmers to effectively use those capabilities. Variousprocesses and methodologies have been developed over the last few decades to improvesoftware quality management such asprocedural programming andobject-oriented programming. However, software projects that are large, complicated, poorly specified, or involve unfamiliar aspects, are still vulnerable to large, unanticipated problems.