1 / 20

Chapter 6 DB System Development: Forms and Reports

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

meda
Télécharger la présentation

Chapter 6 DB System Development: Forms and Reports

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. University of ManitobaAsper School of Business3500 DBMSBob Travica Chapter 6 DB System Development: Forms and Reports Based on G. Post, DBMS: Designing & Building Business Applications Updated 2014 1

  2. Basic Concepts • 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

  3. Uses of Forms • Collect Data • Display Query Results • Display Analysis and Computations • Switchboard for other Forms and Reports

  4. 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 Human Factors Design(Recall knowledge of SA&D!)

  5. “Forgiveness” Anticipation and correction of errors Confirmation on delete and updates Backup and recovery Feedback to user Methods Visual Text Audio Uses Acceptance of input Changes to data Completion of tasks Events / Activation Human Factors Design

  6. 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… Graphical User Interface Standards

  7. 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: Navigation errors around a screen or across screens (menus’links, menu form [pull-down, tabs], screen design (clickable icons) in using a new interface Time on Task Learningspeed Knowledge retention Satisfaction (subjective, qualitative) Usability of User Interface

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

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

  10. Window components Frame (sizing) Title bar Control-menu box Buttons Maximize Minimize Close Scroll box (thumb) Scroll bar Windows Interface

  11. Message Forms (“Boxes”) Title Message Simple buttons Icons Message Box (A Simple Form)

  12. Form Order Item 11 Dog 5 7 Dog 1 13 Cat 2 Form Layout • Types of Forms • Tabular • Single Row • Sub-forms (one-to-many) • Switchboard • Controls • Form Properties • Form Events

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

  14. 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) Single Row (Columnar) Form

  15. 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). Sub-Forms

  16. Role of main menu & sub-menus. Graphical elements (Logo) Purposes: Identify user Choose Task - serves as main menu Switchboard Form • Switchboard or Tab – it is the question now! (Hamlet  )

  17. Main Menu Sales 1. Setup Choices 2. Data Input 3. Print Reports 4. Utilities 5. Backups • Weekly Sales Reports • Daily Sales Reports • Friday Sales Meeting • Sales Prospects • Exit Menu Design Hard to understand More legible, organized by user tasks.

  18. 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 SaleID Date 1234 7/25/01 CustomerID 17 Carly Embry Use of Forms for Query

  19. Controls on Forms (Basic)

  20. Basic Controls Option Group (single response) Label Text Box Command Button Combo Box (click arrow to open) List Box (always open)

More Related