D
B
S
Y
S
T
E
M
S
University of Manitoba
Asper School of Business
3500 DBMS
Bob Travica
Chapter 6
DB System Development:
Forms and Reports
Based on G. Post, DBMS: Designing & Building Business Applications
Updated 2016
1 of 231
D
B
Basic Concepts
 Forms = input and output screens
S
Y
S
T
E
M
S
 Reports = output screens & paper
 The topic of forms & reports relates to building
a DB system - user interface & “applications”
(outputs that satisfy organizational information
needs)
 An important step in system development
2 of 23
D
B
S
Y
S
T
E
M
S
Uses of Forms
 Collect Data
 Display Query Results
 Display Analysis and Computations
 Switchboard for other Forms and Reports
3 of 23
D
B
S
Y
S
T
E
M
S
Human Factors Design
(Recall knowledge of SA&D!)
 Clarity
 Language used
 Graphical elements used
 Organization of elements
 Aesthetics
 Symmetry, balance of
elements
 Shapes & colors
 User Control
 Match user tasks.
 Application responds to user
control & events.
 User customization
 Consistency
 Layout design & colors
 Actions
4 of 23
D
B
S
Y
S
T
E
M
S
Human Factors Design
 Feedback to user
 Methods
 Visual
 Text
 Audio
 Uses
 Acceptance of input
 Changes to data
 Completion of tasks
 Events / Activation
 “Forgiveness”
 Anticipation and correction
of errors
 Confirmation on delete and
updates
 Backup and recovery
5 of 23
D
B
S
Y
S
T
E
M
S
Graphical User Interface Standards
MS Windows Interface:
 Navigation and Choices
 Mouse, Icons clicking
 Keyboard, Short-cuts
 Menus
 Manipulation methods:
 Point & click
 Drag and Drop
 Touch screen
 System feedback to user:
 Progress indicators and
status gauges
 Flashing
 Tool tips
 Status bar
 Message forms…
6 of 23
D
B
Usability of User Interface
 A special method within the human factors approach
S
Y
S
T
E
M
S
 Started at Sun Microsystems (Jacob Nielsen)
 Usability testing consists of measuring certain dimensions of usercomputer interaction while the user performs a task:
1. Navigation errors around a screen or across screens (menus’
links, menu form [pull-down, tabs], screen design (clickable
icons) in using a new interface
2. Time on Task
3. Learning speed
4. Knowledge retention
5. Satisfaction (subjective, qualitative)
7 of 23
D
B
The goal of usability testing is to identify problematic
parts of user interface that need improvement.
Simple Usability Test
S
Y
S
T
E
M
S
• Get the user use an important input of output screen
• Ask the user to speak aloud as s/he is working with the form
• Record errors in navigation, time on task, and user‘s comments
• Ask the user how s/he feels about working with that screen, and why so
• If you identify problems, that already is a finding
• Think of ways of eliminating problems – redesign; usability test can`t give
solutions.
8 of 23
D
B
S
Y
S
T
E
M
S
Interface / Accessibility Usability for Physically Challenged Persons
 Recommendations based on empirical data:
 Beware of Red/Green indifference for some people
(avoid to base the meaning to be conveyed on
differentiating these).
 Avoid requiring rapid user responses.
 Avoid rapid flashing on the screen.
 Give options to users (color, typefaces, fonts)
 Make users feel in control (locus of control dimension)
9 of 23
D
B
Windows Interface
 Window components
S
Y
S
T
E
M
S
 Frame (sizing)
 Title bar
 Control-menu box
 Buttons
 Maximize
 Minimize
 Close
 Scroll box (thumb)
 Scroll bar
10 of 23
D
B
Message Box (A Simple Form)
 Message Forms (“Boxes”)
S
Y
S
T
E
M
S




Title
Message text
Buttons
Images
11 of 23
D
B
Form Layout
 Types of Forms
S
Y
S
T
E
M
S




Tabular
Single Row
Sub-forms (one-to-many)
Switchboard
 Controls
 Form Properties
 Form Events
Form
Order
Item
11
7
13
Dog
Dog
Cat
5
1
2
12 of 23
D
B
S
Y
S
T
E
M
S
Tabular Form
 Works best for single table.
 Designer can control data entry sequence.
 Probably include buttons for sorting.
13 of 23
D
B
S
Y
S
T
E
M
S
Single Row (Columnar) Form
 Data for only one row.
 Legible
 Designer can set optimal
layout.
 Similar in appearance to
paper forms.
 Can use color, graphics, and
command buttons to make
the form easier to use.
 Note the navigation buttons
(consider implementing them)
14 of 23
D
B
S
Y
S
T
E
M
S
Sub-Forms
 Typically a one-to-many relationship.
 Subform contents are linked to the main form through a common
column (not displayed on the subform.)
 Can have multiple subforms (Independent or Nested).
15 of 23
D
B
S
Y
S
T
E
M
S
Switchboard Form
 Role of main menu & submenus.
 Graphical elements (Logo)
 Purposes:
 Identify user
 Choose Task serves as main menu
• Switchboard or Tab – it is the question now!
16 of 23
D
B
Menu Design
Main Menu
S
Y
S
T
E
M
S
Sales
1.
Setup Choices
• Weekly Sales Reports
2.
Data Input
• Daily Sales Reports
3.
Print Reports
• Friday Sales Meeting
4.
Utilities
• Sales Prospects
5.
Backups
• Exit
Hard to understand
More legible, organized by
user tasks.
17 of 23
D
B
S
Y
S
T
E
M
S
Use of Forms for Query
Customer Order
OrderID 1234 Date 7/25/01
CustomerID 17
 Clerk enters a CustomerID.
 Stored in the Order table.
 Query joins Sale and
Customer.
 Automatically matches the
CustomerID.
 Matching name is
displayed on the form.
 Do not include the join
column (CustomerID) from
Customer.
18 of 23
D
B
S
Y
S
T
E
M
S
Controls on Forms (Basic)
Label
Text box
Option group
Toggle button
Option button
Check box
Combo box
List box
Command
button
Picture
Unbound object Bound object
Page break
Tab control
Subform
Line
Box
More controls
19 of 23
D
B
S
Y
S
T
E
M
S
Basic Controls
Label
Text Box
Option Group
(single response)
Command
Button
Combo Box
(click arrow to open)
List Box
(always open)
20 of 23
D
B
S
Y
S
T
E
M
S
Menu Design
• Tabs, Switchboard, standard forms linked
• Navigation tabs in Access 2103 (each executes a query/report)
• Command buttons (button control)
21 of 23