Materi System and Design Method

System Analysis and
Design Methods
(B1A451)
System Design Input, Output
and Interface Design
Jun 3, 2016
Hamzah Ritchi-System Analysis&Design Methods
Hamzah Ritchi Accounting Padjadjaran University
Timetable
Gambaran umum SADM
Information Building Block
IS Development Life Cycle, Methodology, Technique, and Tools
System Planning and Analysis Req and Feasibility Study
System Planning and Analysis Data and Process Modelling
System Design Data and Process Design
System Design Input, Output and Interface, Implementation and
Support
Seminar Aplikasi Sistem
Tinjauan Menyeluruh dan Kisi kisi ujian
Hamzah Ritchi-System Analysis&
Jun 3, 2016
Todays Outline
Define the appropriate format and media for a computer input.

Explain the difference between data capture, data entry, and data input.
Identify and describe several automatic data collection technologies.
Apply human factors to the design of computer inputs.
Design internal controls for computer inputs , output, and interface.
Select proper screen-based controls for input attributes that are to appear on
a GUI input screen.
Design a web-based input interface.
Identify several important human engineering factors and guidelines and
incorporate them into a design of a user interface.
Understand the role of operating systems, web browsers, and other
technologies for user interface design.
Describe how prototyping can be used to design a user interface.
Jun 3, 2016
Design
Phase
Jun 3, 2016
Input Design Process

1. Identify system inputs and review logical
requirements.
2. Select appropriate GUI controls.
3. Design, validate and test inputs using
some combination of:
a) Layout tools (e.g., hand sketches, spacing
charts, or CASE tools.
b) Prototyping tools (e.g., spreadsheet, PC
DBMS, 4GL)
4. As necessary design source documents.

Jun 3, 2016
Data Capture and Data Entry

Data capture the identification and
acquisition of new data (at its source).
Source documents forms used to record
business transactions in terms of data that
describe those transactions.
Data entry the process of translating the

source data or document (above) into a
computer readable format.
Jun 3, 2016
Data Processing
Data processing is all processing that occurs on
the data after it is input from a machine readable
form.
In batch processing, the entered data is collected into
files called batches and processed as a complete batch.
In on-line processing, the captured data is processed
immediately
In remote batch processing, data is entered and
edited on-line, but collected into batches for subsequent
processing.
Jun 3, 2016
Input Implementation
Methods
Keyboard
Mouse
Touch Screen
Point-of-sale terminals
Sound and speech
Automatic data capture
Optical mark recognition (OMR)
Bar codes
Optical character recognition (OCR)

Magnetic Ink
Electromagnetic transmission
Smart cards
Biometric
Jun 3, 2016
Taxonomy for Computer Inputs

Process
Method
Data Capture
Data Entry
Data Processing
Keyboard
Data is usually captured on

a business form that
becomes the source
document for input. Data
can be collected real-time.
Data is entered via

keyboard. This is the
most common input
method but also the
most prone to errors.
OLD: Data can be collected

into batch files (disk) for
processing as a batch.
NEW: Data is processed as
soon as it has been keyed.
Mouse
Same as above.
Used in conjunction with

keyboard to simplify data
entry. Mouse serves as a
pointing device for a
screen.
Same as above, but the use of

a mouse is most commonly
associated with online and realtime processing.
Touch
Screen
Same as above.
Data is entered o a touch

screen display or
handheld device. Data
entry users either touch
commands and data
choices or enter data
using handwriting
recognition.
On PCs, touch screen choices

are processed same as above.
On handheld computers, data
is sorted on the handheld for
later processing as a remote
batch.
Jun 3, 2016
Taxonomy for Computer Inputs (continued)

Process
Method
Data Capture
Data Entry
Data Processing
Point of Sale
Data captured as close

to the point of sale as
humanly possible. No
source documents.
Data is often entered directly by

the customer or by an
employee directly interacting
with the customer.
Data is almost always

processed immediately
as a transaction or
inquiry.
Sound
Data is captured as close

to the source as
possible, even when the
customer is remotely
located.
Data is entered using touchtones (typically from a

telephone). Usually requires
rigid command menu structure
and limited input options.

as a transaction or
inquiry.
Speech
Same as sound.
Data (and commands) is

spoken. This technology is not
as mature and is much less
reliable and common than other
techniques.

as a transaction or
inquiry.
Optical Mark
Data is recorded on
Eliminates the need for data
optical scan sheets as
entry.
processed as a batch.
marks or precisely
formed letter, numbers,
and punctuation.
10
Jun 3, 2016
Taxonomy for Computer Inputs (concluded)

