Testable requirements and specifications

Authors:
Jonathan S. Ostroff;Faraz Ahmadi Torshizi
Affiliations:
Department of Computer Science and Engineering, York University, Toronto, ON, Canada;Department of Computer Science and Engineering, York University, Toronto, ON, Canada
Venue:
TAP'07 Proceedings of the 1st international conference on Tests and proofs
Year:
2007

Citing 4
Cited 1

Problem frames: analyzing and structuring software development problems

Problem frames: analyzing and structuring software development problems
Fit for Developing Software: Framework for Integrated Tests (Robert C. Martin)

Fit for Developing Software: Framework for Integrated Tests (Robert C. Martin)
Beyond assertions: advanced specification and verification with JML and ESC/Java2

FMCO'05 Proceedings of the 4th international conference on Formal Methods for Components and Objects
Agile model driven development is good enough

IEEE Software

An approach to test-driven development of conceptual schemas

Data & Knowledge Engineering

Quantified Score

Hi-index	0.00

Visualization

Abstract

A design specification is the artifact intermediate between implemented code and the customer requirements. In this paper we argue that customer requirements and design specifications should be testable and testable early in the design cycle leading to early detection of requirement and specification errors. The core idea behind early testable requirements is that the problem is described before we search for a solution that can be tested against the problem description. We also want the problem description to drive the design. We provide a method for describing early testable requirements and specifications and a support tool called ESpec. ESpec allows for the description of testable requirements via Fit tables as well as testable design specifications via contracts written in Eiffel using mathematical models following the single model principle. The tool can mechanically check the requirements and specifications.