3-UID-rules
3-UID-rules
• A model used for GUI design and development should fulfill these
GUI specific steps.
• GUI Requirement Gathering - The designers may like to have list of
all functional and non-functional requirements of GUI. This can be
taken from user and their existing software solution.
• User Analysis - The designer studies who is going to use the software
GUI. The target audience matters as the design details change
according to the knowledge and competency level of the user. If user
is technical savvy, advanced and complex GUI can be incorporated.
For a novice user, more information is included on how-to of software.
• Task Analysis - Designers have to analyze what task is to be done by the software
solution. Here in GUI, it does not matter how it will be done. Tasks can be
represented in hierarchical manner taking one major task and dividing it further
into smaller sub-tasks. Tasks provide goals for GUI presentation. Flow of
information among sub-tasks determines the flow of GUI contents in the software.
• GUI Design & implementation - Designers after having information about
requirements, tasks and user environment, design the GUI and implements into
code and embed the GUI with working or dummy software in the background. It
is then self-tested by the developers.
• Testing - GUI testing can be done in various ways. Organization can have in-
house inspection, direct involvement of users and release of beta version are few
of them. Testing may include usability, compatibility, user acceptance etc.
• The following rules are mentioned to be the golden rules for GUI design
• Strive for consistency - Consistent sequences of actions should be required in
similar situations. Identical terminology should be used in prompts, menus, and
help screens. Consistent commands should be employed throughout.
• Enable frequent users to use short-cuts - The user’s desire to reduce the number
of interactions increases with the frequency of use. Abbreviations, function keys,
hidden commands, and macro facilities are very helpful to an expert user.
• Offer informative feedback - For every operator action, there should be some
system feedback. For frequent and minor actions, the response must be modest,
while for infrequent and major actions, the response must be more substantial.
• Permit easy reversal of actions - This feature relieves anxiety, since the user
knows that errors can be undone. Easy reversal of actions encourages exploration
of unfamiliar options. The units of reversibility may be a single action, a data
entry, or a complete group of actions.
• Support internal locus of control - Experienced operators strongly desire the
sense that they are in charge of the system and that the system responds to their
actions. Design the system to make users the initiators of actions rather than the
responders.
• Reduce short-term memory load - The limitation of human information
processing in short-term memory requires the displays to be kept simple, multiple
page displays be consolidated, window-motion frequency be reduced, and
sufficient training time be allotted for codes, mnemonics, and sequences of actions.
• The graphical user interface is the most popular user interface today. A
GUI uses windows, menus and icons to execute commands.
• A mouse is the most common way to navigate through a GUI,
although many GUIs allow navigation and execution via a keyboard.
• One example of a GUI-based application is Microsoft Word.
• A user can change options for page layouts and styles by selecting the
corresponding icon with a mouse or keyboard.
• https://www.tutorialspoint.com/software_engineering/software_user
_interface_design.htm
• https://www.usability.gov/what-and-why/user-interface-design.html#
:~:text=The%20best%20interfaces%20are%20almost,get%20things%2
0done%20more%20quickly.
• https://www.elegantthemes.com/blog/resources/10-rules-of-good-ui-
design-to-follow-on-every-web-design-project