Visio prototyping -LONG-

5 Jun 2005 - 4:18pm
9 years ago
1 reply
932 reads
Juan Lanus
2005

Gosh! Jonathan's simple question about where to find Visio training
triggered a raft of 18+ postings, all of then fairly worked!

As of now the subject "visio prototyping" is already historic. Now it
should be "Prototyping and design and documentation tools
(un)available", (please don't change it).

I'm following the thread with special interest because I'm designing a
related tool. Initially a tool for capturing user requirements by
registering system interaction, in a textual fashion like "scenarios"
or "use cases."
But scenarios and use-cases lie close to UI-operaion design (as
opposed to UI-appearance design).
Also, any such tool *must* be able to handle some sort of links,
preferable the best kind:: two-way, easily set and automatically
mantained.
The resulting links web is the basic material a functioning prototype
is made of, the foundational bricks. So the tool should be able to
export it's data in a shape usable by Visio, or in HTML, or as I se
now, both formats. And also Openoffice / StarOffice Draw for Linux and
Mac users.

I'd like to end up with a tool useful for everybody. All the team
members of most of the teams, with focus in smaller teams or
single-developer teams.

Sort of a layered repository of all the collected and produced
information about the project.
Organized the way each one needs it. For example the programmer will
want objects while the graphical designer prefers "screens" or
"forms".

As it's already impossible to reproduce the capabilities of programs
as those mentioned in the thread, and already many people in
proficients in ome or more of them (as can be infered frm the thread),
the idea is to make the tool capalbe of linking to the final
documents.

Treating your postings as a suspected-wish list, I'd write the
following -note that anything you wrote can be used against you :-)
and that it's not a problem if I'm somehow wrong because what you
didn't mean may be yes meant by somebody else:

Wendy: Visio, Flash, Visual Basic
+ hyperlinks: interactive prototypes
+ no training
+ From the link http://www.guuui.com/issues/02_03_02.php
The reason why Visio is the favourite prototyping tool
of many interaction designers is because of its ready-made
interface objects, you can drag-and-drop onto pages and
its ability to link pages together and export them as web
pages.
But what distinguishes Visio from other prototyping tools
is its use of layered backgrounds.
Marci Ikeler: Visio, Visual Basic, HTML
+ hyperlinks
+ seamless results w/o creating each and every page
+ state transitions
Tom Vollaro: Visio, HTML, Acrobat
+ hyperlinks
Robert Cornejo: InDesign, Pagemaker, Visio, Acrobat
+ paper prototyping
+ "master" pages (stencils?)
+ hyperlinks
+ small files, readable by any client
David Heller: Mac, Visio, HTML, Flash, Norpath Elements, Dreamweaver
+ hyperlinks
+ background pages, stacked
+ software design stencils
+ web and desktop
+ intuitive layout procedures
+ screen design
+ widget states
+ design
+ document
+ enjoy programming (!)
+ fidelity levels
Bill DeRouchey: InDesign, PDF but not Acrobat
+ master pages: do it once
+ hyperlinks to any object
+ common navigatoin items
+ export to PDF
Ji Kim: Visio, MS Office
+ web applications
+ thick clients
+ short learning curve
Michelle N.: Mac, Omnigraffe, JSP, Powerpoint, Macromedia Flex
+ screen-level design
+ widgets stencil
+ realistic designs
+ programming
+ explanatory text layer
+ explanatory text on/off
Navneet Nair: Excel, Dreamweaver, Visio, not Flex, Flash
+ low-fidelity prototyping
+ hyperlinks
+ forms and controls
+ comment feature
+ review people adds comments
+ no server dependency for showing
Helen Johnstone: Paint, Photoshop, Visual Studio, powerPoint
+ personal widget library
+ explanatory text on/off
Anjali Arora: Fireworks, DreamWeaver, Photoshop, Javascript, Flash
+ flexibility
+ store art pieces as (in?) folders
+ turn off/on layers
Ron: ACD System Canvas, Illustrator, InDesign, Acrobat, Visio
+ hyperlinks
+ one seamless application
+ available in Windows and Mac
+ default stencils
+ doing flowcharts and such
+ explanatory text
+ turn layer on/off
Sylvania Dye: Visio, Dreamweaver, PhotoShop, Flash
+ functioning prototype
+ tool depends on prototype type
+ Windows UI widgets library
+ scalable, layered UI elements
+ interactive behaviour; mouse in, onClick ...
+ wireframing
+ switch fidelity levels
+ paper prototyping
+ process flows
+ UML
+ documenting final design
Nurit Peres: Visio
+ different tools for different targets
+ different tools for different stages
+ programming
+ web applications
+ Windows applications
+ GIS aplications
+ design targets: customer, users, testers, evelopers, designers, boss
+ diference between graphics and UI
+ what tool do you master

What would you want a tool help you do?
--
Juan Lanus
TECNOSOL
Argentina

Comments

5 Jun 2005 - 5:00pm
Wendy Fischer
2004

It's funny, because I really tend to adapt my tools for prototyping based on what type of company I am working at and what resources I have access to. Lately, most of my wireframes and paper prototypes have been in Illustrator (using the Zentall GUI elements) due to the fact that my boss forgot to order Visio Professional so I've been without it.

