--- title: "Software crisis" subject: "Software Engineering" chapter: 1 key: "semester_5/software_engineering:software-crisis" source: https://www.bctengineer.com/q/semester_5/software_engineering/software-crisis site: BCT Engineering --- # Software crisis Software Engineering · Chapter 1: Software Process and requirements - Asked in: 2068 Chaitra, 5 marks - Video: [Software Crisis | Software Engineering | SE | Lec-02 | Bhanu Priya](https://www.youtube.com/watch?v=soNnQjJ6FBQ) — Education 4u - Answer checked by Claude Sonnet 5.5 on 2026-10-14 - Page: https://www.bctengineer.com/q/semester_5/software_engineering/software-crisis - Whole chapter: https://www.bctengineer.com/md/semester_5/software_engineering/chapter-1 ## Question What is software crisis? Explain with the help of an example. ## Short answer Software crisis refers to the chronic problems of projects exceeding budget and schedule, delivering unreliable software that fails to meet user needs, and being hard to maintain, while demand outpaces development capacity. For example, the London Ambulance Service dispatch system (1992) went live with incomplete requirements and load testing, causing lost calls and delayed ambulances, forcing a return to manual operation. ## Answer **Software crisis** is the term used (first at the 1968 NATO Software Engineering Conference) for the situation in which software projects regularly ran over budget, finished late, failed to meet user needs and were unreliable and hard to maintain, while the demand for new and larger software grew much faster than the ability to build it. #### Symptoms of the software crisis - Projects run **over budget** and **behind schedule**. - Delivered software **does not meet the user's real requirements**. - Software is of **low quality**: many bugs, crashes, poor performance. - Code is **difficult to maintain**, modify or extend. - Many projects are **cancelled** or never used after delivery. - Developer **productivity does not keep pace** with demand, so there is a large backlog of software waiting to be built. #### Main causes 1. Rapid growth in the **size and complexity** of software. 2. **Unclear and changing requirements**; poor communication between users and developers. 3. **Poor estimation** of cost and time, and weak project management. 4. Use of an informal "code-and-fix" approach instead of a **systematic process**. 5. **Inadequate testing** and quality assurance. 6. Lack of trained people and of standards and tools. #### Example The **London Ambulance Service Computer-Aided Dispatch (LASCAD)** system (1992) was meant to automate the allocation of ambulances to emergency calls. It was built on a very tight schedule, with incomplete requirements, little user involvement and incomplete load testing. Soon after it went live it could not cope with the real call volume: calls were lost or duplicated, ambulances were sent late or to wrong places, and patients waited far longer than normal. Within days the service had to go back to a largely manual system. The project was late, over budget, unreliable and did not meet its users' needs, which shows every symptom of the software crisis. A smaller, familiar example: a college result-processing system that is delivered months late, gives wrong grade totals because a rule was misunderstood, and needs costly rework every year when the grading rules change. #### Response The software crisis led to **software engineering**: a systematic, disciplined and measurable approach to developing software, using process models, proper requirements engineering, design methods, testing, quality management and configuration management. ## Check yourself The answer's key points as multiple-choice questions, with the correct option and why. 1. Which situation best describes the software crisis? A. Hardware became too expensive for companies to buy B. Projects ran over budget and late, were unreliable and hard to maintain, while demand grew faster than the ability to build software C. Programmers refused to document their code D. Software was produced too quickly and flooded the market Answer: B. The crisis was the combination of late, over-budget, unreliable, hard-to-maintain software and demand outgrowing development capacity. (Key point: Meaning of software crisis) 2. Which of the following is a symptom of the software crisis? A. Delivered software does not meet the user's real requirements B. Software is delivered far ahead of schedule C. Developer productivity exceeds demand, leaving no backlog D. Maintenance is easy because code is well structured Answer: A. Failing to meet real user requirements, along with delays, overruns, low quality and poor maintainability, is a classic symptom. (Key point: Symptoms) 3. Which is one of the main causes of the software crisis? A. Too much testing and quality assurance B. Clear and fixed requirements C. Using an informal code-and-fix approach instead of a systematic process D. Over-qualified and well-trained staff Answer: C. Code-and-fix development, together with poor estimation, changing requirements and inadequate testing, causes the crisis. (Key point: Causes) 4. In the London Ambulance Service (LASCAD) example, what went wrong after the system went live? A. It was too secure for dispatchers to use B. It was cancelled before any coding began C. It was completed far ahead of schedule but never installed D. It could not cope with real call volume, so calls were lost or duplicated and the service reverted to manual working Answer: D. Tight schedule, incomplete requirements and incomplete load testing led to failure under real load and a return to a manual system. (Key point: Example: LASCAD) ## Related in Software Engineering - [Software characteristics and software crisis](https://www.bctengineer.com/question.md?key=semester_5%2Fsoftware_engineering%3Acharacteristics-and-crisis) — Software Engineering, chapter 1