![](bg4.png)
Ontologies [12] and other information/knowledge science ideas can further bring
executable specifications to the business/customer world.
Lastly, it seems that over the years, the community is becoming better and better
at specifying the scope of software projects. However, this comes with losing the
user/stakeholder's true goals. This work would like to help forward the research and
practice toward closing this gap.
Acknowledgements
I would like to thank the SKY reviewers for their helpful comments.
References
1. G. Adzic. Test Driven .NET Development with FitNesse, Neuri, 2008.
2. G. Adzic. Bridging the Communication Gap: Specification by Example and Agile Accep-
tance 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-acceptance-
tests).
7. F. Brooks. The Mythical Man-Month Essays on Software Engineering, Addison-Wesley,
Anniversary 2
nd
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, Prag-
matic 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, Addison-
Wesley, 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-the-
next-level-executable-documentation/).
15. L. Koskela, Test Driven, Practical TDD and Acceptance TDD for Java Developers, Man-
ning Publications, 2007.
16. R Mugridge & W Cunningham. Fit for Developing Software: Framework for Integrated
Tests, Prentice Hall, 2005.
90