Comments on: 4 easy steps for documenting user interface

By: 1001 Lists To Read Before You Die | Terabell - technology, law, programming and a laugh

Sat, 11 Aug 2007 09:40:05 +0000

[...] [...]

By: fsbrainstorm v4.0 » Blog Archive » 4 Easy Steps for Documenting User Interfaces

Mon, 22 Jan 2007 00:12:12 +0000

[...] Here are 4 easy steps for documenting user interfaces from justaddwater.dk. In short: [...]

By: WebWord » Blog Archive » 4 easy steps for documenting user interface

WebWord » Blog Archive » 4 easy steps for documenting user interface — Sun, 26 Nov 2006 15:48:05 +0000

[...] Short, simple, easy… [...]

By: Thomas Baekdal

Thomas Baekdal — Wed, 22 Nov 2006 17:21:38 +0000

Jesper, that is good advice – and a very simply method. I use the method of “whatever-I-can-think-of-documentation”, which is not very good. Maybe I should give your approach a go.

Rasmus, A good way to see the relation between interface elements and interactions is to make a mind map. Most of the system that I make is modular; meaning the same interaction and interface elements is used in many different scenarios and systems (with an added bonus of creating cross-system consistency).

Combining Jespers’ method with a mind map could really be interesting.

By: Percy

Percy — Wed, 22 Nov 2006 16:30:10 +0000

This is a neat way to do the documentation. I wish I’d known about it when I used to do UI evaluations of a product. It seems to be that you’re really cutting it down to the essentials and in doing so you could even find problems that might have been overlooked earlier. Even if you don’t, it’s a nice way to handle the documentation.

By: Preben Carlsen

Preben Carlsen — Wed, 22 Nov 2006 12:25:14 +0000

Depending on the complexity of the GUI, I sometimes uses the model suggested by Jesper, sometimes uses QuickTime to demonstrate and thereby reduces a potential big number of screenshots.

By: Rasmus Knippel

Rasmus Knippel — Wed, 22 Nov 2006 11:47:48 +0000

As I was the asking party I just want to add a couple of lines.

The problem is, as noted above, that some of the GUI is interacting with various services and systems. What I need is a way to “anchor” a GUI in such a way that I can identify which GUI’s potentially will be affected of a change in the backend services (URL is not an option).

Looking forward to you input..