Prototype development

Description

Simple HTML mock-up of a web/Intranet site or application, constructed for briefing and testing, to facilitate a design iteration, before main development effort begins (using expensive programmers, etc.).

Appropriate use

In web/Intranet and software application development projects where programming and database development resources are to be used, an HTML mock-up can be constructed before that expensive team of people (programmers, database designers, etc.) starts work on the project.

The objective here is to reduce project risk by having a more complete specification for the main development phase of the project, reduce the amount of clarification that the programming team needs to seek (or not), shorten the main development phase of the project, and shorten the test/iteration phase at the end of the project (as much of the changes were already made using the prototype).

Output

Graphics or an HTML mock-up.

CSS2: We have moved over to developing prototypes using CSS2, i.e. no tables for layout. In addition to aiding rapid development, HTML and CSS rules from our prototypes are re-usable in the main development effort, saving time and budget. For example, if the main product is to be developed for a portal platform (e.g. Microsoft SharePoint or IBM WebSphere), then much of the HTML code and CSS styles for each box (the <div> and id) on our prototype pages can be used in the webparts or portlets of the portal.

Briefings: in addition to facilitating usability testing, and an iteration of the design before programmers start their work, the prototype is useful to get buy-in from stakeholders early in the project.

User-centred design: Key to a successful project, 'user-centred design' dictates that we must comprehensively test designs & processes with users early in the development process. A prototype, which is faster and cheaper to develop than the main product, facilitates this testing effort.

Reducing project risk: Using the prototype to identify problems with navigation, design, content & processes, and fixing them early, allows the main development to be planned and costed more accurately, reducing the chance of nasty surprises later in the project.