Writing A Functional Specification - The Color Purple (
Page 7 of 9 )
With the workflow decided, the next step is to define the look and feel for
the application's user interface. At this point, you will finally have to
commit to things like the interface metaphor, screen colors, branding and
related items. Much of this information will come from detailed discussions
with the organization's interface design team, and will be based heavily on
the prototypes created in the previous stage.
Care should be taken at this point to ensure that the filling in of the
skeletal structure decided in the previous phase does not have the unwanted
effect of making previously-simple items complicated - for example, by
adding visual enhancements that distract (rather than enhance) the user
experience. The typical example here is that of the flashing banner
advertisement - it's a definite attention-getter, but it usually ends up
annoying more users than gaining customers. And if you're building a new
product, anything that increases your user's already-high stress level is a
definite no-no.
It is for this reason that you, in the role of specification writer and
moderator, must interact closely with the interface design team and provide
feedback if the interface begins complicating, rather than simplifying,
common functions. As in all other aspects of life, the KISS principle has a
role to play here too.
It's important to take into account the client's branding requirements at
this stage also. Selection of the screen colours, a clearly-visible logo or
brand image, the attitude and spirit conveyed by the various elements of the
interface must all be in sync with the client's needs and desired image. To
this end, care should be taken to involve the client's marketing or brand
equity personnel in discussions of the user interface, so as to avoid design
changes at a later date.
/ 60 
