Bryant Street Cafe

     
 

Design interface first, then code


I am not an engineer. But I use a lot of applications. I was involved in helping design a workflow for a group inside Sun. To do that, I worked with a methodology called "The Bridge" (for example, http://www.upassoc.org/conferences_and_events/upa_conference/2005/program/activity.php?id=235,) where we gathered a small group of users and engineers to participate in a focussed three-day workshop designing a workflow. The outcome of that process is to have paper prototypes of GUIs which capture the needed functionality. From those paper prototypes one could conduct usability testing. And all of this without any coding. From this effort, one could derive a prioritized set of specifications because one would have derived how the user uses the application. I will say this effort is a hard sell, at least for me. But I would love to hear if others had worked this way on interfaces.Or maybe I don't realize that a lot of work is done this way and since I am not in the engineering community, I am not aware of it.
 
 
 
 
Comments:

Hi, we do also ui prototyping yet in analyze phase before any coding. Our business analysts use this tool: http://www.cleverlance.cz/en/Products/Petra/Petra_lite/screenshots_demos/

Posted by Karel Kyovsky on December 13, 2005 at 10:31 AM PST #

Karel, Thank you for the info. I see you can use your product on Linux. That's very interesting. I will keep your info in case I can use in for an upcoming project. By the way, my sister's name is Karol (slightly different spelling, but close!)

Posted by Mary Lautner on December 13, 2005 at 11:01 AM PST #

Post a Comment:
  • HTML Syntax: NOT allowed
 

« December 2009
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
  
       
Today

Valid XHTML or CSS?

[This is a Roller site]
Theme by Rowell Sotto.

View My Stats
 
© lautner