Chapter 7
UNDERSTANDING
AND DESIGNING
FORMS
Input Forms: Content
and Organization
Need for forms
Event analysis and forms
Relationship between input
forms and tables
Types of input forms:
 Single-record entry form
 Tabular entry forms
 Multi-table entry forms
Input Forms: Content
and Organization
Means of data entry:
 4 ways to enter data
1. Internal agent types in
the data
2. Internal agent selects
data to be entered using
a look-up table, radio
button, or check box
3. Internal agent scans the
bar code of a product or
the identification card of
a customer
4. User enters the data
using a form at the
company’s Web site
Input Forms: Content
and Organization
Identifying forms required:
 The need depends on
 What data need to be
collected and
 How the data will be
collected
 A UML use case is a
sequence of steps
 A use case diagram is a
graphical presentation
providing a list of use cases
that occur in an application
 CRUD framework: a tool
used as an aid in
developing use case
diagrams
Input Forms: Content
and Organization





Documenting form
content and organization
- form design template:
Attributes recorded in
tables
Attributes displayed from
tables
Calculated fields
Foreign keys
Queries
Interaction with Forms:
Controlling AIS Inputs
Form interface elements:
 Text boxes
 Labels
 Look-up feature
 Command buttons
 Radio buttons
 Check boxes
Interaction with Forms:
Controlling AIS Inputs








Improving accuracy and
efficiency of data entry:
Primary key
Look-up feature
Scanning
Record-checking
Confirmation
Referential integrity
Format checks
Validation rules
Interaction with Forms:
Controlling AIS Inputs




Improving accuracy and
efficiency of data entry:
Defaults
 Application-level default
 Agent-level default
 Transaction-level default
Prohibit blank fields
Computer-generated
values
Prompt user to
accept/reject data
Interaction with Forms:
Controlling AIS Inputs

Input controls and
workflow controls:
Key difference
 Input controls refer to
checks performed
automatically by the
computer itself
Designing Forms
Identify and document forms
required
Single-record date entry form
– maintenance of manager
table
Single-record form – deposit
form
Tabular data entry form –
inventory maintenance
Multi-table entry form
KEYTERMS






Check boxes
Command buttons
Computer-generated
values
Confirmation
CRUD
Default
KEYTERMS









Form
Form interface elements
Format checks
Join query
Look-up feature
Main form
Multi-table entry form
Radio buttons
Record checking
KEYTERMS








Referential integrity
Single-record entry form
Subform
Tabular entry form
Use case
Use case description
Use case diagram
Validation rule