Week 8 Reading Summary:

Web Redesign, Chapter 6, Phase 4 : Production and QA

This article is very useful for our class project, I think. It provides a detailed checklist for us, especially project managers.

This phase is to creat, implement, and integrate--where the actual building happens. The goal: no duplication of efforts; Code each HTML page only once; No misinterpretation of user capabilities or project goals; No backtracking.

The author divides this phase into three sections-- prepping, building, and testing. This is a production workflow aimed at
keeping the project's HTML construction on track.

[Prepping] Assessing Project Status
Reassess HTML production team’s capabilities now that you know the true extent of the design and technical requirements. Depending on your team’s level of expertise, you will need to determine the true level of complexity that the site production can handle. And before any coding truly begins, a final justbefore-production-starts review of audience needs (browsers, screen size, connection speed), technology (plug-ins, scripting, backend needs), and redesign goals (download size, user experience goals) can only help.

You will have to address complex questions about servers, directory structure, and the HTML production specifics that may have been left until this phase.

[Prepping] Establishing clear guidelines
The Client Spec Sheet sets parameters for audience
capabilities and technical standards for the site. It is a worksheet, long and detailed and technical. Parameters: target operating systems, browsers, monitors, and connection speeds.

Before beginning the production process, it is important to
identify a composite of the target audience and understanding the client’s expectations and preferences concerning the site production details.

*check whether scope expectations meet scope reality
*check time. You should have been tracking your hours on a weekly
basis, so this should be a relatively easy assessment.
*check content status, design status;
*confirm the backend integration plan (if the site is dynamic).

[Prepping] Setting File Structure
It is not site architecture, but housekeeping (be scalable and stay organized).

[Building] Slicing and Optimization
Prior to production, during the design phase, before any visual design directions are finalized and approved, they must get checked by the production team to ensure that the files are, in fact, sliceable and optimizable under target-audience download requirements. Visual designers need to work closely with the HTML production team to determine the best way to slice the graphic templates so that the HTML tables — the rudimentary basis for HTML layout — can be constructed.

[Building] Creating HTML Templates and Pages

[Building] Implementing Light Scripting
* Rollovers, forms, pull-down menus, pop-up windows, image swaps, frames… all are the result of light scripting.

* The separation of style from content--separate our design from our data.

[Building] Populating Pages
Make sure the content goes into the correct places. Make certain nothing gets missed or placed in the wrong spot.

[Building] Populating your pages
It involves all content, including the frequently forgotten, production-specific “invisible content”— ALT, META, and TITLE tags.

[Building] Integrating Bachend Development
Communication between the backend development team and the front-end design and production teams has always been important, but at this point in the web development process, it becomes absolutely crucial.

[Testing]
> Understanding Quality Assurance Testing
> Creating a QA Plan
> Prioritizing and Fixing Bugs
> Conducting a Final Check
*Design check
*HTML check
*Functionality/engineering check (if applicable)
*Content check
*Client approval.