All of the following are characteristics for consideration when designing forms and reports except

We’ve updated our privacy policy so that we are compliant with changing global privacy regulations and to provide you with insight into the limited ways in which we use your data.

You can read the details below. By accepting, you agree to the updated privacy policy.

Thank you!

View updated privacy policy

We've encountered a problem, please try again.

  • School Syracuse University
  • Course Title IST 352
  • Type

    Notes

  • Pages 5
  • Ratings 100% (1) 1 out of 1 people found this document helpful

This preview shows page 1 - 2 out of 5 pages.

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

When designing forms and reports, the task characteristic addresses:

A. activities that differ in the amount of information that must be obtained from or provided to the user
B. the platform in which the system is constructed influencing interaction styles and devices
C. issues related to experience, skills, motivation, education, and personality
D. social issues such as the user's status and role, lighting, sound, task interruptions, temperature, and humidity

When designing forms and reports, the system characteristic addresses:

A. issues related to experience, skills, motivation, education, and personality
B. the platform in which the system is constructed influencing interaction styles and devices
C. social issues such as the user's status and role, lighting, sound, task interruptions, temperature, and humidity
D. job activities that differ in the amount of information that must be obtained from or provided to the user

When designing forms and reports, the environment characteristic addresses:

A. the platform in which the system is constructed influencing interaction styles and devices
B. issues related to experience, skills, motivation, education, and personality
C. social issues such as the user's status and role, lighting, sound, task interruptions, temperature, and humidity
D. job activities that differ in the amount of information that must be obtained from or provided to the user

When designing forms and reports, the user characteristic addresses:

A. social issues such as the user's status and role, lighting, sound, task interruptions, temperature, and humidity
B. the platform in which the system is constructed, influencing interaction styles and devices
C. job activities that differ in the amount of information that must be obtained from or provided to the user
D. issues related to experience, skills, motivation, education, and personality

What are the four guidelines for good form design?

To design forms that people find useful, four guidelines for form design should be observed:.
Make forms easy to fill in..
Ensure that forms meet the purpose for which they are designed..
Design forms to ensure accurate completion..
Keep forms attractive..

Which of the following are the guidelines for displaying tables?

Answer: a. Which of the following are general guidelines for displaying tables and lists? All columns and rows should have meaningful labels . One of the guidelines for displaying lists and tables are using meaningful labels for rows and columns along with formatting or rows and columns.

Is an overall evaluation of how a system performs in supporting a particular user for a particular task?

Reliability is an overall evaluation of how a system performs in supporting a particular user for a particular task. Referencing form and report usability, the consistency guideline means that formatting should be designed with an understanding of the task being performed and the intended user.