Solid Software: Is It Rocket Science?
Over the years, software engineers have created and applied many technologies to monitor and improve the quality of the software we produce. At the same time, the demands on that software have been increasing: our clients want better and predictable software for less cost in shorter time frames. This presentation will present several techniques for producing “solid software”: software that is reliable, predictable and easy to maintain. We will explore whether these techniques are enough to guarantee high quality every time.
KeywordsAttack Missile Missile Defense Predictable Software Solid Software Missile Defense System
Unable to display preview. Download preview PDF.
- 1.Bruce G. Blair, “Nukes: A lesson from Russia”, Washington Post, Wednesday, July 11, 2001, page A19.Google Scholar
- 2.Edsger W. Dijkstra, “The end of computing science?” Communications of the ACM, 44(3), March 2001, page 92.Google Scholar
- 3.John Knight and Nancy Leveson (1986). “An empirical study of failure probabilities in multi-version software”. In Digest of the Sixteenth International Symposium on Fault-tolerant Computing, pp. 165–70. Los Alamitos, CA: IEEE Computer Society Press.Google Scholar
- 5.Peter G. Neumann and David L. Parnas, “Computers: Boon or bane?” Communications of the ACM, 44(3), March 2001, page 168.Google Scholar
- 6.Shari Lawrence Pfleeger, Les Hatton and Charles C. Howell, Solid Software, Prentice Hall, Upper Saddle River NJ, 2001.Google Scholar
- 7.Burton Richter, “It doesn’t take rocket science; to test missile defense, start with basic math”, Washington Post, Sunday, July 23, 2000, page B2.Google Scholar