1 / 9

MBI 630: Week 11 Interface Design

MBI 630: Week 11 Interface Design. 10/23/2019. Week 11: Designing Interfaces and Dialogues. Designing Interfaces and Dialogues. Styles of User Interfaces. User interface design is the specification of a conversation between the system user and the computer. Interaction Methods and Devices.

dewaynel
Download Presentation

MBI 630: Week 11 Interface Design

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. MBI 630: Week 11Interface Design 10/23/2019

  2. Week 11: Designing Interfaces and Dialogues • Designing Interfaces and Dialogues

  3. Styles of User Interfaces • User interface design is the specification of a conversation between the system user and the computer.

  4. Interaction Methods and Devices • Command Language Interaction • Menu Interaction • Object-Based Interaction (GUI) • (Natural Language Interaction)

  5. Controlling Data Input • One objective of interface design is to reduce data entry errors • Role of systems analyst is to anticipate user errors and design features into the system’s interfaces to avoid, detect and correct data entry mistakes • Table 11-8 (p. 410) describes types of data entry errors • Table 11-9 (p. 411) lists techniques used by system designers to detect errors

  6. Providing Feedback • Status Information • Keeps users informed of what is going on in system • Displaying status information is especially important if the operation takes longer than a second or two • Prompting Cues • Best to keep as specific as possible • Error and Warning Messages • Messages should be specific and free of error codes and jargon • User should be guided toward a result rather than scolded • Use terms familiar to user • Be consistent in format and placement of messages

  7. Providing Help • Place yourself in user’s place when designing help • Guidelines • Simplicity • Help messages should be short and to the point • Organization • Information in help messages should be easily absorbed by users • Demonstrate • It is useful to explicitly show users how to perform an operation

  8. Designing Dialogues • Dialogue • Sequence in which information is displayed to and obtained from a user • Primary design guideline is consistency in sequence of actions, keystrokes and terminology • Dialogue Diagram (Fig. 11-17 -19, pp. 418-420) • A formal method for designing and representing human-computer dialogues using box and line diagrams • Consists of a box with three sections (Fig. 11-17, p. 418) • Top: Unique display reference number used by other displays for referencing dialogue • Middle: Contains the name or description of the display • Bottom: Contains display reference numbers that can be accessed from the current display

  9. Sample Dialogue Diagram Figure 11-18

More Related