The inevitable pain of software development: Why there is no silver bullet (2004)
Cached
Download Links
- [se.math.uwaterloo.ca]
- [se.uwaterloo.ca]
- [se.math.uwaterloo.ca]
- [se.uwaterloo.ca]
- DBLP
Other Repositories/Bibliography
by
Daniel M. Berry
| Venue: | In RISSEF |
| Citations: | 7 - 2 self |
BibTeX
@INPROCEEDINGS{Berry04theinevitable,
author = {Daniel M. Berry},
title = {The inevitable pain of software development: Why there is no silver bullet},
booktitle = {In RISSEF},
year = {2004},
pages = {50--74},
publisher = {Springer}
}
Bookmark
 |
 |
 |
 |
 |
 |
OpenURL
Abstract
Abstract. A variety of programming accidents, i.e., models, methods, artifacts, and tools, are examined to determine that each has a step that programmers find very painful. Consequently, they habitually avoid or postpone the step. This pain is generally where the programming accident meets requirements, the essence of software, and their relentless volatility. Hence, there is no silver bullet.
