Design process: When to bring in technology? (was RE: [ID Discuss]Software for requirements management)

17 Dec 2004 - 10:23am
938 reads
Peter Boersma

David wondered:
> I just want to make sure that what he is saying above is not saying that
> design should be completely technology free throughout its
> process (even the front-end design).

You are right, I am not saying that design should be completely technology
free. Technology requirements limit the range of possible solutions, as do
all requirements.
But I am saying that requirements should be stated in a technology-ignorant
way (except for pure technology requirements like "must run on Sun Solaris"
or "must render the same in IE6.0 and Netscape 4.75").

So dont say: "Welcome to this" goes on webpage 3.
Instead say: Welcome text goes into the introduction section.

This allows you to develop several different prototypes and check whether
they meet the requirements instead of forcing designers down one way by
writing assumptions (from one prototype) into the requirements.

It also makes your requirements documents more future-proof and
cross-channel applicable.

Peter Boersma - Senior Information Architect - EzGov
Rijnsburgstraat 11 - 1059AT Amsterdam - The Netherlands
t: +31(0)20 7133881 - f: +31(0)20 7133799 - m: +31(0)6 15072747
mailto:peter.boersma at -

Syndicate content Get the feed