| Software Crisis |
Article Index for Software |
Website Links For Software |
Information AboutSoftware Crisis |
| CATEGORIES ABOUT SOFTWARE CRISIS | |
| information science | |
| software engineering | |
| history of software | |
| crisis | |
|
Conflicting requirements have always hindered the software development process. For example, while users demand a large number of features, customers generally want to minimise the amount they must pay for the software and the time required for its development. The term software crisis was coined by F. L. Bauer at the first NATO Software Engineering Conference in 1968 at Garmisch , Germany. An early use of the term is in Edsger Dijkstra 's 1972 ACM Turing Award Lecture, "The Humble Programmer" (EWD340), published in the '' Communications Of The ACM ''. Dijkstra states: The causes of the software crisis were linked to the overall complexity of the software process and the relative immaturity of software engineering as a profession. The crisis manifested itself in several ways:
Various Processes And Methodologies have been developed over the last few decades to "tame" the software crisis, with varying degrees of success. However, it is widely agreed that there is no "silver bullet" - that is, no single approach which will prevent project overruns and failures in all cases. In general, software projects which are large, complicated, poorly-specified, and involve unfamiliar aspects, are still particularly vulnerable to large, unanticipated problems. SEE ALSO
REFERENCES
|
|
|