“The situation is good, but not hopeless” (Polish folk wisdom) The text is devoted to the Software Analysis and Testing (SAT) methods and s- porting tools for assessing and, if possible, improving software quality, specifically its correctness. The term quality assurance is avoided for it is this author’s firm belief that in the current state of the art that goal is unattainable, a plethora of “gu- anteed” solutions to the problem notwithstanding. Therefore, the rather awkward phrase “improving correctness” is to be understood as an effort to minimize the number of residual programming faults (“bugs”) and their impact on the software’s behavior, that is, to make the faults tolerable. It is clear that such a minimalist approach is a result of frustration. Indeed, having spent years developing software and teaching (preaching?) “How to do it right,” I still do not know how to go about it with any degree of certainty! It appears then I probably should stop right now, for who with a modicum of common sense would reach for a text that does not offer salvation but (as will be seen) hard work and misery? If I intend to continue, it is only that I suspect there are many professionals out there who have similar doubts. And they are the intended audience of this project. The philosophical underpinning of the text is the importance of sound engine- ing practices in software development.
Laski / Stanley
Software Verification and Analysis jetzt bestellen!
Zielgruppe
Professional/practitioner
Weitere Infos & Material
The Semantic Analysis.- Why Not Write Correct Software the First Time?.- How to Prove a Program Correct: Programs Without Loops.- How to Prove a Program Correct: Iterative Programs.- Prepare Test for Any Implementation: Black-Box Testing.- Static Analysis.- Intermediate Program Representation.- Program Dependencies.- What Can One Tell About a Program Without Its Execution: Static Analysis.- Dynamic Analysis.- Is There a Bug in the Program? Structural Program Testing.- Dynamic Program Analysis.
