Ad-hoc reports provide details behind the summary values on a key-indicator or exception report.

Designing forms and reportsDesigndatabasesforms and reportsdialogues and interfacesdistributed and internet systemsForm:business document that contains some predefined data and may include some areaswhere additional data are to be filled in.- an instance of a form is typically based on one db record.Report:business document that contains only predefined data.- a passive document used solely for reading or viewing data.A report typically contains data from many unrelated records or transactions.Common types of reports:scheduled:produced at predefined time intervals for routine information needskey-indicator: provides summary of critical info on regular basisexception:highlights data outside of normal operating rangesdrill-down:provides details behind summary of key-indicator or exception reports.ad-hoc:responds to unplanned requests for non-routine info needs.Process of designing forms and reports-user focused activity-follows a prototyping approach.-1st steps are to gain an understanding if the intended user and task objectives bycollecting initial requirements duringrequirements determinationrequirement determination:-who will use form/ report?-what is purpose of form/report?-when is report needed or used?-where does form/report need to be delivered and used?-how many people need to use or view form/report?prototyping-initial prototype designed from requirements-users review prototype design and either accept the design orrequest changes-if changes are requested the construction evaluation - refinementcycle is repeated until the design is accepted.acoding sheetis an “old” tool for designing forms/reports, usually associated with text-based forms and reports for mainframe applications.

Upload your study docs or become a

Course Hero member to access this document

Upload your study docs or become a

Course Hero member to access this document

End of preview. Want to read all 5 pages?

Upload your study docs or become a

Course Hero member to access this document

Tags

data integrity, alphanumeric data, data integrity rules, routine information needs

CHAPTER 10

Designing Forms and Reports

- Form: a business document that contains some predefined data and may include some areas where

additional data are to be filled in (an instance of a form is typically based on one database record)

- Report: a business document that contains only predefined data (it is a passive document used solely for

reading or viewing data); typically contains data from many unrelated records or transactions

- Common Types of Reports:

●Scheduled: produced at predefined time intervals for routine information needs

●Key-indicator: provides a summary of critical information on regular basis

●Exception: highlights data outside of normal operating ranges

●Drill-down: provides details behind summary of key-indicator or exception reports

●Ad-hoc: a “what if;” responds to unplanned requests for non-routine information needs

The Process of Designing Forms and Reports

- Is a user-focused activity. Follows a prototyping approach. First steps are to gain an understanding of the

intended user and task objectives by collecting initial requirements during requirements determination.

- Requires Determination: Who will use the form or report? What is the purpose of the form or report? When is

the report needed or used? Where does the form or report a need to be delivered and used? How many

people need to use or view the form or report?

- Prototyping:

●Initial prototype is designed from requirements.

●Users review prototype design and either accept the design or request changes.

●If changes are requested, the construction-evaluation-refinement cycle is repeated until the design is

accepted.

- A coding sheet is an “old” tool for designing forms and reports, usually associated with text-based forms and

reports for mainframe applications.

- Visual Basic and other development tools provide computer-aided GUI form and report generation.

Deliverables and Outcomes

- Design specifications are the major deliverables and inputs to the system implementation phase. Design

specifications have three sections:

●Narrative overview: characterizes users, tasks, system, and environmental factors

●Sample design: image of the form (from coding sheet or form building development tool)

●Testing and usability assessment: measuring test/usability results (consistency, sufficiency, accuracy,

etc.)

Formatting Forms and Reports

- Meaningful titles — use clear, specific, version information, and current date

- Meaningful information — include only necessary information, with no need to modify

- Balanced layout — use adequate spacing, margins, and clear labels

- Easy navigation system — show how to move forward and backward, and where you are currently

Highlighting Information

- Notify users of errors in data entry or processing, provide warnings regarding possible problems, draw

attention to keywords, commands, high-priority messages, unusual data values. Highlighting can include:

upper case, bold, italics, underlining, etc.

Colors vs. No Color

- benefits of color:

- downfalls of color: color pairings may wash out or cause problems for some users, resolution may degrade

with different displays, color fidelity may degrade on different displays, printing or conversion to other media

may not easily translate.

Which of the following report provides details behind the summary values on a key indicator?

What is form and report in system analysis and design?

When displaying textual information we should also be careful not to hyphenate?

Which of the following are the guidelines for displaying tables?