Product Specification Document

Early in the project, before the origination of assets has begun, a product specification needs to be drawn up by the interactive designer which flowcharts and itemises every screen image, every instance of screen text and every consequence of user events. Part of any specification must be a file-naming convention which should be agreed between the interactive designer and the programmers. The product specification should contain a specification for graphics to serve as a check list for the artistic director, the file transfer manager, and programming. The specification for sound should serve as a checklist for the sound engineer, the file transfer manager and programming. Included in the product specification document should be notes on file formats, parameters (such as dimensions, duration, and resolution) and projected file sizes (in kilobytes, say).

The product specification document should be designed to cross-reference with other documents produced, such as flowcharts and storyboards.

It may contain the following:


A good product specification will result in better product design, clear task goals, and a greater liklihood of working to schedule and within budget.

Poor product specification can result in team 'drift', with goals being hard to set, and problems emerging late in the production process affecting all stages, causing delays and extra expense.