I might be misunderstanding here, but this sounds like it might lead to too much up front design, which is a trap I'm naturally inclined to fall into. Again maybe I'm misunderstanding. I found the example pretty opaque (granted I gave up trying to understand it very quickly).

I do think starting with basic architecture and design is a good idea, but it's important to jump in and test your assumptions before you become too attached to them. In my mind the ideal flow goes something like this:

1. Short design/modeling/architecture/etc session

2. Test assumptions by hacking together a quick prototype

3. Revamp design.

4. Implement more robust prototype.

5. Iterate as necessary.