The Multimedia Development Process

Introduction

For the purposes of these guidelines, the multimedia design process has been broken down into the following principal phases: planning, design, production and validation. (A schematic representation of the process is given in the accompanying Pert chart of the development process.) This section provides information on each of these phases, breaking them down into a number of sub-tasks. Tasks are listed sequentially, in the order they would often be tackled in the actual development process. Depending on project requirements, however, the exact nature of tasks and the order in which they are carried out will vary between projects and according to team preferences. For instance, not all projects will require support materials or packaging, or a destination-site study, and end-user models may be carried over between projects, as long as the assumptions built into the model are explicit and may be reviewed and revised as a result of user-feedback generated in the course of product testing and validation. Equally, delays usually require creative project management decisions to bring tasks into parallel which might ideally be best completed in series.

Table of Contents

• Planning a Working Environment
• Putting together a development team
• Planning
  Sufficient care and time should be given to ensuring that aims and objectives are clarified, that the material and human resource requirements of the project have been identified, that roles and responsibilities are clear, that the best procedures to realize project aims and objectives have been discussed and agreed and that difficulties are anticipated and allowed for. Good planning is essential to the successful outcome of any project.
  • Starting projects
  • Exploratory meetings
  • Initial Brief or Treatment
  • Costs
  • Feasability Studies
  • Test of Concept Models
  • Written Agreements
  • Documentation
• Design
  Once the team is in place and the strategy for tacking the project has been planned, designing the look and feel of the interactive program and writing the content can take place.
  • Brainstorming
  • Flowcharts
  • Modelling the End-user
  • Report on Destination Site
  • Product Specification
  • Storyboarding
  • Human-computer Interface Design
  • Content definition: writing scripts and captions
  • Asset research, copyright clearance and acquisition
  • Inputting text
  • File convertion and file management
  • Designing Support Materials and Packaging
• Production
  • Prototyping
  • Graphics
  • TV
  • Programming
  • Support Materials and Packaging
  • Integration
  • Mastering
• Validation
  Validation (or testing) is a painstaking procedure but an essential part of the total quality assurance process. It is the study of the effectiveness of design prototypes, acknowledging any weaknesses encountered. The purpose of validation is to check to see if the program meets its specified objectives. Realising the objectives of the validation process requires clear testing procedures to be devised. In-house debugging is the testing of a program's functionality: do all the buttons and effects operate as intended without causing the system to crash? It will also cover performance testing under different hardware and operating system configurations. Trialling refers to testing the program's end-user objectives in a simulated or real end-user environment -- field testing. The process of testing, trialling and revision is cyclical. Program revision sends the team back to the debugging process and on to field testing again. One of the big problems in the process is that exhaustive testing is usually impossible, given the limited time and resources available for the project's lifetime and the pressures to demonstrate working models to clients prematurely.
  • Quality and Task Completion Checking
  • In-house debugging
  • Content Testing
  • Trialling
  • Revising
• Post Development Support and Maintenance
  Built into any project should be an overhead to cover the post-development support and maintenance of deliverables. One should not underestimate the amount of time that can be consumed handling technical support queries on a product for which there is no longer a budget.