Communicating Domain Knowledge in Executable Acceptance Test Driven Development
暂无分享,去创建一个
[1] Kent L. Beck,et al. Extreme programming explained - embrace change , 1990 .
[2] Shari Lawrence Pfleeger,et al. Software Metrics : A Rigorous and Practical Approach , 1998 .
[3] Evans,et al. Domain-driven design , 2003 .
[4] Jacques Philippe Sauvé,et al. Teaching software development with ATDD and easyaccept , 2008, SIGCSE '08.
[5] Grigori Melnik,et al. The practice of specifying requirements using executable acceptance tests in computer science courses , 2005, OOPSLA '05.
[6] N. Hoffart. Basics of Qualitative Research: Techniques and Procedures for Developing Grounded Theory , 2000 .
[7] Natalia Juristo Juzgado,et al. Basics of Software Engineering Experimentation , 2010, Springer US.
[8] CEM KANER ON SCENARIO TESTING The Power of “ What If . . . ” and Nine Ways to Fuel Your Imagination , .
[9] Mike Chiasson,et al. Executable acceptance tests for communicating business requirements: customer perspective , 2006, AGILE 2006 (AGILE'06).
[10] Grigori Melnik,et al. Student experiences with executable acceptance testing , 2005, Agile Development Conference (ADC'05).
[11] Grigori Melnik,et al. Empirical analyses of executable acceptance test driven development , 2007 .
[12] Frank Maurer,et al. Scaling Agile Methodologies for Developing a Production Accounting System for the Oil & Gas Industry , 2007, Agile 2007 (AGILE 2007).