Good point. What my blog entry doesn't show is that there's a layer of web controllers sitting over the top, which orchestrate calls across the components to deliver features to the user.
Aside from having a good suite of outside-in tests, how do teams currently do this? One controller per user story? One per use case?
E-mail addresses are not publicly displayed, so please only leave your e-mail address if you would like to be notified when new comments are added to this blog entry (you can opt-out later).