It’s more difficult (and more time consuming) to base a book around a real software project than it is to write one with a toy example. For this book, though, we thought it was important to show how DDT works on the real thing, as we expect a bit of skepticism from test-driven developers. This chapter introduces you to our example project, which we call the Mapplet 2.0, and Chapters 5–8 will show how we’ve unit tested it (at two levels of abstraction) and how we’ve done acceptance testing against use-case scenarios and against the requirements. As you can see in the chapter-opener diagram, these two levels of developer testing and two levels of independent QA testing form the core of DDT.
KeywordsDomain Model Detailed Design Sequence Diagram Domain Object Business Requirement
Unable to display preview. Download preview PDF.