I have not clear where to start coding a story in a web project.
I focus first on the presentation layer?
or in the business layer?
I have read in a TDD book that the business layer should be the first, then the persistence, and finally the presentation.
But I have also seen projects where they first show the client a prototype web pages.
The ATDD says that you first code the acceptance tests, then the funcionality.
I unconsciously start imaging the appearance of the web page. So where to start?
I'd like to know about your experiences
Joined: Oct 15, 2010
In the book "Agile Java Development with Spring, Hibernate and Eclipse", 2006, the author
explains with an example the complete end-to-end agile proces: from user up to implementation. The steps he folllows are:
1. define domain model (i.e. model classes) and build UI prototype
2. define user stories
3. create application flow map
4. create CRC cards
5. create UML diagram
6. define directory struture
7. test and implement model classes
8. test and implement controller classes
I'like to know if you follow this process to implemente the user stories.