Process Method
Data Capture
Data Entry
Magnetic Ink
Data usually prerecorded

on forms that are
completed by the
customer. The customer
records additional
information on the form.
A magnetic ink reader reads

the magnetized data. The
processed as a batch.
customer-added data must be
entered using another input
method.
Electromagnetic
Data is recorded directly

on the object to be
described by data.
Data is transmitted by radio

frequency.

processed immediately.
Smart Card
Data is recorded directly

on a device to be carried
by the customer,
employee, or other
individual that is described
by that data.
Data is read by smart card

readers.

processed immediately.
Biometric
Unique human
characteristics become
data
Jun 3, 2016
Data Processing
Data read by biometric

Data is processed
sensors. Primary applications immediately.
are security and medical
monitoring
11
Input Design Guidelines

Capture only variable data.
Not data that can be looked up.
Do not capture data that can calculated or

stored in computer programs as constants.
Extended Price, Federal Withholding, etc.
Use codes for appropriate attributes.
Jun 3, 2016
12
Source Document /
Form Design Guidelines
Include instructions for completing the
form.
Minimize the amount of handwriting.
Data to be entered (keyed) should be
sequenced top-to-bottom and left-to-right.
When possible use designs based on
known metaphors.
Jun 3, 2016
13
Bad Flow in a Form
Jun 3, 2016
14
Good Flow in a Form
Jun 3, 2016
15
Internal Controls for Inputs

The number of inputs should be monitored (to
minimize risk of lost transactions).
For batch processing

Use batch control slips
Use one-for-one checks against post-processing detail reports
For on-line systems
Log each transaction as it occurs to a separate audit file
Validate all data
Existence checks
Data-type checks
Domain checks
Combination checks
Self-checking digits
Format checks
Jun 3, 2016
16
Common GUI Controls (Windows and Web)

Text boxes
Radio buttons
Check boxes
List boxes
Drop down
lists
Combination
boxes
Spin boxes
Buttons
Courtesy of Palupi, Yoza and Natalie, 2007
Jun 3, 2016
17
Common GUI Controls Uses

Text boxes
When the input data values are unlimited in scope
Radio buttons
When data has limited predefined set of mutually exclusive

values
Check boxes
When value set consists of a simple yes or no value
List boxes
When data has a large number of possible values
Drop down lists
When data has large number of possible values and screen

space is too limited for a list box
Combination boxes
To provide user with option of selecting value from a list or

typing a value that may or may not appear in the list
Spin boxes
When need to navigate through a small set of choices or

directly typing a data value
Jun 3, 2016
18
The User Interface Design Process

1. Chart the user interface dialogue.
State Transition Diagram a tool used to
depict the sequence and variation of screens
that can occur during a user session.
2. Prototype the dialogue and user interface.

3. Obtain user feedback.
Exercising (or testing) the user interface
4. If necessary return to step 1 or 2
Jun 3, 2016
19
System User Classifications

Expert User an experienced computer user
Spends considerable time using specific application

programs.
Use of a computer is usually considered non-discretionary.
In the mainframe computing era, this was called a dedicated
user.
Novice User a less experienced computer user
Uses computer on a less frequent, or even occasional,

basis.
Use of a computer may be viewed as discretionary (although
this is becoming less and less true).
Sometimes called a casual user.
Jun 3, 2016
20
Interface Problems
According to Galitz, the following problems result in
confusion, panic, frustration, boredom, misuse,
abandonment, and other undesirable consequences.
Excessive use of computer jargon and acronyms

Nonobvious or less-than-intuitive design
Inability to distinguish between alternative actions (what
do I do next?)
Inconsistent problem-solving approaches
Design inconsistency
Jun 3, 2016
21
Commandments of User
Interface Design
Understand your users and their tasks.

Involve the user in interface design.
Test the system on actual users.
Practice iterative design.
Jun 3, 2016
22
Human Engineering Guidelines

The user should always be aware of what to
do next
Tell user what the system expects right now.

Tell user that data has been entered correctly.
Tell user that data has not been entered correctly.
Explain reason for a delay in processing.
Tell user a task was completed or not completed.
Format screen so instructions and messages

always appear in same general display area.
Display messages and instructions long
enough so user can read them.
Jun 3, 2016
23
Human Engineering Guidelines (continued)

Use display attributes sparingly.
Default values should be specified.
Anticipate errors users might make.
Users should not be allowed to proceed without
correcting an error.
If user does something that could be catastrophic,
the keyboard should be locked to prevent any
further input, and an instruction to call the analyst
or technical support should be displayed.
Jun 3, 2016
24
User Interface Technology

