Knowledge

Software crisis

Source 📝

60:
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
88:
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:
28:
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
32:
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.
136:. However, software projects that are large, complicated, poorly specified, or involve unfamiliar aspects, are still vulnerable to large, unanticipated problems. 150: 274: 120:
The main cause is that improvements in computing power had outpaced the ability of programmers to effectively use those capabilities. Various
41: 207:"Report on a conference sponsored by the NATO SCIENCE COMMITTEE Garmisch, Germany, 7th to 11th October 1968" 307: 121: 71: 185: 133: 125: 230: 302: 165: 76: 312: 206: 129: 29: 98: 8: 254: 25: 264: 287: 160: 66: 49: 109: 296: 260: 53: 155: 283: 61:
gigantic computers, programming has become an equally gigantic problem.
145: 114: 40:
The term "software crisis" was coined by some attendees at the first
45: 124:
have been developed over the last few decades to improve
110:
Projects were unmanageable and code difficult to maintain
231:"E.W.Dijkstra Archive: The Humble Programmer (EWD 340)" 151:
List of failed and overbudget custom software projects
288:"How Did Software Get So Reliable Without Proof?" 294: 56:Lecture makes reference to this same problem: 186:"NATO Software Engineering Conference 1968" 265:The NATO Software Engineering Conferences 106:Software often did not meet requirements 295: 255:Edsger Dijkstra: The Humble Programmer 223: 199: 42:NATO Software Engineering Conference 24:is a term used in the early days of 178: 13: 14: 324: 248: 16:Term in early computing history 72:The Humble Programmer (EWD340) 1: 171: 99:Software was very inefficient 115:Software was never delivered 92:Projects running over-budget 7: 139: 134:object-oriented programming 126:software quality management 122:processes and methodologies 103:Software was of low quality 10: 329: 95:Projects running over-time 35: 271:Cycles of Software Crises 166:Technological singularity 83: 77:Communications of the ACM 130:procedural programming 81: 58: 308:History of software 275:ENISA Quarterly on 280:(PDF file; 1,86MB) 257:(PDF file, 473kB) 26:computing science 320: 303:Software quality 269:Markus Bautsch: 242: 241: 239: 237: 227: 221: 220: 218: 216: 211: 203: 197: 196: 194: 192: 182: 79: 328: 327: 323: 322: 321: 319: 318: 317: 313:1968 neologisms 293: 292: 277:Secure Software 251: 246: 245: 235: 233: 229: 228: 224: 214: 212: 209: 205: 204: 200: 190: 188: 184: 183: 179: 174: 161:System accident 142: 86: 80: 67:Edsger Dijkstra 65: 50:Edsger Dijkstra 38: 22:Software crisis 17: 12: 11: 5: 326: 316: 315: 310: 305: 291: 290: 281: 267: 258: 250: 249:External links 247: 244: 243: 222: 198: 176: 175: 173: 170: 169: 168: 163: 158: 153: 148: 141: 138: 118: 117: 112: 107: 104: 101: 96: 93: 85: 82: 63: 37: 34: 15: 9: 6: 4: 3: 2: 325: 314: 311: 309: 306: 304: 301: 300: 298: 289: 285: 282: 279: 278: 272: 268: 266: 262: 261:Brian Randell 259: 256: 253: 252: 232: 226: 208: 202: 187: 181: 177: 167: 164: 162: 159: 157: 154: 152: 149: 147: 144: 143: 137: 135: 131: 127: 123: 116: 113: 111: 108: 105: 102: 100: 97: 94: 91: 90: 89: 78: 74: 73: 68: 62: 57: 55: 51: 47: 43: 33: 31: 27: 23: 19: 276: 270: 234:. Retrieved 225: 213:. Retrieved 201: 189:. Retrieved 180: 119: 87: 70: 59: 54:Turing Award 39: 21: 20: 18: 156:Fred Brooks 48:, Germany. 44:in 1968 at 297:Categories 172:References 30:complexity 146:AI winter 236:26 April 215:26 April 191:26 April 140:See also 128:such as 64:—  52:'s 1972 46:Garmisch 36:History 286:1996, 84:Causes 284:Hoare 210:(PDF) 273:in: 238:2017 217:2017 193:2017 132:and 299:: 263:: 75:, 69:, 240:. 219:. 195:.

Index

computing science
complexity
NATO Software Engineering Conference
Garmisch
Edsger Dijkstra
Turing Award
Edsger Dijkstra
The Humble Programmer (EWD340)
Communications of the ACM
Software was very inefficient
Projects were unmanageable and code difficult to maintain
Software was never delivered
processes and methodologies
software quality management
procedural programming
object-oriented programming
AI winter
List of failed and overbudget custom software projects
Fred Brooks
System accident
Technological singularity
"NATO Software Engineering Conference 1968"
"Report on a conference sponsored by the NATO SCIENCE COMMITTEE Garmisch, Germany, 7th to 11th October 1968"
"E.W.Dijkstra Archive: The Humble Programmer (EWD 340)"
Edsger Dijkstra: The Humble Programmer
Brian Randell
The NATO Software Engineering Conferences
ENISA Quarterly on Secure Software
Hoare
"How Did Software Get So Reliable Without Proof?"

Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.