I found that the Zachman Framework was inadequate for a Websited Development Lifecycle and looked for alternatives. What I found was the Bliss Classification System (BC2). Instead of six interrogatives, there are twelve. I found with little effort that I could account for all the major components of a website using this classification system.
We now had 12 swimlanes for the 6 phases.
1. Cause - The goal of using the site
2. Matter - The Data (XML)
3. Energy - The Software (Java)
4. Space - The Server (Linux)
5. Time - The scheduling of events
6. Agent - The Browsers designed for (Firefox)
7. Kind - The visual characteristics
8. Part - The graphic layout (CSS)
9. Material - The written content (XHTML)
10. Operation - How the objects behave
11. Patient - The Audiences of the website (demographics)
12. Effect - The transactions that can occur
All of these swimlanes are addressed in parallel phase by phase.
The result is a clear set of deliverables at each phase. A report of cost of each phase. And a calculation of delivered benefits after a set number of instances have occurred.