[Sigia-l] Web browser based diagramming

[Stewart Dean]

>From: Listera <listera at rcn.com>
>To: SIGIA-L <sigia-l at asis.org>
>Subject: Re: [Sigia-l] Web browser based diagramming
>Date: Sun, 26 Mar 2006 16:33:35 -0500
>
>Stewart Dean:
>
> > Sounds how things used to be done prior to someone realising that like a
> > building, you need a plan prior to building things.
>
>So last century. The Berlin Wall is down and the waterfall process is dead.

Who said anything about a water fall process?

>Let's contrast your personal predilection with the prevailing trends in the
>industry. First, finally the notion of page-based, navigation-driven web
>*sites* is being relegated to legacy status. Data-driven, dynamic
>*applications* is the future. With that comes a different way of designing
>and developing.

Intefaces are usulay either time or space based.  Web 2.0 apps bring dynamic 
elements already found in other interactive platforms. The complexity of new 
apps is even greater reason to define strucutre and flow before  commiting 
to interface.

It was during the creation of a complex interface i realised how poor the 
existing tools are and how a good planning tool would increase the speed of 
interface creation. By defining flow you can ensure all error handling is 
covered, for example.

I think you are misunderstanding what I'm looking for, it's about reducing 
the need to spend time creating interfaces, about element reuse, 
simplification of applications and automation of common tasks.  It's not 
about creating another deliverable and is certainly not isolated from the 
creation of the final app/site - it's about the creation of the final site 
in an IA way, working a level up to save potentialy huge amounts of time and 
reduce errors in the process.

I'm not going to convince you that you 'extreme user experience' view is 
deeply flawed, instead it's good fuel for me to plan this app and get it 
implimented.

Stewart Dean