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. © Springer-Verlag Berlin Heidelberg 2004.
Cite
CITATION STYLE
Berry, D. M. (2004). The inevitable pain of software development: Why there is no silver bullet. Lecture Notes in Computer Science (Including Subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics), 2941, 50–74. https://doi.org/10.1007/978-3-540-24626-8_4
Register to see more suggestions
Mendeley helps you to discover research relevant for your work.
