Systems Analysis andDesignSlides in this presentation containhyperlinks. JAWS users should beable to get a list of links by usingINSERT+F7Chapter 6:Designing Interfaces
Learning Objectives6.1 Explain the process of designing forms and reports and thedeliverables for their creation6.2Apply the general guidelines for formatting forms and reports6.3Use color and know when color improves the usability ofinformation6.4Format text, tables, and lists effectively6.5Explain how to assess usability and describe how variations inusers, tasks, technology, and environmental characteristicsinfluence the usability of forms and reports6.6Discuss guidelines for the design of forms and reports forInternet-based electronic commerce systems
Systems Development Life Cycle with LogicalDesign Phase Highlighted
Designing Interfaces: Forms andReports•Form– business document that contains some predefined data andmay include some areas where additional data are to be filled in. Aninstance of a form is typically based on one database record.–Usually in a stylized format and not a simple row and column look•Report– business document that contains only predefined data; it is apassive document used solely for reading or viewing. A report typicallycontains data from many unrelated records or transactions–Reports typically contain data from many unrelated records ortransactions
Common Types of Business ReportsReport NameDescriptionScheduled ReportsReports produced at predefined intervals—daily,weekly, or monthly—to support the routineinformational needs of an organization.Key-Indicator ReportsReports that provide a summary of criticalinformation on a recurring basis.Exception ReportsReports that highlight data that are out of thenormal operating range.Drill-Down ReportsReports that provide details behind the summaryvalues on a key-indicator or exception report.Ad-hoc ReportsUnplanned information requests in whichinformation is gathered to support a nonroutinedecision.
The Process of Designing Interfaces(1 of 3)•A user-centered activity that follows aprototypingapproach:–Understanding the target audience and their needs–Collect initial requirements–Structure and refine this information into an initial prototype–Users then evaluate the prototype–Make any needed refinements until users are satisfied andaccept the prototype
Fundamental Questions WhenDesigning Forms and Reports1.Who will use the form or report?2.What is the purpose of the form or report?3.When is the form or report needed and used?4.Where does the form or report need to be delivered andused?5.How many people need to use or view the form or report?
The Process of Designing Interfaces(2 of 3)•Paper prototype– series of mock screens that can beused to test content, look, and feel, as well as the taskflow and other usability factors–Focus is on the design (content, layout, flow)•Wireframe– simple design to show the placement ofinformation elements on a screen and the space neededfor each element–Allows users to get a sense and feel of a design
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 52 pages?
Upload your study docs or become a
Course Hero member to access this document
Notes
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