One strategy for assuring testable software is to assure testable requirements, i.e., requirements that are clearly and precisely specified and cost-effectively checkable. David Gelperin describes two specification techniques, action contracts and Planguage quality specs, which both support testable requirements. Functionality can be precisely defined with pre- and post-conditions using action contracts. The measurement of non-functional characteristics can be precisely specified with Planguage specs. The techniques will be illustrated with examples and short exercises.
- An application information architecture that assures testability
- How to specify functions with action contracts
- How to specify measures for nonfunctional characteristics