>I agree with much of what was said here, however my experience
>is that the GUI has a very direct effect on tasks taken on in
>the service layer. I would not recommend separately them
>prematurely, as how the client wants things done in the GUI,
>often has direct implications with regards to what goes on
>behind the scenes (often related to units of work and transactions).
>
>Jonathan
I would like to reiterate the fact that in many cases the user *thinks* in
terms of UI actions. The problem is that the user often does not have the
understanding of the mechanics and psychology of user interfaces to
accurately define what the UI should look like.
I have seen many a UI that had gaudy colors, with strange looking buttons
and arcane sequences of action to perform tasks. Just because a customer
thinks that the UI should look a certain way does not mean it should, in the
same fashion that if you were to design a house, and decide to put a
specific function in a specific room, the artchitect might interject and
explain why things should not be the way you want them. This is because it's
the architects expertise to understand the implications of specific domestic
artifacts on the plan and the end result. In a similar fashion the UI expert
can explain to the customer why their choice of UI is not optimal.
Eventually the same things will happen, but hopefully, with the UI expert's
help, they will be easier, clearer and safer to accomplish.
Amir
To Post a message, send it to: [EMAIL PROTECTED]
To Unsubscribe, send a blank message to: [EMAIL PROTECTED]
ad-free courtesy of objectmentor.com
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/extremeprogramming/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
