Skip to content

Testing in Software Development

Spend $50 to get a free movie!

ISBN-10: 0521337860

ISBN-13: 9780521337861

Edition: 1986

Authors: Martyn A. Ould, Charles Unwin

List price: $35.99
Blue ribbon 30 day, 100% satisfaction guarantee!
Out of stock
what's this?
Rush Rewards U
Members Receive:
Carrot Coin icon
XP icon
You have reached 400 XP and carrot coins. That is the daily max!

Description:

With the increasing application of software in systems, especially safety- or even life-critical systems, it is no longer sufficient for the software developer to rely solely on testing the code produced. Testing must begin with the specification of requirements, continue on the design and finally on the implemented system. This book gives guidance on how testing can be carried out at each of the stages of software development. It does this by looking at the development process from four viewpoints: that of the intended user of the system, of its designers, of its programmers, and of the manager responsible for development. The product of each stage of development is individually examined…    
Customers also bought

Book details

List price: $35.99
Copyright year: 1986
Publisher: Cambridge University Press
Publication date: 12/18/1986
Binding: Paperback
Pages: 136
Size: 6.25" wide x 9.25" long x 0.50" tall
Weight: 0.330
Language: English

BONNIE KIME SCOTT is Professor of English and Women's Studies at the University of Delaware. She is the author of Joyce and Feminism, James Joyce, and New Alliances in Joyce Studies; she is the editor of The Gender of Modernism. She is editing the letters of Rebecca West.

Preface
Introduction
The Manager's View of Testing
The need to manage testing
Management's role
Why are there errors in software?
Three key ideas
An eight-point programme for managers
A model of the software development process
The four views of testing
Introduction
The manager's view
The user's view
The designer's view
The programmer's view
System development and testing
Introduction
Static testing
Dynamic testing
Testability
Verification and validation
Translating the life-cycle diagram into a project plan
Change management
Configuration management
Change control
Version control
Record-keeping and traceability
Special management concerns in testing
Educating staff
Contractual requirements and testing objectives
Establishing a budget for testing
Planning the tests
Establishing a method
Starting early
Testing through the life of the system
Measurement and data collection
The User's View of Testing
Introduction
Testing the Requirements Expression
Introduction
Criteria for testing a Requirements Expression
Techniques for testing a Requirements Expression
Testing the System Specification
Introduction
How does one test a System Specification?
Qualifying a System Specification
Validating a System Specification
The ideal form of a System Specification
Testing the System for Trial
Introduction
The Acceptance Test
Testing functional statements
Testing constraints
Testing attributes
The format of an Acceptance Test Plan
Testing an Acceptance Test
The Designer's View of Testing
The system design process
Testing the design
What to test for in a system design
Test methods for a system design
Integration testing
Introduction
The scope of integration
The objectives of integration
The organisation of integration
The Integration Test Plan
Integration Test Specifications
Test software
System testing
The Programmer's View of Testing
Introduction
Testing the Module Specification
Introduction
Testing the quality of the Module Specification
Verification of the Module Specification
Testing the Unit Test Plan
Introduction
Checking the quality of the Unit Test Plan
Requirements-directed generation of test data
Design-directed generation of test data
Unit Testing
Introduction
Checking the quality of coded units
Verification of coded units
Supporting techniques
Bibliography
Index