http://blogs.msdn.com/agile/archive/tags/fit/default.aspxTags: fiten-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/agile/archive/2008/01/22/tests-and-requirements-requirements-and-tests-a-m-bius-strip.aspxWed, 23 Jan 2008 00:43:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:7202166gmelnik4http://blogs.msdn.com/agile/comments/7202166.aspxhttp://blogs.msdn.com/agile/commentrss.aspx?PostID=7202166<P class=MsoNormal style="MARGIN: 0in 0in 10pt"><FONT face=Calibri size=3>Over a year ago, <A class="" title=http://blog.objectmentor.com/articles/category/uncle-bobs-blatherings href="http://blog.objectmentor.com/articles/category/uncle-bobs-blatherings" mce_href="http://blog.objectmentor.com/articles/category/uncle-bobs-blatherings">Robert&nbsp;Martin</A> and I wrote a paper&nbsp;</FONT><FONT face=Calibri size=3>on exploring and disambiguating requirements with acceptance tests. In it we formulate the <EM>equivalence hypothesis</EM> - as formality increases, acceptance tests and requirements become indistinguishable. At the limit, acceptance tests and requirements are equivalent. IEEE Software magazine published it in the January/February’08 issue (<A href="http://www.computer.org/portal/cms_docs_software/software/homepage/2008/s1mel.pdf"><FONT face=Calibri size=3>http://www.computer.org/portal/cms_docs_software/software/homepage/2008/s1mel.pdf</FONT></A><FONT face=Calibri size=3>)</FONT>. </FONT></P> <P class=MsoNormal style="MARGIN: 0in 0in 10pt"><FONT face=Calibri size=3>As usual, comments are welcomed. </FONT></P><img src="http://blogs.msdn.com/aggbug.aspx?PostID=7202166" width="1" height="1">articlesagilefitacceptance tests