Can Executable Specifications Close the Gap between Software Requirements and Implementation?

Reuven Yagel

Abstract

This paper reviews some of the techniques which are considered executable specifications. It explains why, in spite of their apparent benefit, they did not become an industry mainstream (yet) and what might be done about it. At last several future directions, research plans and suggestions are drawn.

References

  1. G. Adzic. Test Driven .NET Development with FitNesse, Neuri, 2008.
  2. G. Adzic. Bridging the Communication Gap: Specification by Example and Agile Acceptance Testing, Neuri, 2009.
  3. G. Adzic. Specification by Example - How Successful Teams Deliver the Right Software, Manning, 2011.
  4. K. Beck. Test Driven Development: By Example, Addison-Wesley, 2002.
  5. E. V. Berard. Essays on Object-Oriented Software Engineering, Prentice Hall, 1992 (see: http://www.softwarequotes.com/showquotes.aspx?id=613).
  6. M. Bria. "Jim Shore Suggests Automated Acceptance Tests Are Not The Right Move". Infoq article, 2010 (see: http://www.infoq.com/news/2010/04/dont-automate-acceptancetests).
  7. F. Brooks. The Mythical Man-Month Essays on Software Engineering, Addison-Wesley, Anniversary 2nd edition, 1995.
  8. D. Chelimsky, D. Astels, Z. Dennis, A. Helles√ły, B. Helmkamp, and Dan North. The RSpec Book: Behaviour-Driven Development with RSpec, Cucumber, and Friends, Pragmatic Programmer, 2010.
  9. J. Coplien and B. Martin. "Coplien and Martin Debate TDD, CDD and Professionalism", infoq interview, 2008. (see: http://www.infoq.com/interviews/coplien-martin-tdd).
  10. A. Elssamadisy. "Automated Acceptance Tests - Theoretical or Practical", infoq article, 2009, (see: http://www.infoq.com/news/2009/06/automated-acceptance-tests).
  11. S. Freeman and N. Pryce. Growing Object-Oriented Software, Guided by Tests, AddisonWesley, 2009.
  12. Gartner, Predicts 2010: Agile and Cloud Impact Application Development Directions, Gartner, 2009.
  13. T. R. Gruber. "Toward principles for the design of ontologies used for knowledge sharing", Padua workshop on Formal Ontology, 1993, and International Journal of Human-Computer Studies, Vol. 43, Issues 4-5, 1995.
  14. Keithps. "Taking executable specs to the next level: Executable Documentation", Blog post, 2011, (see: http://keithps.wordpress.com/2011/06/26/taking-executable-specs-to-thenext-level-executable-documentation/).
  15. L. Koskela, Test Driven, Practical TDD and Acceptance TDD for Java Developers, Manning Publications, 2007.
  16. R Mugridge & W Cunningham. Fit for Developing Software: Framework for Integrated Tests, Prentice Hall, 2005.
  17. D. North. Introducing Behaviour Driven Development, (see: introducing-bdd/).
  18. Selenium. SeleniumHW Web Application Test System. http://seleniumhq.org/
  19. Standish Group, "CHAOS Report.", Standish Group, 1994.
  20. Watir, Automated testing that doesn't hurt, http://watir.com/.
Download


Paper Citation


in Harvard Style

Yagel R. (2011). Can Executable Specifications Close the Gap between Software Requirements and Implementation? . In Proceedings of the 2nd International Workshop on Software Knowledge - Volume 1: SKY, (IC3K 2011) ISBN 978-989-8425-82-9, pages 87-91. DOI: 10.5220/0003698800870091


in Bibtex Style

@conference{sky11,
author={Reuven Yagel},
title={Can Executable Specifications Close the Gap between Software Requirements and Implementation?},
booktitle={Proceedings of the 2nd International Workshop on Software Knowledge - Volume 1: SKY, (IC3K 2011)},
year={2011},
pages={87-91},
publisher={SciTePress},
organization={INSTICC},
doi={10.5220/0003698800870091},
isbn={978-989-8425-82-9},
}


in EndNote Style

TY - CONF
JO - Proceedings of the 2nd International Workshop on Software Knowledge - Volume 1: SKY, (IC3K 2011)
TI - Can Executable Specifications Close the Gap between Software Requirements and Implementation?
SN - 978-989-8425-82-9
AU - Yagel R.
PY - 2011
SP - 87
EP - 91
DO - 10.5220/0003698800870091