Operating Systems and Web Browsers
GUI
Windows, Macintosh, UNIX, Linux, Palm OS, Windows CE
Growing importance of platform independence
Display Monitor
Regular PC monitors
Non-GUI terminals
Growing importance of devices such as handhelds
Paging Display complete screen of characters at a time.
Scrolling Display information up or down a screen one
line at a time.
Keyboards and Pointers

Mouse
Pens
Jun 3, 2016
25
Graphical User Interfaces Styles and

Considerations
Windows and frames
Menu-driven interfaces
Pull-down and
cascading menus
Tear-off and pop-up
menus
Toolbar and iconic
menus
Hypertext and hyperlink
menus
Instruction-driven
interfaces
Language-based syntax
Mnemonic syntax
Natural language syntax
Question-answer
dialogue
Jun 3, 2016
26
Special Considerations for

User Interface Design
Internal Controls
Authentication and
Authorization
User ID and
Password
Privileges assigned
to roles
Web certificates
Online Help
Growing use of
HTML for help
systems
Help authoring
packages
Tool tips
Help wizards
Agents reusable
software object that
can operate across
different applications
and networks.
Jun 3, 2016
27
Server Security Certificate
Jun 3, 2016
28
Help Tool Tip, Help Agent, and

Natural Language Processing
Jun 3, 2016
29
Help Wizard
Jun 3, 2016
30
Automated Tools for User Interface

Design & Prototyping
Microsoft
Access
CASE Tools
Visual
Studio
Excel
Visio
Jun 3, 2016
Visual
Studio .NET
Menu
Construction
31
Todays Outline
Define the appropriate format and media for a computer input.

Explain the difference between data capture, data entry, and data input.
Identify and describe several automatic data collection technologies.
Apply human factors to the design of computer inputs.
Design internal controls for computer inputs , output, and interface.
Select proper screen-based controls for input attributes that are to appear on
a GUI input screen.
Design a web-based input interface.
Identify several important human engineering factors and guidelines and
incorporate them into a design of a user interface.
Understand the role of operating systems, web browsers, and other
technologies for user interface design.
Describe how prototyping can be used to design a user interface.
Jun 3, 2016
32

Materi System and Design Method

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Materi System and Design Method

Hochgeladen von

Copyright:

Verfügbare Formate

System Analysis and

Hamzah Ritchi-System Analysis&Design Methods

Hamzah Ritchi Accounting Padjadjaran University

Define the appropriate format and media for a computer input.

Hamzah Ritchi-System Analysis&

Hamzah Ritchi-System Analysis&

Input Design Process

4. As necessary design source documents.

Hamzah Ritchi-System Analysis&

Data Capture and Data Entry

Data entry the process of translating the

Hamzah Ritchi-System Analysis&

Hamzah Ritchi-System Analysis&

Optical character recognition (OCR)

Hamzah Ritchi-System Analysis&

Taxonomy for Computer Inputs

Data is usually captured on

Data is entered via

OLD: Data can be collected

Used in conjunction with

Same as above, but the use of

Data is entered o a touch

On PCs, touch screen choices

Hamzah Ritchi-System Analysis&

Taxonomy for Computer Inputs (continued)

Data captured as close

Data is often entered directly by

Data is almost always

Data is captured as close

Data is entered using touchtones (typically from a

Data is almost always

Data (and commands) is

Data is almost always

Taxonomy for Computer Inputs (concluded)

Data usually prerecorded

A magnetic ink reader reads

Data is recorded directly

Data is transmitted by radio

Data is almost always

Data is recorded directly

Data is read by smart card

Data is almost always

Data read by biometric

Input Design Guidelines

Do not capture data that can calculated or

Use codes for appropriate attributes.

Hamzah Ritchi-System Analysis&

Hamzah Ritchi-System Analysis&

Bad Flow in a Form

Hamzah Ritchi-System Analysis&

Good Flow in a Form

Hamzah Ritchi-System Analysis&

Internal Controls for Inputs

For batch processing

Validate all data

Hamzah Ritchi-System Analysis&

Common GUI Controls (Windows and Web)

Courtesy of Palupi, Yoza and Natalie, 2007

Hamzah Ritchi-System Analysis&

Common GUI Controls Uses

When the input data values are unlimited in scope

When data has limited predefined set of mutually exclusive

When value set consists of a simple yes or no value

When data has a large number of possible values