<p>This updated and reorganized Fifth edition of <b>Software Testing: A Craftsman's Approach </b>applies the strong mathematics content of previous editions to a coherent treatment of software testing. Responding to instructor and student survey input of previous editions, the authors have streamlin
Software Testing: A Craftsman's Approach
โ Scribed by Paul C. Jorgensen
- Publisher
- CRC Press
- Year
- 1995
- Tongue
- English
- Category
- Library
No coin nor oath required. For personal study only.
โฆ Synopsis
Software Testing offers a synthesis of information in the field of software testing. It brings together the two fundamental approaches-functional and structural-with numerous practical examples and exercises. The material provides the basis for making well-informed choices regarding appropriate techniques.Part I focuses on the mathematics needed to understand and correctly apply the two fundamental approaches. Parts II and III examine the functional and structural testing techniques. Part IV includes information on integration and system testing. Part V focuses on testing management.
๐ SIMILAR VOLUMES
The software development world has changed significantly in the past five years. Noteworthy among its many changes is the emergence of the ""Unified Modeling Language"" (UML) as an industry standard. While thousands of software computer professionals and students continue to rely upon the bestsellin
<p>This updated and reorganized Fifth edition of <b>Software Testing: A Craftsman's Approach </b>applies the strong mathematics content of previous editions to a coherent treatment of software testing. Responding to instructor and student survey input of previous editions, the authors have streamlin
This updated and reorganized Fifth edition of Software Testing: A Craftsman's Approach applies the strong mathematics content of previous editions to a coherent treatment of software testing. Responding to instructor and student survey input of previous editions, the authors have streamlined chapter
<P>A common problem with most texts on requirements specifications is that they emphasize structural models to the near exclusion of behavioral modelsโfocusing on what the software is, rather than what it does. If they do cover behavioral models, the coverage is brief and usually focused on a single