I ordered Macromedia MX Studio and Adobe Creative Studio 2 and have been quite happy with using Flash and Illustrator for more basic interactive prototypes and using Dreamweaver and Photoshop for higher fidelity prototypes. It's also easier to print out Illustrator documents as PDF and you don't need Acrobat.

Juan Lanus <juan.lanus at gmail.com> wrote:
[Please voluntarily trim replies to include only relevant quoted material.]

Gosh! Jonathan's simple question about where to find Visio training
triggered a raft of 18+ postings, all of then fairly worked!

As of now the subject "visio prototyping" is already historic. Now it
should be "Prototyping and design and documentation tools
(un)available", (please don't change it).

I'm following the thread with special interest because I'm designing a
related tool. Initially a tool for capturing user requirements by
registering system interaction, in a textual fashion like "scenarios"
or "use cases."
But scenarios and use-cases lie close to UI-operaion design (as
opposed to UI-appearance design).
Also, any such tool *must* be able to handle some sort of links,
preferable the best kind:: two-way, easily set and automatically
mantained.
The resulting links web is the basic material a functioning prototype
is made of, the foundational bricks. So the tool should be able to
export it's data in a shape usable by Visio, or in HTML, or as I se
now, both formats. And also Openoffice / StarOffice Draw for Linux and
Mac users.

I'd like to end up with a tool useful for everybody. All the team
members of most of the teams, with focus in smaller teams or
single-developer teams.

Sort of a layered repository of all the collected and produced
information about the project.
Organized the way each one needs it. For example the programmer will
want objects while the graphical designer prefers "screens" or
"forms".

As it's already impossible to reproduce the capabilities of programs
as those mentioned in the thread, and already many people in
proficients in ome or more of them (as can be infered frm the thread),
the idea is to make the tool capalbe of linking to the final
documents.

Treating your postings as a suspected-wish list, I'd write the
following -note that anything you wrote can be used against you :-)
and that it's not a problem if I'm somehow wrong because what you
didn't mean may be yes meant by somebody else:

Wendy: Visio, Flash, Visual Basic
+ hyperlinks: interactive prototypes
+ no training
+ From the link http://www.guuui.com/issues/02_03_02.php
The reason why Visio is the favourite prototyping tool
of many interaction designers is because of its ready-made
interface objects, you can drag-and-drop onto pages and
its ability to link pages together and export them as web
pages.
But what distinguishes Visio from other prototyping tools
is its use of layered backgrounds.
Marci Ikeler: Visio, Visual Basic, HTML
+ hyperlinks
+ seamless results w/o creating each and every page
+ state transitions
Tom Vollaro: Visio, HTML, Acrobat
+ hyperlinks
Robert Cornejo: InDesign, Pagemaker, Visio, Acrobat
+ paper prototyping
+ "master" pages (stencils?)
+ hyperlinks
+ small files, readable by any client
David Heller: Mac, Visio, HTML, Flash, Norpath Elements, Dreamweaver
+ hyperlinks
+ background pages, stacked
+ software design stencils
+ web and desktop
+ intuitive layout procedures
+ screen design
+ widget states
+ design
+ document
+ enjoy programming (!)
+ fidelity levels
Bill DeRouchey: InDesign, PDF but not Acrobat
+ master pages: do it once
+ hyperlinks to any object
+ common navigatoin items
+ export to PDF
Ji Kim: Visio, MS Office
+ web applications
+ thick clients
+ short learning curve
Michelle N.: Mac, Omnigraffe, JSP, Powerpoint, Macromedia Flex
+ screen-level design
+ widgets stencil
+ realistic designs
+ programming
+ explanatory text layer
+ explanatory text on/off
Navneet Nair: Excel, Dreamweaver, Visio, not Flex, Flash
+ low-fidelity prototyping
+ hyperlinks
+ forms and controls
+ comment feature
+ review people adds comments
+ no server dependency for showing
Helen Johnstone: Paint, Photoshop, Visual Studio, powerPoint
+ personal widget library
+ explanatory text on/off
Anjali Arora: Fireworks, DreamWeaver, Photoshop, Javascript, Flash
+ flexibility
+ store art pieces as (in?) folders
+ turn off/on layers
Ron: ACD System Canvas, Illustrator, InDesign, Acrobat, Visio
+ hyperlinks
+ one seamless application
+ available in Windows and Mac
+ default stencils
+ doing flowcharts and such
+ explanatory text
+ turn layer on/off
Sylvania Dye: Visio, Dreamweaver, PhotoShop, Flash
+ functioning prototype
+ tool depends on prototype type
+ Windows UI widgets library
+ scalable, layered UI elements
+ interactive behaviour; mouse in, onClick ...
+ wireframing
+ switch fidelity levels
+ paper prototyping
+ process flows
+ UML
+ documenting final design
Nurit Peres: Visio
+ different tools for different targets
+ different tools for different stages
+ programming
+ web applications
+ Windows applications
+ GIS aplications
+ design targets: customer, users, testers, evelopers, designers, boss
+ diference between graphics and UI
+ what tool do you master

What would you want a tool help you do?
--
Juan Lanus
TECNOSOL
Argentina
_______________________________________________
Welcome to the Interaction Design Group!
To post to this list ....... discuss at ixdg.org
(Un)Subscription Options ... http://discuss.ixdg.org/
Announcements List ......... http://subscribe-announce.ixdg.org/
Questions .................. lists at ixdg.org
Home ....................... http://ixdg.org/

Syndicate content Get the feed