Chapter 8: User Interface Design

Name:
Chapter 8 – User Interface Design: Chapter 8 explains how to design an effective user interface, and how
to handle data security and control issues.

Questions
1. Provide an overview of the systems design phase.
The purpose of systems design is to create a physical model of the system that
satisfies the design requirements that were defined during the systems analysis
phase.
The goal of systems design is to build a system that is effective, reliable, and maintainable.
 A system is effective if it supports business requirements and meets user needs.

m
er as
 A system is reliable if it handles input errors, processing errors, hardware failures, or human

co
mistakes. A good design will anticipate errors, detect them as early as possible, make it easy

eH w
to correct them, and prevent them from damaging the system itself. Other characteristics of

o.
a reliable system include it being available nearly all of the time, and proper backups
rs e
maintained in case of system failure.
ou urc
 A system is maintainable if it is flexible, scalable, and easily modified. Changes might be
needed to correct problems, adapt to user requirements, or take advantage of new
technology.
o
aC s

2. Explain Apple’s view of user interface design, especially for apps.

vi y re

Apple believes that designing and exceptional user interface is essential to a successful app. Apple
has long distinguished itself from its competitors by the intuitiveness of its products. Their
command of the market suggests that consumers are willing to pay a premium for products the “just
ed d

work.”
ar stu

3. Describe the habits of successful interface designers.

 Understands the business

is

 Maximizes graphical effectiveness

Th

 Thinks like a user

 Uses models and prototypes

sh

 Focuses on usability

 Invites feedback

 Documents everything

4. List the eight main guidelines for user interface design. How would you rank them in order of

This study source was downloaded by 100000809806213 from CourseHero.com on 04-14-2021 06:23:12 GMT -05:00

https://www.coursehero.com/file/31166631/Chapter08docx/
 importance? Explain your answer.

 Create an Interface That Is Easy to Learn and Use

 Enhance User Productivity
 Provide Users with Help and Feedback
 Create an Attractive Layout and Design
 Enhance the Interface
 Focus on Data Entry Screens
 Use Validation Rules
 Reduce Input Volume
5. How has input technology changed in recent years? Provide examples of traditional, evolving,
and emerging input technology.

In addition to traditional devices and methods, there has been a rapid expansion of new hardware
and ways to capture and enter data into a system. Businesses are using the new technology to
speed up the input process, reduce costs, and capture data in new forms, such as the digital

m
er as
signature.

co
INPUT TECHNOLOGY

eH w
Traditional Evolving Emerging

o.
Keyboard rs e Body motion detection
Brain-Computer Interface
ou urc
(BCI)
Mouse Advanced voice recognition Neural networks
Pointing devices Biological feedback Artificial intelligence (AI)
o

Microphone Embedded magnetic data Advanced motion sensors

aC s

OCR (optical character RFID Two-way satellite interface

vi y re

recognition)
MICR (magnetic ink character Advanced optical recognition Virtual environments
recognition)
Graphic input devices Physical adaptation devices 3-D technology
ed d

6. What are input masks? What are validation rules? Why are they important?
ar stu

Input masks are templates or patterns that makes it easier for users to enter data. Often used in
automated forms to guide an unfamiliar user.
is

Validation rules are the best defense against incorrect data that sets out to identify and correct
errors before they enter the system. They improve input quality by testing the data and rejecting any
Th

entry that fails to meet specified conditions.

7. What is the difference between a detail report, a summary report, and an exception report?
sh

A detail report produces one or more lines of output for each record processed. Because it contains
one or more lines for each record, a detail report can be quite lengthy.

A summary report is used by individuals at higher levels in the organization that includes less detail
than reports used by lower-level employees.

An exception report displays only those records that meet a specific condition or conditions.

This study source was downloaded by 100000809806213 from CourseHero.com on 04-14-2021 06:23:12 GMT -05:00

https://www.coursehero.com/file/31166631/Chapter08docx/
 Exception reports are useful when the user wants information only on records that might require
action but does not need to know the details.

8. What are the main principles of source document design?

Good report design requires effort and attention to detail. To produce a well-designed report, the
analyst must consider design features such as report headers and footers, page headers and footers,
column headings and alignment, column spacing, field order, and grouping of detail lines.

 Report headers and footers

 Page headers and footers

 Repeating fields

 Consistent design

9. Provide suggestions for reducing input volume.

m
er as
 Input necessary data only.

co
eH w
 Do not input data that the user can retrieve from system files or calculate from other data.

o.
 Do not input constant data.

Use codes. rs e
ou urc


10. Describe modular design and explain the two main prototyping methods.
o

In a modular design, individual components, called modules, are created that connect to a higher-
aC s

level program or process. In a structured design, each module represents a specific process, which is
vi y re

shown on a data flow diagram (DFD) and documented in a process description. If an object-oriented
design is being used code modules represent classes.

System prototyping produces a full-featured, working model of the information system. A system
ed d

prototype that meets all requirements is ready for implementation. Due to a model being “on track”
for implementation, it is especially important to obtain user feedback, and to be sure that the
ar stu

prototype meets all requirements of users and management.

Systems analysts also use prototyping to verify user requirements, after which the prototype is
is

discarded, and implementation continues. The approach is called design prototyping, or throwaway
prototyping. In this case, the prototyping objectives are more limited, but no less important. The
Th

end product of design prototyping is a user-approved model that documents and benchmarks the
features of the finished system. Design prototyping makes it possible to capture user input and
approval while continuing to develop the system within the framework of the SDLC. Systems
sh

analysts typically use design prototyping as they construct outputs, inputs, and user interfaces.

This study source was downloaded by 100000809806213 from CourseHero.com on 04-14-2021 06:23:12 GMT -05:00

https://www.coursehero.com/file/31166631/Chapter08docx/
Powered by TCPDF (www.tcpdf.org)