Please enable JavaScript.
Coggle requires JavaScript to display documents.
4.1 UNDERSTAND USER INTERFACE DESIGN - Coggle Diagram
4.1 UNDERSTAND USER INTERFACE DESIGN
USER INTERFACE DESIGN (UI)
:check: how users interact with a computer system
:check: and consists of all the hardware, software, screens, menus, functions, output
:check: and features that affect two-way communications
between the user and the computer.
a) Evolution of the User Interface
:check: the user interface mainly consisted of process-control screens that allowed the user to send commands to the system
:check: User-centered system
b) Human-Computer Interaction
:check: Main objective is to create a user-friendly design that is easy to learn and use
:check: Most important, the interface will be based on the perspective of a user rather than a computer engineer, programmer, or systems analyst.
c) Principles of user-centered design
:check: Understand the Business
:!: understand the underlying business functions and how the system supports individual, departmental, and enterprise goals.
:!: A good starting point might be to analyze a functional decomposition diagram (FDD).
:check: Maximize Graphical Effectiveness
:!: Studies show that people learn better visually.
:!: A well-designed interface can help users learn a new system rapidly, and be more productive.
:check: Think Like a User
:!: A systems analyst should understand user experience, knowledge, and skill levels.
:!: The interface should use terms and metaphors that are familiar to users.
:check: Use Models and Prototypes
:!: the interface is the most critical part of the system design because it is where he or she interacts with the system
:!: Users must test all aspects of the interface design and provide feedback to the designers.
:check: Focus on Usability
:!: The user interface should include all tasks, commands, and communications between users and the information system.
:!: Each screen option leads to another screen, with more options
:check: Invite Feedback
:!: Even after the system is operational, it is important to monitor system usage and solicit user suggestions.
:!: Based on user feedback, Help screens might need revision and design changes to allow the system to reach its full potential.
:check: Document Everything
:!: User-approved sketches and storyboards also can be used to document the user interface.
:!: You should document all screen designs for later use by programmers.
2) USER INTERFACE DESIGN GUIDELINES
a) Good user interface design is based on a combination of:
:recycle: Ergonomics
:!: how people work, learn, and interact with computers
:recycle: Aesthetics
:!: how an interface can be made attractive and easy to use
:recycle: Interface technology
:!: operational structure required to carry out the design objectives
b) When you create a user interface, you should follow eight basic guidelines
:recycle: Design a transparent interface
:recycle: Create an interface that is easy to learn and use
:recycle: Enhance user productivity
:recycle: Make it easy for users to obtain help or correct errors
:recycle: Minimize input data problems
:recycle: Provide feedback to users
:recycle: Create an attractive layout and design
:recycle: Use familiar terms and images
c) Screen Elements & Controls
:recycle: List box – scroll bar
:recycle: Drop-down list box
:recycle: Option button, or radio button
:recycle: Check box
:recycle: Calendar control
:recycle: Switchboard
USER INTERFACE COMPONENTS
a) Screen Elements & Controls
:warning: Menu bar
:warning: Toolbar
:warning: Command button
:warning: Dialog box
:warning: Text box
:warning: Toggle button
SOURCE DOCUMENTS
:explode: collects input data
:explode: triggers or authorizes an input action and provides a record of the original transaction
:explode: A form should indicate data entry positions clearly using blank lines or boxes and descriptive captions.
:explode: Source documents typically include most of the zones shown.
:explode: Information should flow on a form from left to right and top to bottom to match the way users read documents naturally.
:explode: The same user-friendly design principles also apply to printed forms such as invoices and monthly statements, except that heading information usually is preprinted.
