Comments on: Prototyping http://barocks.com/2007/07/02/prototyping/ Maria (Murphy) Horrigan talks about Business Analysis, User Centred Design in Requirements Development and Business Process Improvement Thu, 28 Aug 2008 08:40:01 +0000 http://wordpress.org/?v=2.2 By: Urls Sinistras » Blog Archive » del.icio.us entre 03/07/2007 e 09/07/2007 http://barocks.com/2007/07/02/prototyping/#comment-22 Urls Sinistras » Blog Archive » del.icio.us entre 03/07/2007 e 09/07/2007 Tue, 10 Jul 2007 03:02:28 +0000 http://barocks.com/2007/07/02/prototyping/#comment-22 [...] PrototypingI have recently been involved in a project where it was difficult to articulate the needs of users in the requirements specifications, because the users did not really know what they wanted. [...] […] PrototypingI have recently been involved in a project where it was difficult to articulate the needs of users in the requirements specifications, because the users did not really know what they wanted. […]

]]> By: horri http://barocks.com/2007/07/02/prototyping/#comment-19 horri Wed, 04 Jul 2007 03:19:44 +0000 http://barocks.com/2007/07/02/prototyping/#comment-19 Yes, Matt it is you. M Yes, Matt it is you.

M

]]> By: magia3e http://barocks.com/2007/07/02/prototyping/#comment-18 magia3e Wed, 04 Jul 2007 01:53:52 +0000 http://barocks.com/2007/07/02/prototyping/#comment-18 "IA Colleagues" ??? ... that would be me! *LOL* M “IA Colleagues” ???

… that would be me! *LOL*

M

]]> By: Theory: separating good prototypes from the bad « Matt’s Musings http://barocks.com/2007/07/02/prototyping/#comment-17 Theory: separating good prototypes from the bad « Matt’s Musings Tue, 03 Jul 2007 03:49:36 +0000 http://barocks.com/2007/07/02/prototyping/#comment-17 [...] Horrigan recently blogged about her experiences with systems prototyping. Maria wouldn’t describe herself as an IA, but her efforts always result in systems that [...] […] Horrigan recently blogged about her experiences with systems prototyping. Maria wouldn’t describe herself as an IA, but her efforts always result in systems that […]

]]> By: magia3e http://barocks.com/2007/07/02/prototyping/#comment-16 magia3e Mon, 02 Jul 2007 23:48:20 +0000 http://barocks.com/2007/07/02/prototyping/#comment-16 As you rightly say, though, prototyping with a good tool is only half way there. Theory and methodology of information design, usability, and accessibility, is also needed to support good 'design' decisions -- they prompt questions like: * scope - what information and what content is needed by the system's users? what information support is needed to help system users? what processes can be supported and how? * structure - what taxonomy of navigation and information is needed to easily get around? Folksonomy? Taxonomy? Both? How can they be used to create a logical and consistent flow of information? * skeleton - what parts, widgets, banners, forms, do users need? Where can they go on the page to ensure they can be easily used? How can they be consistency applied to ensure context is maintained throughout the system? * surface - what will the graphical elemets look like? how can they help rather than hinder? Asking these questions differentiates a good prototype (and a good prototyper) from a poor one, regardless of whether they call themselves a BA or a User-experience designer. M As you rightly say, though, prototyping with a good tool is only half way there. Theory and methodology of information design, usability, and accessibility, is also needed to support good ‘design’ decisions — they prompt questions like:

* scope - what information and what content is needed by the system’s users? what information support is needed to help system users? what processes can be supported and how?

* structure - what taxonomy of navigation and information is needed to easily get around? Folksonomy? Taxonomy? Both? How can they be used to create a logical and consistent flow of information?

* skeleton - what parts, widgets, banners, forms, do users need? Where can they go on the page to ensure they can be easily used? How can they be consistency applied to ensure context is maintained throughout the system?

* surface - what will the graphical elemets look like? how can they help rather than hinder?

Asking these questions differentiates a good prototype (and a good prototyper) from a poor one, regardless of whether they call themselves a BA or a User-experience designer.

M

]]> By: Billy http://barocks.com/2007/07/02/prototyping/#comment-15 Billy Mon, 02 Jul 2007 11:12:42 +0000 http://barocks.com/2007/07/02/prototyping/#comment-15 Sweet prototyping tool - hadn't come across that before (although I have become pretty handy with Visio for wireframes). Sweet prototyping tool - hadn’t come across that before (although I have become pretty handy with Visio for wireframes).

]]>