Chapter 6 DB System Development: Forms and Reports

20
D D B B S S Y Y S S T T E E M M S S 1 of 23 Chapter 6 DB System Development: Forms and Reports 1 Based on G. Post, DBMS: Designing & Building Business Applications University of Manitoba Asper School of Business 3500 DBMS Bob Travica Updated 2015

description

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 2014. 1. Basic Concepts. Forms = input and output screens Reports = output screens & paper - PowerPoint PPT Presentation

Transcript of Chapter 6 DB System Development: Forms and Reports

Page 1: Chapter 6 DB System Development: Forms and Reports

DDBB

SSYYSSTTEEMMSS

1 of 23

Chapter 6

DB System Development:Forms and Reports

1

Based on G. Post, DBMS: Designing & Building Business Applications

University of ManitobaAsper School of Business

3500 DBMSBob Travica

Updated 2015

Page 2: Chapter 6 DB System Development: Forms and Reports

DDBB

SSYYSSTTEEMMSS

2 of 23

Forms = input and output screens 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

Basic Concepts

Page 3: Chapter 6 DB System Development: Forms and Reports

DDBB

SSYYSSTTEEMMSS

3 of 23

Uses of Forms

Collect Data

Display Query Results

Display Analysis and Computations

Switchboard for other Forms and Reports

Page 4: Chapter 6 DB System Development: Forms and Reports

DDBB

SSYYSSTTEEMMSS

4 of 23

Human Factors Design(Recall knowledge of SA&D!)

User Control Match user tasks. Application responds to user

control & events. User customization

Consistency Layout design & colors Actions

Clarity Language used Graphical elements used Organization of elements

Aesthetics Symmetry, balance of

elements Shapes & colors

Page 5: Chapter 6 DB System Development: Forms and Reports

DDBB

SSYYSSTTEEMMSS

5 of 23

Human Factors Design

“Forgiveness” Anticipation and correction

of errors Confirmation on delete and

updates Backup and recovery

Feedback to user Methods

VisualTextAudio

UsesAcceptance of inputChanges to dataCompletion of tasksEvents / Activation

Page 6: Chapter 6 DB System Development: Forms and Reports

DDBB

SSYYSSTTEEMMSS

6 of 23

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…

Page 7: Chapter 6 DB System Development: Forms and Reports

DDBB

SSYYSSTTEEMMSS

7 of 23

Usability of User Interface A special method within the human factors approach

Started at Sun Microsystems (Jacob Nielsen) Usability testing consists of measuring certain dimensions of user-

computer 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)

Page 8: Chapter 6 DB System Development: Forms and Reports

DDBB

SSYYSSTTEEMMSS

8 of 23

The goal of usability testing is to identify problematic parts of user interface that need improvement.

Simple Usability Test

• 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.

Page 9: Chapter 6 DB System Development: Forms and Reports

DDBB

SSYYSSTTEEMMSS

9 of 23

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)

Page 10: Chapter 6 DB System Development: Forms and Reports

DDBB

SSYYSSTTEEMMSS

10 of 23

Windows Interface

Window componentsFrame (sizing)Title barControl-menu boxButtons

MaximizeMinimizeCloseScroll box (thumb)Scroll bar

Page 11: Chapter 6 DB System Development: Forms and Reports

DDBB

SSYYSSTTEEMMSS

11 of 23

Message Box (A Simple Form)

Message Forms (“Boxes”) Title Message text Buttons Images

Page 12: Chapter 6 DB System Development: Forms and Reports

DDBB

SSYYSSTTEEMMSS

12 of 23

Form Layout

Types of Forms Tabular Single Row Sub-forms (one-to-many) Switchboard

Controls Form Properties Form Events

Form

Order

11 Dog 5 7 Dog 113 Cat 2

Item

Page 13: Chapter 6 DB System Development: Forms and Reports

DDBB

SSYYSSTTEEMMSS

13 of 23

Tabular Form Works best for single table. Designer can control data entry sequence. Probably include buttons for sorting.

Page 14: Chapter 6 DB System Development: Forms and Reports

DDBB

SSYYSSTTEEMMSS

14 of 23

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)

Page 15: Chapter 6 DB System Development: Forms and Reports

DDBB

SSYYSSTTEEMMSS

15 of 23

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).

Page 16: Chapter 6 DB System Development: Forms and Reports

DDBB

SSYYSSTTEEMMSS

16 of 23

Switchboard Form

Role of main menu & sub-menus.

Graphical elements (Logo)

Purposes: Identify user

Choose Task -

serves as main menu

• Switchboard or Tab – it is the question now!

Page 17: Chapter 6 DB System Development: Forms and Reports

DDBB

SSYYSSTTEEMMSS

17 of 23

Menu Design

1. Setup Choices

2. Data Input

3. Print Reports

4. Utilities

5. Backups

Main Menu

• Weekly Sales Reports

• Daily Sales Reports

• Friday Sales Meeting

• Sales Prospects

• Exit

Sales

Hard to understand More legible, organized by user tasks.

Page 18: Chapter 6 DB System Development: Forms and Reports

DDBB

SSYYSSTTEEMMSS

18 of 23

Use of Forms for Query

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.

Customer Order

1234OrderID 7/25/01Date

Page 19: Chapter 6 DB System Development: Forms and Reports

DDBB

SSYYSSTTEEMMSS

19 of 23

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 SubformLine Box More controls

Page 20: Chapter 6 DB System Development: Forms and Reports

DDBB

SSYYSSTTEEMMSS

20 of 23

Basic ControlsLabel

Text BoxOption Group(single response)

Combo Box(click arrow to open)

List Box(always open)

CommandButton