Test-driven global software development

In a global software development project, distributed teams need to have a consistent view of the system even in the face of frequently changing requirements. Thus how precisely requirements and changes therein are communicated to remote developers becomes a critical issue. In this position paper, we hypothesize that a test-driven methodolog y may help keep development across multiple sites consistent with changing requirements and with each other.

[1]  Audris Mockus,et al.  Distance, dependencies, and delay in a global collaboration , 2000, CSCW '00.

[2]  Laurie A. Williams,et al.  Assessing test-driven development at IBM , 2003, 25th International Conference on Software Engineering, 2003. Proceedings..

[3]  Albert L. Baker,et al.  JML: A Notation for Detailed Design , 1999, Behavioral Specifications of Businesses and Systems.

[4]  Bertrand Meyer,et al.  Eiffel: The Language , 1991 .

[5]  MeyerBertrand,et al.  Design by Contract , 1997 .

[6]  Phyllis G. Frankl,et al.  The ASTOOT approach to testing object-oriented programs , 1994, TSEM.

[7]  Kent L. Beck,et al.  Test-driven Development - by example , 2002, The Addison-Wesley signature series.

[8]  Anneke Kleppe,et al.  The object constraint language: precise modeling with UML , 1998 .