And there are other important development products besides code. To be sure that
the code solves the right problem, we must have a specification that describes what
we want the program to do. To be sure that the units of code will work together, we
need a design that describes how the program is built up from parts and how the
parts communicate. If the specification or design turns out to be wrong, code may
have to be reworked or discarded, so many projects conduct reviews or inspections
where people examine specifications and designs. These are usually expressed in
informal notations such as natural language and hand-drawn diagrams that cannot be
analyzed automatically, so reviews and inspections are time-consuming, subjective,
and fallible.
In this book we teach novel solutions to these problems: expressing and checking
specifications and designs, generating test cases, and checking the results of test
runs. The methods we describe increase the automation in each of these activities,
so they can be more timely, more thorough, and (we expect) more effective.
1 Definitions for terms that are printed in italics where they first appear are collected in the
Glossary (Appendix C).
3
4 Describe, Analyze, Test
We also teach a technology that realizes these solutions: the NModel modeling
and testing framework, a library and several tools (applications) built on the C#
language and .
Pages:
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27