This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Tests and Requirements, Requirements and Tests: A M?bius Strip
January/February 2008 (vol. 25 no. 1)
pp. 54-59
ASCII Text
x 
 
Robert C. Martin, Grigori Melnik, "Tests and Requirements, Requirements and Tests: A M?bius Strip," IEEE Software, vol. 25, no. 1, pp. 54-59, January/February, 2008.
 
 
BibTex
x
 
@article{ 10.1109/MS.2008.24,
author = {Robert C. Martin and Grigori Melnik},
title = {Tests and Requirements, Requirements and Tests: A M?bius Strip},
journal ={IEEE Software},
volume = {25},
number = {1},
issn = {0740-7459},
year = {2008},
pages = {54-59},
doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2008.24},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - MGZN
JO - IEEE Software
TI - Tests and Requirements, Requirements and Tests: A M?bius Strip
IS - 1
SN - 0740-7459
SP54
EP59
EPD - 54-59
A1 - Robert C. Martin,
A1 - Grigori Melnik,
PY - 2008
KW - acceptance testing
KW - requirements engineering
KW - executable specification
KW - FIT
KW - Framework for Integrated Testing
KW - FitNesse
VL - 25
JA - IEEE Software
ER -
 
Robert C. Martin, Object Mentor Inc.
Grigori Melnik, University of Calgary and Microsoft
Writing acceptance tests early is a requirements-engineering technique that can save businesses time and money and help them better respond to change. An equivalence hypothesis states that concrete requirements blend with acceptance tests so that you should be able to specify and verify system behavior using tests. Several examples in the FIT (Framework for Integrated Testing) demonstrate the approach.

1. D. Gause and G. Weinberg, Exploring Requirements, Dorset House, 1989, p. 249.
2. D. Graham, "Requirements and Testing: Seven Missing-Link Myths," IEEE Software, vol. 19, no. 5, 2002, pp. 15–17.
3. B. Hetzel, The Complete Guide to Software Testing, QED Information Sciences, 1983.
4. G. Meszaros, "Agile Regression Testing Using Record &Playback," Companion of the 18th Ann. ACM SIGPLANConf. Object-Oriented Programming, Systems, Languages, and Applications (OOPSLA03), ACM Press, 2003, pp. 353–360.
5. R. Janicki, D. Parnas, and J. Zucker, Tabular Representations in Relational Documents, Communications Research Laboratory, McMaster University, 1995, p. 5.
6. R. Mugridge and W. Cunningham, Fit for Developing Software, Prentice Hall, 2005.
7. I. Alexander and N. Maiden, Scenarios, Stories, Use Cases through the Systems Development Life-Cycle, John Wiley &Sons, 2004, p. 5.
8. C. Potts, K. Takahashi, and A. Antón, "Inquiry-Based Requirements Analysis," IEEE Software, vol. 11, no. 2, 1994, pp. 21–32.
9. G. Melnik, F. Maurer, and M. Chiasson, "Executable Acceptance Tests for Communicating Business Requirements: Customer Perspective," Proc. Agile 2006 Conf., IEEE CS Press, 2006, pp. 35–46.
10. C. Kaner, "On Scenario Testing," Software Testing and Quality Eng. Magazine, Sept./Oct. 2003, pp. 16–22.
11. E. Evans, Domain-Driven Design: Tackling Complexity in the Heart of Software, Addison-Wesley, 2004, p. 376.
12. K. Weidenhaupt t al., "Scenarios in System Development: Current Practice," IEEE Software, vol. 15, no. 2, 1998, pp. 34–45.
13. M. Fowler, "Continuous Integration," www.martinfowler.com/articlescontinuousIntegration.html , May 2006.

Index Terms:
acceptance testing, requirements engineering, executable specification, FIT, Framework for Integrated Testing, FitNesse
Citation:
Robert C. Martin, Grigori Melnik, "Tests and Requirements, Requirements and Tests: A M?bius Strip," IEEE Software, vol. 25, no. 1, pp. 54-59, Jan.-Feb. 2008, doi:10.1109/MS.2008.24
Usage of this product signifies your acceptance of the Terms of Use.