Email: anthony@handaweb.com

Go to Site Map

Return to HandaWeb Home

 

 

Learn more about Anthony

Go to Project Portfolio

Go to the Photo Gallery

Go to the Comedy Lounge

Read some of Anthony's Tales from the Rice Paddy

Read some articles from the Iwate Pre-Departure Handbook

Credit where due & some cool Links

 

E-Marketplace Case Study
Wireframe Tracker
Spring 2001

 

Background

  • Tool: Microsoft Excel
  • Input: Site Map, Wireframe Page Flow Diagrams
  • Primary Author: Anthony Hand
  • Download: Wireframe Tracker (23 KB)

Every big project should have one or more asset tracking tools. I created this spreadsheet primarily to assist all of my client and internal team colleagues.

For the Creative Team:

  • Helped them keep track of the unique pages and templates in the site so they could identify what graphical assets they needed to create.
  • Helped the copywriter identify which pages required copy, the kind of copy (e.g., error message, confirmation messages, prompts, Help text), and so on.

For the Development Team:

  • - Helped them keep track of the unique pages and templates so they could streamline their activities, such as the creation of the front end style sheets and server-side interaction controllers. - Because the client relied on a static Help sub-site, the spreadsheet helped the tech team keep track of which specific Help page each web page linked to. This allowed us to develop a rudimentary context-sensitive Help feature.

For the Quality Assurance Team:

  • Provided them with a single source for all unique pages in the site and helped them develop testing scripts.

For the Client Team:

  • As the client requested to take on most of the copywriting responsibilities, this helped them to get a better grasp of the scope of copywriting duties ahead of them.

In addition, this document served the purpose of exposing all of the hard work I'd done in developing the wireframes (esp. since a single web page often required as many as 4 individual Visio pages due to their length and complexity), leveraging page templates as much as possible, and so on. The Project Manager didn't believe me when I told her before we began the Construction Phase that dozens of individual wireframes needed to be created to support the 20 or so individual pages shown on the hierarchical site map. Including page flows, multi-page wireframes, notes, and some duplication of templates, I'd say I created at least 300 individual Visio pages across about 12 wireframe sets. Thank goodness I had some great help! My colleague Lija B., a fellow UEA trained at University of Michigan School of Information, provided about a month's worth of assistance in conceptualizing and developing wireframes.

 

Other Links in this Case Study

 

 

 

About Me | Project Portfolio |
Photo Gallery | Comedy Lounge |
Rice Paddy Tales | Iwate Handbook | Credits & Links

Contact Me | Site Map | HandaWeb Home/Anthony

 

Images and Text ©2001, Anthony Hand
Email:
anthony@handaweb.com