The term ‘software quality assurance’ rarely evokes much excitement. It is often perceived as a form of applied pedantry, lacking the challenge and creativity that is required to actually design and build a software system. In short, it is often seen as a necessary chore. Nobody wants to read and learn about necessary chores. To some, a book on quality assurance is about as enticing as a book on dish-washing.
Swipe to navigate through the chapters of this book
Please log in to get access to this content
To get access to this content you need the following product:
- Springer International Publishing
- Sequence number
- Chapter number
- Chapter 1