---
title: "Shortcomings of software development models"
subject: "Instrumentation II"
chapter: 9
key: "semester_5/instrumentation_ii:sw-model-shortcomings"
source: https://www.bctengineer.com/q/semester_5/instrumentation_ii/sw-model-shortcomings
site: BCT Engineering
---

# Shortcomings of software development models

Instrumentation II · Chapter 9: Software For Instrumentation And Control Applications

- Asked in: 2074 Asoj, 5 marks
- Answer checked by Claude Sonnet 5.5 on 2026-10-14
- Page: https://www.bctengineer.com/q/semester_5/instrumentation_ii/sw-model-shortcomings
- Whole chapter: https://www.bctengineer.com/md/semester_5/instrumentation_ii/chapter-9

## Question

Discuss the shortcomings of existing software development models, and suggest measures to overcome them.

## Short answer

Waterfall is rigid, prototyping can confuse and cost, spiral is complex. Overcome with hybrid iterative-incremental models, agile practices, early validation, continuous integration, risk management, and automated testing.

## Answer

#### Shortcomings of existing models
- **Waterfall:** rigid and sequential; requirements must be fixed at the start; a working product appears late; errors found late are expensive; poor for changing requirements.
- **Prototyping:** the customer may confuse the prototype with the final product; quick-and-dirty design; unplanned iterations raise cost and time; poor documentation.
- **Spiral:** needs expert risk analysis; costly and complex to manage; not suitable for small, low-risk projects; hard to define end of the loops.
- **General:** weak customer involvement during development, heavy documentation, difficulty of estimating, insufficient support for reuse and for hardware/software co-design in embedded systems.

#### Measures to overcome them
1. **Hybrid or iterative-incremental approach:** a waterfall-style plan for stable parts, with prototyping for unclear parts and spiral-style risk analysis for critical parts; deliver in increments.
2. **Agile practices:** short iterations, continuous customer feedback, frequent builds and adaptive planning.
3. **Early validation:** requirement reviews, prototypes of user interface, simulation.
4. **Risk management** from the start, with regular reviews.
5. **Configuration and change control** to manage changes; maintain essential documentation and traceability.
6. **Continuous integration and automated testing** to find bugs early; reuse of tested components.

## Check yourself

The answer's key points as multiple-choice questions, with the correct option and why.

1. Main shortcoming of Waterfall?
   A. Rigid and sequential, working product appears late
   B. Needs constant risk analysis
   C. Prototype mistaken for final product
   D. Too many loops
   Answer: A. Waterfall requires fixed requirements and late results. (Key point: Waterfall weakness)

2. A shortcoming of prototyping?
   A. Requirements must be fixed first
   B. Customer may confuse the prototype with the final product
   C. Expert risk analysis is needed
   D. Product appears very late
   Answer: B. Prototyping can give quick-and-dirty design with poor documentation. (Key point: Prototyping weakness)

3. Spiral model needs what?
   A. No risk analysis
   B. Only small low-risk projects
   C. Expert risk analysis and is costly
   D. Fixed requirements
   Answer: C. Spiral is complex and not suited to small low-risk projects. (Key point: Spiral weakness)

4. How can the shortcomings be reduced?
   A. Use only waterfall
   B. Remove documentation fully
   C. Avoid customer feedback
   D. Hybrid iterative-incremental approach with agile practices and early validation
   Answer: D. Combining models and early feedback addresses weaknesses. (Key point: Overcoming)

## Related in Instrumentation II

- [Software process models and effort estimation](https://www.bctengineer.com/question.md?key=semester_5%2Finstrumentation_ii%3Asw-process-models) — Instrumentation II, chapter 9, asked 2×
- [Compare software models; propose a fourth model](https://www.bctengineer.com/question.md?key=semester_5%2Finstrumentation_ii%3Asw-models-compare-fourth) — Instrumentation II, chapter 9
- [Spiral model of software development](https://www.bctengineer.com/question.md?key=semester_5%2Finstrumentation_ii%3Aspiral-model) — Instrumentation II, chapter 9, asked 3×
- [Software testing time paradox](https://www.bctengineer.com/question.md?key=semester_5%2Finstrumentation_ii%3Asw-testing-paradox) — Instrumentation II, chapter 9
- [Prototyping model of software](https://www.bctengineer.com/question.md?key=semester_5%2Finstrumentation_ii%3Aprototype-model) — Instrumentation II, chapter 9, asked 3×

## Related in other subjects

- [Software reliability and reliability models](https://www.bctengineer.com/question.md?key=semester_5%2Fsoftware_engineering%3Areliability-models) — Software Engineering, chapter 9, asked 2×
- [Embedded software development process](https://www.bctengineer.com/question.md?key=semester_6%2Fembedded_system%3Asoftware-development-flow) — Embedded System, chapter 3, asked 3×
- [Why software development is complex; man-month myth](https://www.bctengineer.com/question.md?key=semester_5%2Fsoftware_engineering%3Acomplex-development) — Software Engineering, chapter 1
- [Common business models of startups](https://www.bctengineer.com/question.md?key=semester_7%2Fentrepreneurship_development%3Adifferent-business-models) — Entrepreneurship Development, chapter 4