So far, we have coded a few of our requirements from front to back. We built the view layer using CherryPy. Next, we configured security to protect the site. Then we fully implemented one of the customer features so that it stored new accounts in the database.
Coding more features follows a similar pattern. The order the steps are executed are a matter of taste. It is possible to code the entire back end using automated testing, followed by skinning it with a web layer. In our case, we used the more demonstrative style of building the interface first, and then fleshing out the backend later. Either way, it is easy to iterate through and see how Spring Python's IoC container kept the security, view, and controller logic nicely decoupled.
Now let's fast forward development to the point where all the customer features are implemented.