[IxDA Discuss] The Five Types of Prototypes

Rich Rogan jrrogan at gmail.com
Tue Oct 2 13:17:30 PDT 2007


Prototypes seem to be important for the entire Software Development Life
Cycle, which kind of maps to your 5 utilities of Prototypes.

I've always thought of the utility of protoytpes in a SDLC frame of mind:

1. Concrete example of requirements, facilitating gathering/flushing out
details/buy in
2. Artifact of requirement/design deltas, (versioning/iteration/changing
requirements)
3. Engineering Level of Effort measurement and negotiations artifact, (I've
worked at a place which "counted screens" as per engineering hours of
effort, no kidding)
4. QA artifact
5. Base line Software Artifact


>
> 1. As a common communication platform–using them to get everyone on
> the same page, avoiding misinterpretation of ideas, using them as a
> method to show and tell.
> 2. Work through a design–for designers and developers, prototypes act
> as a way to work through your design solution, giving you the ability
> to evaluate a few different options, tweak them, and come up with the
> best one.
> 3. Sell your idea internally–using them to sell your design solution
> to internal stake holders like senior management, other designers, or
> the engineering team.
> 4. Gauge technical feasibility–designers want to do X, but can
> engineering do it? Do we have the resources? Is it worth the effort?
> 5. As a marketing tool–while similar to number 3, this is for an
> external audience.
>
>


More information about the Discuss mailing list