|
Before we started to design GUI, we first made analysis of
4 issues
1.
Working experience and knowledge background of the users
2.
Task that the software will perform for users
3.
Frequency that users perform special tasks of the product
4.
Importance of these tasks
We are trying to make GUI able to lead the users gradually
and request data decisions that relative with previous ones, so that
users can use GUI by recognition easily.
Access
exploits forms and reports to implement user interface. We use forms
when we want to provide an interactive interface, reports when we want
to provide a one-way interface. We design the GUI as a direct
manipulation interface, where users can perform direct incremental
reversible operations with immediately visible results.
Form
Design
Users
of our products will spend most of their time working with forms.
Various controls have been explored, which are text box, combo box,
list box, option group, check box and label and so on.
Text
boxes are the most common type of data control on most forms. We use a
text box when we want the user to maintain the value by typing
information.
However,
the disadvantage of text box is that the user must type the commands
precisely and sometimes user may not be able to type rapidly. In order
to minimize these drawbacks, we also explore combo box, which can
provide a number of possible choices. User can select one from the
list by pointing at it with a mouse instead of typing. The values in
list can come from records in a table or query, or the values we set.
A combo box can be a wise choice when the list of values to show is
relatively small—less than 200 or so.
List
box is quite similar to combo box. However, we will choose list box
when the following two criteria are met:
1.
The values available for selection can vary
2.
The only values the can be stored in the associated field are
the values shown in the list
The
user chooses a value from the list by clicking the desired option in
the list. The value chosen replaces the current contents of the
associated field.
When
we have a field that can only contain a small number of possible
values, we consider using an option group.
When
a field only contains one to two possible values, such as Yes/No, we
consider check box.
Layout
Here
are a few guidelines we follow to design the forms.
·
Consistently
group related controls together – for example, all the fields
containing add4ress information. Grouping saves valuable space on your
form and improves the flow when maintaining data.
·
Use
rectangles and lines to separate groups of related controls. This
helps the user associate the controls with the topics they relate to.
·
Use
space between controls to indicate relationships. For example, little
or no space between controls shows that the controls depend on each
other to describe a particular piece of information.
·
Use
alignment to help indicate related controls. Staggering groups of
related controls gives a visual clue that they are included in a
group.
·
Align
controls both horizontally and vertically to give the form an orderly
appearance.
·
Balance
the placement of controls on the form, so that they are evenly
distributed over the form.
·
Large
rectangle controls can be used to either frame or separate information
on the form.
Using
Color Effectively
We
make use of color to give visual cues about the data. For example, we
make required fields one color and optional fields another.
We
also avoid using too many colors, because using fewer colors on a form
gives those colors more impact.
We
do not rely on color and shading alone to send signals. Moreover we
change fonts to give a second cue.
Font
There
are some guidelines when we are regarding fonts.
·
Mixed
uppercase and lowercase text is easier to read than text set in
all-capitals.
·
Using
all capital letters is a good way to draw ATTENTION
·
Bold
type adds emphasis to text.
|