| 000 | 01759nam a2200361Ia 4500 | ||
|---|---|---|---|
| 005 | 20260803094046.0 | ||
| 008 | 251212s2009 xx 000 0 und d | ||
| 245 | 1 |
_aSoftware verification and analysis : _ban integrated, hands-on approach / _cJanusz Laski. |
|
| 100 | _aLaski, Janusz | ||
| 700 | _aStanley, William | ||
| 260 |
_aNew York : _bSpringer, _c2009. |
||
| 300 | _axviii, 224 p.: | ||
| 300 | _c24 cm. | ||
| 500 | _aIncludes bibliographic references and index | ||
| 020 | _a978-1-84882-239-9 | ||
| 650 |
_aComputer software _xVerification |
||
| 650 | _aComputer science | ||
| 650 | _aSoftware engineering | ||
| 050 | _a005.14 L33s | ||
| 943 |
_b0 _c0 _d0 _e1 _f0 _g0 _h0 _i0 _j0 |
||
| 944 |
_b1 _c1 _d0 |
||
| 953 | _pHED2586 | ||
| 546 | _aEnglish | ||
| 953 | _cCollLib | ||
| 505 | _aPreface.- Introduction: What Do We Want to Know About the Program.- 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.- Intermediate Program Representation.- Program Dependencies.- What Can One Tell about a Program Without Its Execution: Static Analysis.- Is there a Bug in the Program?- Structural Program Testing.- Dynamic Program Analysis.- Index. | ||
| 520 | _aThis book addresses the most important techniques in improving the correctness of software, including correctness by construction, program proving, static analysis and dynamic, execution-based analysis. Problems and exercises are included. | ||
| 591 | _a0 | ||
| 336 | _aText | ||
| 337 | _aUnmediated | ||
| 338 | _aVolume | ||
| 942 |
_2lcc _cBK _arizal _b2015-04-07 23:18:18 _drizal _e2015-04-07 23:18:18 |
||
| 998 | _a3428 | ||
| 999 |
_c3415 _d3415 |
||