OUTPUT DESIGN
-
Upload
chester-dunlap -
Category
Documents
-
view
41 -
download
3
description
Transcript of OUTPUT DESIGN
![Page 1: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/1.jpg)
1
OUTPUT DESIGN
1
![Page 2: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/2.jpg)
2
Characteristics of Output(Output Design Considerations)
1. Accessibility - how easy is it to use?
2. Timeliness - is it available in time?
3. Relevance - is it helpful?
4. Accuracy - is it error-free?
5. Usability - is it in an acceptable format?
6. Cost effectiveness – is it cost effective to produce?
2
![Page 3: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/3.jpg)
3
Introduction
• Outputs present information to system
users.
• Outputs are the most visible component of
a working information system.
• Often the basis for the users’ and
management final assessment of the
system’s value.3
![Page 4: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/4.jpg)
4
Checklist for Output Design1. What is the purpose of the output?
2. Who or what wants this information, why is it needed, and how will it be used?
3. What information will be included?
4. What format should be used?
5. When will information be provided, and how often must it be updated?
6. Will simultaneous user access be required?
7. Are there security or confidentiality issues involved that need to be considered?
4
![Page 5: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/5.jpg)
5
Classification of Printed Reports
Reports can be classified by content
1.Detail reports – Example: A listing of all
customers Present information with little
or no filtering or restrictions.
Some detailed reports are historical in
nature.
5
![Page 6: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/6.jpg)
6
Detailed reports confirm and document the
successful processing of transactions and serve as
an audit trail for subsequent management inquiry.
–These reports assist management planning and
controlling by generating schedules and analysis.
•Other detailed reports are regulatory, that is,
required by government.
![Page 7: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/7.jpg)
7
2. Exception reports - An internal output
that filters data to report exceptions to
some condition or standard. Example: A
listing of customers with past due
accounts
![Page 8: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/8.jpg)
8
3.Summary reports - increasingly presented in graphical
formats using charts, Example: A count of customers by
region
4.Combination – has a flavor of detailed and summary. It
maybe a summary report with drill down capability
Examples : Detailed report where exceptions are
highlighted, Summary report where exceptions are
highlighted.
8
![Page 9: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/9.jpg)
9
Reports also can be classified by
distribution
1. Internal reports – an output intended for
system owners and system users within
an organization e.g. memos.
9
![Page 10: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/10.jpg)
10
2.External reports – an output that leaves the
organization
– Intended for customers, suppliers, partners, or
regulatory agencies
3.Turnaround reports – an external output that may re-
enter the system as an input.
– Most “bills” and invoices include a stub to be
returned by the customer with payment
![Page 11: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/11.jpg)
11
DETAIL REPORT
11
![Page 12: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/12.jpg)
12
Control Breaks
12
![Page 13: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/13.jpg)
13
Identify Fields
13
![Page 14: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/14.jpg)
1414
![Page 15: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/15.jpg)
15
Summary Report with Drill Down to the Detailed Report
15
![Page 16: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/16.jpg)
16
Output Media and FormatsA good systems analyst will consider all available options for implementing an output, especially output medium and output format.
A medium is what the output information is recorded on, such as paper or video display device.
Format is the way the information is displayed on a medium for instance, columns of numbers. The selection of an appropriate medium and format for an output depends on how the output will be used and when it is needed.
![Page 17: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/17.jpg)
17
Distribution
Delivery
Internal Output (reporting)
Turnaround Output (external; then internal)
External Output (transactions)
Printer Detailed, summary, or exception information printed on hard-copy reports for internal business use.
Business transactions printed on business forms that will eventually be returned as input business transactions.
Business transactions printed on business forms that conclude the business transactions.
Screen Detailed, summary, or exception information displayed on monitors for internal business use.
Business transactions displayed on monitors in forms or windows that will also be used to input other data to initiate a related transaction.
Business transactions displayed on business forms that conclude the business transactions.
Point-of-Sale Terminals
Information printed or displayed on special-purpose terminals dedicated to specific internal business functions.
Information printed or displayed on a special-purpose terminal for the purpose of initiating a follow-up business transaction.
Information printed or displayed on special-purpose terminals dedicated to customers.
17
![Page 18: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/18.jpg)
18
Distribution
Delivery
Internal Output (reporting)
Turnaround Output (external; then internal)
External Output (transactions)
Multimedia(audio or video)
Information transformed into speech for internal users.
Information transformed into speech for external users who respond with speech or tone input data.
Information transformed into speech for external users.
E-mail Displayed messages related to internal business information.
Displayed messages intended to initiate business transactions.
Displayed messages related to business transactions.
Hyperlinks Web-based links to internal information that is enabled via HTML or XML formats.
Web-based links incorporated into Web-based input pages to provide users with access to additional information.
Web-based links incorporated into Web-based transactions.
Microfiche Archival of internal management reports to microfilm that requires minimal physical storage space.
Not applicable unless there is an internal need to archive turnaround documents.
Not applicable unless there is an internal need for copies of external reports. 18
![Page 19: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/19.jpg)
19
Chart Types
19
Line charts show one or more series of data over a period of time. They are useful for summarizing and showing data at regular intervals. Each line represents one series or category of data.
Area charts are similar to line charts except that the focus is on the area under the line. That area is useful for summarizing and showing the change in data over time. Each line represents one series or category of data.
![Page 20: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/20.jpg)
20
Bar charts are useful for comparing series or categories of data. Each bar represents on series or category of data.
Column charts are similar to bar charts except that the bars are vertical. Also, a series of column charts may be used to compare the same categories at different times or time intervals. Each bar represents one series or category of data.
20
![Page 21: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/21.jpg)
21
Pie charts show the relationship of parts to a whole. They are useful for summarizing percentages of a whole within a single series of data. Each slice represents one item in that series of data.
Donut charts are similar to pie charts except that they can show multiple series or categories of data, each as its own concentric ring. Within each ring, a slice of that ring represents one item in that series of data.
21
![Page 22: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/22.jpg)
22
Radar charts are useful for comparing different aspects of more than one series or category of data. Each data series is represented as a geometric shape around a central point. Multiple series are overlaid so they can be compared.
Scatter charts are useful for showing the relationship between two or more series or categories of data measured at uneven intervals of time. Each series is represented by data points using either different colors or bullets.
22
![Page 23: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/23.jpg)
23
A selection of Charts
![Page 24: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/24.jpg)
24
Sample of Column Charts
![Page 25: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/25.jpg)
25
Sample Pie charts
![Page 26: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/26.jpg)
26
Sample of Bar charts
![Page 27: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/27.jpg)
27
Sample line charts
![Page 28: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/28.jpg)
28
Sample scatter charts
![Page 29: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/29.jpg)
29
Output Design Guidelines1. Outputs should be simple to read and interpret.
Include a title.
Date and time stamp.
Include sections and headings to segment
information.
Clearly label all fields and columns.
Include legends for all abbreviations.
29
![Page 30: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/30.jpg)
30
Include only required information. And provide methods to expand and contract information.
Report information in format that does not have to be manually edited.
Information should be balanced across the page or screen.
Provide for easy navigation.
Avoid computer jargon and error messages.
30
![Page 31: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/31.jpg)
31
2. The timing of outputs is important.
• This can affect how the output is designed and
implemented
3. The distribution of (or access to) outputs must be
sufficient to assist all relevant users. - The choice of
implementation method affects distribution
4. Outputs must be acceptable to the system users who
will receive them.
• Systems analyst must understand how the recipient
plans to use the output
![Page 32: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/32.jpg)
32
Output Design Process
1.Identify system outputs and review logical
requirements.
2.Specify physical output requirements.
3.As necessary, design any preprinted forms.
4.Design, validate and test outputs using
some combination of:
32
![Page 33: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/33.jpg)
33
Output Design Process….
Layout tools (e.g., hand sketches,
spacing charts, or CASE tools.
Prototyping tools (e.g., spreadsheet,
PC DBMS, 4GL)
Code generating tools (e.g., report
writer)
33
![Page 34: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/34.jpg)
34
Tabular Report Design PrinciplesDesign Issue Design Guideline Examples
Page Size Today the page sizes of choice are standard (8½" x 11") and legal (8½" x 4").
Not applicable
Page Orientation Portrait orientation is often preferred because it is oriented the way we orient most books and reports; however, landscape is often necessitated for tabular reports because more columns can be printed.
Page Headings At a minimum, page headers should include a recognizable report title, date and time, and page numbers.
Report Legends A legend is an explanation of abbreviations, colors, or codes used in a report. In a printed report, a legend can be printed on only the first or last page. On a display screen, a legend can be made available as a pop-up dialogue box.
portrait landscape
JAN 4, 2004
Page 4 of 8Oversubscriptions By Course
REPORT LEGENDSEATS – Number of seats in classroomLIM – Course Enrollment Limit
![Page 35: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/35.jpg)
35
Tabular Report Design Principles
35
Design Issue Design Guideline Examples
Column Headings
Column headings should be short and descriptive. Avoid abbreviations or include a Report Legend
Self-explanatory
Heading Alignments
Alignment should be tested with users for preferences with a special emphasis on the risk of misinterpretation of the information.
Column Spacing If columns are too close, users may not properly differentiate between the columns. If they are too far apart, the user may have difficulty following a single row. Rule of thumb is to use 3-5 spaces between each.
Self explanatory
Row Headings The first one or two columns should identify data that differentiates each row. Rows should be sequenced in a fashion that supports their use. Frequently rows are sorted on a numerical key or alphabetically.
NAMEXXXXXXX XXXXXX
AMOUNT$X.XX
STATUSX
STUDENT ID STUDENT NAME999-38-8476 Mary Ellen Kukow999-39-5857 Robert Flynn
![Page 36: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/36.jpg)
36
Design Issue Design Guideline Examples
Formatting Data is often stored without formatting characters to save storage space. Outputs should reformat data to match the users’ norms.
Control Breaks Groups of rows should be logically grouped in the report. The transition from one group to the next is called a control break and is frequently followed by subtotals for the group.
End of Report The end of a report should be clearly indicated to ensure that users have the entire report.
As stored: As output:307877262 307-87-72628004445454 (800) 444-545402272004 Feb 27, 2004
*** END OF REPORT ***
RANK NAMESALARY
CPT JANEWAY, K175,000
CPT KIRK, J225,000
CPT PICARD, J200,000
CPT SISKO, B165,000CAPTAINS TOTAL765,000
LTC CHAKOTAY110,000
OTC DATA125,000
LTC RICKER, W140,000
LTC SPOCK, S155,000EXEC OFFCR TOTAL530,000
36
![Page 37: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/37.jpg)
37
Screen Output Design Principles
37
Screen Design Consideration
Design Guidelines
Size The designer should consider the “lowest common denominator.” The default window size should be less than or equal to the worst resolution display in the user community.
Scrolling On-line outputs have the advantage of not being limited by the physical page. This can also be a disadvantage if important information such as column headings scrolls off the screen. If possible, freeze important headings at the top of a screen.
Navigation Users should always have a sense of where they are in a network of on-line screens. Users also require the ability to navigate between screens.
Partitioning In Windows, zones are forms within forms. On the Internet, frames are pages within pages.
Information Hiding
On-line applications offer capabilities to hide information until it is either needed or becomes important. Techniques include drill-down and pop-up dialogue boxes.
Highlighting Highlighting can call users’ attention to erroneous data, exception data, or specific problems. Highlighting can also be a distraction if misused.
Printing Always provide users the option to print a permanent copy of the report.
![Page 38: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/38.jpg)
38
Report Customization
38
![Page 39: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/39.jpg)
39
Graphical Report Prototype
39
![Page 40: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/40.jpg)
40
Record-at-a-Time Output Prototype
40
![Page 41: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/41.jpg)
41
Choosing Technology
a) Will it be stored? If so, how long?
b) Are there any restrictions regarding the
production, storage, or distribution of
the output?
c) Are there any environmental
requirements on creating the output?
41
![Page 42: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/42.jpg)
42
Choosing Technology….
• Acoustic noise, smell, space,
electromagnetic noise, temperature,
connections to other equipment
d) What cost is acceptable for creating the
output
• Consider both initial and maintenance
costs, and the cost of supplies
42
![Page 43: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/43.jpg)
43
Avoiding Bias
Outputs can introduce unintentional bias
from the analyst who designs them
We want to avoid that bias consciously
– How information is sorted
– Setting limits (business rules)
– Choice of graphics
43
![Page 44: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/44.jpg)
44
Sorting Information
Output data are often sorted by cost, time,
or alphabetically
The manner chosen to present results can
place accidental emphasis on output results
Hence many business names start with
multiple A’s, so they show up first in the
Yellow Pages
44
![Page 45: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/45.jpg)
45
Setting Limits
The limits used to generate output (e.g. determine the scope of what is presented) can introduce bias
Often such limits are based on business rules– How long overdue is ‘too much’ for a bill?
A week? A month?– How old are sales records before being
moved to an archive? A year? Five years?
45
![Page 46: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/46.jpg)
46
Choice of Graphics
The way data are presented can introduce severe bias in their interpretation– See also How to Lie with Statistics, Huff
& Geis, ISBN 0393310728
46
Message: Sales are diving!
Gross Sales ($M)
190
192
194
196
198
200
202
2000 2001 2002 2003 2004
Message: Sales are pretty stable
Gross Sales ($M)
0
50
100
150
200
250
2000 2001 2002 2003 2004
![Page 47: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/47.jpg)
47
Choice of Graphics
The absence of a Y axis scale leaves a lot to the imagination
47Message: Can’t tell!
Gross Sales ($M)
186
188
190
192
194
196
198
200
202
2000 2001 2002 2003 2004
![Page 48: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/48.jpg)
48
Choice of Graphics
Comparison to a goal or objective can make a big difference in interpretation
48
Sales History
0
50
100
150
200
250
2000 2001 2002 2003 2004
Sales
Message: Sales are declining recently
Sales Compared to Goal
0
50
100
150
200
250
2000 2001 2002 2003 2004
Sales
Sales Goal
Message: Sales are getting closer to our
goals
![Page 49: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/49.jpg)
49
Avoiding Bias
So to avoid bias in the design of outputs
1. Be aware of the sources of bias
2. Get users involved in the design of
outputs
3. Establish clear sources and specific
business rules for getting and
presenting data
49
![Page 50: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/50.jpg)
50
Avoiding Bias….
4. If desired, create flexible output so
users can change limits or ranges
5. Encourage users to have multiple data
views
50
![Page 51: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/51.jpg)
51
Prototype & Design Computer Outputs
Step 1: Identify System Outputs The DFDs identify output requirements
that must be designed. These outputs can easily be identified by
examining the DFD for data flows that are connecting to external entities.
The designer may have to interview users and to brainstorm outputs of the system.
Examine data model.
![Page 52: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/52.jpg)
52
Prototype & Design Computer Outputs
Step 2: Select Output Medium and Format
The decision for the best output medium and
format is based on:
The type and purpose of the output.
The technical and economic feasibility.
![Page 53: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/53.jpg)
53
Several design issues need to be addressed.What medium would best serve the output?What would be the best format for the report?How frequently is the output generated?How many pages or sheets of output will be generated
for a single copy of a report?Does the output require multiple copies?For printed outputs, have distribution controls been
finalized?For attributes contained on the output, what format
should be followed?
53
![Page 54: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/54.jpg)
54
Prototype & Design Computer Outputs Step 3: Prototype The Output for System
Users
The format or layout of an output directly affects
the system user's ability to read and interpret it.
The best way to lay out outputs is to sketch or,
better still, generate a sample of the report or
document via prototyping.
![Page 55: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/55.jpg)
55
When prototyping outputs, it is important to involve the user to obtain feedback.
The user should be allowed to actually exercise or test the screens.
Part of that experience should involve: Demonstration of how the user may obtain
appropriate help or instructions, Drill-down to obtain additional information, Navigate through pages, Request different formats that are available Size the outputs,
Perform test customization capabilities. 55
![Page 56: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/56.jpg)
56
Output ControlsOutput Integrity
1. Ensure output is correct, complete, & secure
2. Include appropriate titles and dates on reports
3. Number pages consecutively
4. Identify the end of each report
5. Print/reconcile control totals/record counts
6. Create error file to flag uncorrected/reentered records
7. Review error reports for possible causes
56
![Page 57: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/57.jpg)
57
Output Controls: Output Security
1. Protects privacy rights and proprietary data
2. Output must be accurate, complete, current, and secure
3. The IT department is responsible for output control and security measures
4. Many companies have installed diskless workstations
57
![Page 58: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/58.jpg)
58
Output Controls: Output Security5. Important tasks to carry out
a) Control the number of report copies
b) Distribute reports only to authorized users
c) Store sensitive reports in secure areas
d) Label all pages of confidential reports
e) Burn/shred sensitive reports & other output
f) Inventory blank checks regularly
g) Store signature forms securely
6. Output security
58
![Page 59: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/59.jpg)
59
Output Integrity Controls
Ensures output arrives at proper destination and is correct, accurate, complete, and current
Destination controls - output is channeled to correct people
Completeness, accuracy, and correctness controls
Appropriate information present on output
59
![Page 60: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/60.jpg)
OUTPUT DESIGN OPTIONS FOR PHYSICALLY CHALLENGED
Adaptive Technology consists of Input and output devices designed for computer users who are physically challenged . They benefit users with blindness, low vision, learning disabilities, speech and hearing impairments and mobility.
The Kenya Constitution ideally should provided for the physically challenged, consideration therefore when choosing an output media It is important to consider the user.
60
![Page 61: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/61.jpg)
OUTPUT DESIGN OPTIONS FOR PHYSICALLY CHALLENGED
i.e. jaws software which converts the output into audio and makes it easy for them to use a computer.
Hearing impaired users can instruct programs to display words instead of sounds
Blind users can work with voice output- the computer reads information displayed on the
screen
61
![Page 62: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/62.jpg)
OUTPUT DESIGN OPTIONS FOR PHYSICALLY CHALLENGED
For Visually impaired users there is also a Braille printer that prints information on paper in Braille
For windows there are accessibility options physically challenged user can set options to make programs easier to use .
Display options-visually impaired users can change the size or color of text to make words easier to read
62
![Page 63: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/63.jpg)
OUTPUT DESIGN OPTIONS FOR PHYSICALLY CHALLENGED
Eye Tracking -Multifunctional gaze controlled Interface-whenever the user looks at one of the keys at a specific minimum duration the corresponding letter will be typed. Gaze control zooming in and out to view a map or picture at different resolutions.
Head mounted pointer controls pointer on screen
63
![Page 64: OUTPUT DESIGN](https://reader038.fdocuments.net/reader038/viewer/2022103006/568137de550346895d9f8050/html5/thumbnails/64.jpg)
64
Thank You
END
64