Testing in Software Development

Front Cover
Cambridge University Press, Dec 18, 1986 - Computers - 124 pages
1 Review
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 to see how it can be checked for correctness and consistency with earlier specifications. References are given to techniques available to the software developer and there are many helpful checklists. The contributors are all members of the British Computer Society's Working Group on Testing, and between them have an impressive breadth of practical experience in the commercial development of small and large software systems. Their combined experience makes this a most valuable book for the computing professional.
 

What people are saying - Write a review

We haven't found any reviews in the usual places.

Contents

Introduction
1
The Managers View of Testing
4
212 Why are there errors in software?
5
214 An eightpoint programme for managers
6
23 The four views of testing
8
232 The managers view
9
233 The users view
10
235 The programmers view
11
34 Testing the System for Trial
53
342 The Acceptance Test
54
344 Testing constraints
55
345 Testing attributes
56
347 Testing an Acceptance Test
57
The Designers View of Testing
59
42 Testing the design
61
422 Test methods for a system design
63

243 Dynamic testing
13
244 Testability
16
245 Verification and validation
17
246 Translating the lifecycle diagram into a project plan
18
25 Change management
19
252 Change control
20
253 Version control
21
26 Special management concerns in testing
22
262 Contractual requirements and testing objectives
23
264 Planning the tests
24
265 Establishing a method
25
267 Testing through the life of the system
26
The Users View of Testing
28
32 Testing the Requirements Expression
30
322 Criteria for testing a Requirements Expression
31
323 Techniques for testing a Requirements Expression
37
33 Testing the System Specification
41
334 Validating a System Specification
46
335 The ideal form of a System Specification
52
43 Integration testing
69
432 The scope of integration
71
434 The organisation of integration
72
435 The Integration Test Plan
73
436 Integration Test Specifications
75
437 Test software
79
44 System testing
82
The Programmers View of Testing
88
52 Testing the Module Specification
89
522 Testing the quality of the Module Specification
90
523 Verification of the Module Specification
96
53 Testing the Unit Test Plan
97
534 Designdirected generation of test data
99
54 Unit testing
103
543 Verification of coded units
109
544 Supporting techniques
111
Bibliography
113
Index
118
Copyright

Common terms and phrases

References to this book

Software Reliability Handbook
Rook
Limited preview - 1990
All Book Search results »

About the author (1986)

About the author Martyn A. Ould read mathematics at Cambridge University, entered the software industry directly, and worked for several years on operating systems. In 1985 he joined Praxis where he is now Quality and Technical Director. His interests centre on methods and lifecycles and he has had three books published-A Practical Handbook for Software Development, Testing in Software Development; and Strategies for Software Engineering. In recent years he has been leading Praxis's work in the field of business process modelling, including undertaking consultancy assignments for major clients. He is a Fellow of the British Computer Society and a Chartered Engineer. His interest in books extends to running his own private press-The Old School Press-where he prints and publishes using metal type and traditional hand processes for illustration and binding. About Praxis Praxis is the software engineering company of Touche Ross Management Consultants. Its services include the modelling of business processes as part of business improvement.