SAD ch 8-10

What is the difference between a detail report, a summary report, and an exception repot?

- A detail report contains one or more lines of output for each record processes, can be quite lengthy. - A summary report is used by higher level individuals like managers, so it therefore contains less detail than reports used by lower-level employees. Contains bottom line totals and other statistical analysis. - An exception report contains records that meet a specific condition, useful for when users want information only on records requiring action but that does not need details.

online data entry

A data entry method used for most business activity. The online method offers major advantages, including the immediate validation and availability of data.

relational database

A database in which tables are related by common fields, creating a unified data structure that provides improved data quality and access.

Human-computer interaction (HCI)

A description of the relationship between computers and the people who use them to perform business-related tasks. HCI concepts apply to everything from a PC desktop to the main menu for a global network.

detail report

A detail report produces one or more lines of output for each record processed.

control break report

A detail report that focuses on control breaks.

exception report

A document displaying only those records that meet a specific condition or conditions. Exception reports are useful when the user wants information only on records that might require action but does not need to know the details.

Context-sensitive

A feature that is sensitive to the current conditions when it is invoked. For example, context-sensitive help offers assistance for a task in progress.

file-oriented systems

A file-oriented system, also called a file processing system, stores and manages data in one or more separate files.

source document

A form used to request and collect input data, trigger or authorize an input action, and provide a record of the original transaction. During the input design stage, you develop source documents that are easy to complete and inexpensive.

batch

A group of data, usually inputted into an information system at the same time.

query by example (QBE)

A language allows the user to provide an example of the data requested.

data validation rule

A mechanism to improve input quality by testing the data and rejecting any entry that fails to meet specified conditions.

relational model

A model used in relational databases. The relational model was introduced during the 1970s and became popular because it was flexible and powerful.

modules

A module consists of related program code organized into small units that are easy to understand and maintain. A complex program could have hundreds or even thousands of modules.

diskless workstation

A network terminal that supports a full-featured user interface but limits the printing or copying of data, except to certain network resources that can be monitored and controlled more easily.

webcast

A one-way transmission of information or training materials, such as a Webinar session, available on demand or for a specific period to online participants.

source data automation

A popular online input method that combines online data entry and automated data capture using input devices such as magnetic data strips or swipe scanners.

batch input

A process where data entry is performed on a specified time schedule, such as daily, weekly, monthly, or longer. For example, batch input occurs when a payroll department collects time cards at the end of the week and enters the data as a batch.

Structured Query Language (SQL)

A query language that allows PC users to communicate with servers and mainframe computers.

audit trails

A record of the source of each data item and when it entered a system. In addition to recording the original source, an audit trail must show how and when data is accessed or changed, and by whom. All these actions must be logged in an audit trail file and monitored carefully.

character-based reports

A report created using a single mono-spaced character set.

summary report

A report used by individuals at higher levels in the organization that includes less detail than reports used by lower-level employees.

menu bars

A set of user-selectable software application options, usually located across the top of the screen.

natural language

A software feature that allows users to type commands or requests in normal English (or other language) phrases.

java database connectivity (JDBC)

A standard that enables Java applications to exchange data with any database that uses SQL statements and is ODBC-compliant.

faxback

A system that allows a customer to request a fax using email, the company website, or a telephone. The response is transmitted in a matter of seconds back to the user's fax machine. See automated fax.

automated fax

A system that allows a customer to request a fax using email, the company website, or a telephone. The response is transmitted in a matter of seconds back to the user's fax machine. See faxback.

user-centered

A term that indicates the primary focus is upon the user. In a user-centered system, the distinction blurs between input, output, and the interface itself.

Batch controls

A total used to verify batch input. Batch controls might check data items such as record counts and numeric field totals. For example, before entering a batch of orders, a user might calculate the total number of orders and the sum of all the order quantities. When the batch of orders is entered, the order system also calculates the same two totals. If the system totals do not match the input totals, then a data entry error has occurred.

Why is a transparent interface desirable?

A transparent interface is desirable because it is not distracting to the user and therefore isn't really noticed by the user.

reasonableness check

A type of data validation check that identifies values that are questionable but not necessarily wrong. For example, input payment values of $0.05 and $5,000,000.00 both pass a simple limit check for a payment value greater than zero, and yet both values could be errors.

combination check

A type of data validation check that is performed on two or more fields to ensure that they are consistent or reasonable when considered together. Even though all the fields involved in a combination check might pass their individual validation checks, the combination of the field values might be inconsistent or unreasonable.

validity check

A type of data validation check that is used for data items that must have certain values. For example, if an inventory system has 20 valid item classes, then any input item that does not match one of the valid classes will fail the check.

existence check

A type of data validation check that is used for mandatory data items. For example, if an employee record requires a Social Security number, an existence check would not allow the user to save the record until he or she enters a suitable value in the SSN field.

data type check

A type of data validation check that is used to ensure that a data item fits the required data type. For example, a numeric field must have only numbers or numeric symbols, and an alphabetic field can contain only the characters A through Z or the characters a through z.

sequence check

A type of data validation check that is used when the data must be in some predetermined sequence. If the user must enter work orders in numerical sequence, for example, then an out-of-sequence order number indicates an error. If the user must enter transactions chronologically, then a transaction with an out-of-sequence date indicates an error.

range check

A type of data validation check that tests data items to verify that they fall between a specified minimum and maximum value. The daily hours worked by an employee, for example, must fall within the range of 0 to 24.

transparent interface

A user interface that users don't really notice—a user-friendly interface that does not distract the user and calls no attention to itself.

default value

A value that a system displays automatically.

form filling

A very effective method of online data entry where a blank form that duplicates or resembles the source document is completed on the screen. The user enters the data and then moves to the next field.

subschema

A view of the database used by one or more systems or users. A subschema defines only those portions of the database that a particular system or user needs or is allowed to access.

podcast

A web-based broadcast that allows a user to receive audio or multimedia files using music player software such as iTunes, and listen to them on a PC or download them to a portable MP3 player or smart phone.

usability metrics

Data that interface designers can obtain by using software that can record and measure user interactions with the system.

file

Each file or table contains data about people, places, things, or events that interact with the information system.

table

Each file or table contains data about people, places, things, or events that interact with the information system.

What is HCI?

HCI, or Human-computer interaction refers to the relationship between humans and computers in performing business-related tasks.

Data security

Protection of data from loss or damage and recovers data when it is lost or damaged.

option button

Radio buttons that represent groups of options. The user can select only one option at a time; a selected option contains a black dot. See also radio button.

What are seven habits of successful interface designers?

The 7 habits of successful interface designers are as follows: 1. Understanding the business 2. Maximizing graphical effectiveness 3. Thinking like a user 4. Using models and prototypes 5. Focusing on usability 6. Inviting feedback 7. Documenting everything

mock-up

When designing a report, a sample report is prepared, which is a mock-up, or prototype, for users to review. The sample should include typical field values and contain enough records to show all the design features.

control break

A control break usually causes specific actions to occur, such as printing subtotals for a group of records.

data manipulation language (DML)

A DML controls database operations, including storing, retrieving, updating, and deleting data. Most commercial DBMSs, such as Oracle and IBM's DB2, use a DML.

toolbar

A GUI element that contains icons or buttons that represent shortcuts for executing common commands.

toggle button

A GUI element used to represent on or off status. Clicking the toggle button switches to the other status.

calendar control

A calendar control allows the user to select a date that the system will display and store as a field value.

database management system (DBMS)

A collection of tools, features, and interfaces that enables users to add, update, manage, access, and analyze data in a database.

turnaround documents

Output document that is later entered back into the same or another information system. A telephone or utility bill, for example, might be a turnaround document printed by the company's billing system. When the bill is returned with payment, it is scanned into the company's accounts receivable system to record the payment accurately.

dialog box

Allows a user to enter information about a task that a system will perform.

query language

Allows a user to specify a task without specifying how the task will be accomplished. Some query languages use natural language commands that resemble ordinary English sentences.

common field

An attribute that appears in more than one entity. Common fields can be used to link entities in various types of relationships.

electronic health records (EHRs)

An electronic record of a patient's health information generated as the patient encounters various health-care providers and shared among multiple facilities and agencies.

Open database connectivity (ODBC)

An industry-standard protocol that makes it possible for software from different vendors to interact and exchange data.

radio frequency identification(RFID) tags

An input device used in source data automation.

blogs

An online journal. The term is a contraction of "web log."

list boxes

An output mechanism that displays a list of choices that the user can select.

report header

Appears at the beginning of a report and identifies the report as well as the report title, date, and other necessary information.

page footer

Appears at the bottom of the page and is used to display the name of the report and the page number.

report footer

Appears at the end of the report, can include grand totals for numeric fields and other end-of-report information.

page header

Appears at the top of the page and includes the column headings that identify the data.

Output security

Output security protects privacy rights and shields the organization's proprietary data from theft or unauthorized access.

authorization zone

Part of a form that contains any required signatures.

radio button

Buttons that represent groups of options. The user can select only one option at a time; a selected option contains a black dot. See also option button.

System prototyping

Producing a full-featured, working model of the information system being developed.

throwaway prototyping

Creating a prototype of user requirements, after which the prototype is discarded and implementation continues. Also called throwaway prototyping. See design prototyping.

design prototyping

Creating a prototype of user requirements, after which the prototype is discarded and implementation continues. Also called throwaway prototyping. See throwaway prototyping.

How would you rank the 10 guidelines for user interface design in order of importance. Explain your answer.

I would rank the 10 guidelines from most to least important as follows: 1. Create an interface easy to learn and use (most important) 2. Provide users with help and feedback 3. Manage data effectively 4. Reduce input volume 5. Create an attractive layout and design 6. Focus on data entry screens 7. Enhance user productivity 8. Enhance the interface 9. Use validation rules 10. Provide flexibility Although every guideline is important for user interface design, I decided on ranking them the way I did because I wanted to show an emphasis on making the interface very user friendly. After making the interface easy to use and understand, I believe that the data management and activities are the next most important aspects, because not having the data organized and figured out would lead to disaster.

totals zone

If a form has data totals, they will appear in this section of the form.

control field order

In a control break report, the records are arranged or sorted in the same order as the control fields.

scroll bar

In user interface design, a scroll bar allows the user to move through the available choices for an input field.

usability

In user interface design, includes user satisfaction, support for business functions, and system effectiveness.

output control

Methods to maintain output integrity and security. For example, every report should include an appropriate title, report number or code, printing date, and time period covered. Reports should have pages that are numbered consecutively, identified as Page xx of xx, and the end of the report should be labeled clearly.

hash totals

Not meaningful numbers themselves but are useful for comparison purposes. Also known as batch control totals.

limit check

Occurs when a validation check involves a minimum or a maximum value, but not both. Checking that a payment amount is greater than zero, but not specifying a maximum value, is an example of a limit check.

command button

Onscreen button that initiates an action such as printing a form or requesting Help.

records retention policy

Rules designed to meet all legal requirements and business needs for keeping records.

database administrator (DBA)

Someone who manages a DBMS. The DBA assesses overall requirements and maintains the database for the benefit of the entire organization rather than a single department or user.

input mask

Template or pattern that makes it easier for users to enter data. Often used in automated forms to guide an unfamiliar user.

schema

The complete definition of a database, including descriptions of all fields, records, and relationships.

garbage in, garbage out (GIGO)

The concept that the quality of the output is only as good as the quality of the input.

economy of scale

The inherent efficiency of high-volume processing on larger computers. Database design allows better utilization of hardware. If a company maintains an enterprise-wide database, processing is less expensive using a powerful mainframe server instead of using several smaller computers.

What are the main principles of source document design?

The main principles of source document design typically consists of the layout, placement of sections - left to right, accessibility, and user-friendly. Heading zone which contains the company name/logo and the title and number of the form. The control zone contains codes, identification information, numbers, and dates. The instruction zone contains instructions for completing the form. The body zone contains captions and areas for entering variable data. Totals are in the totals zone, and the authorization zone contains any signatures.

user interface (UI)

The mechanism through which the user interacts with the system. The interface can be graphical, textual, aural, or a combination of different modes of interaction.

Prototyping

The method by which a prototype is developed. It involves a repetitive sequence of analysis, design, modeling, and testing. It is a common technique that can be used to design anything from a new home to a computer network.

Input control

The necessary measures to ensure that input data is correct, complete, and secure. A systems analyst must focus on input control during every phase of input design, starting with source documents that promote data accuracy and quality.

form layout

The physical appearance and placement of data on a form. Form layout makes the form easy to complete and provides enough space, both vertically and horizontally, for users to enter the data.

switchboard

The use of command buttons in a user interface to enable users to navigate a system and select from groups of related tasks.

graphical user interface (GUI)

The use of graphical objects and techniques allowing users to communicate with a system. A well-designed GUI can help users learn a new system rapidly and work with the system effectively.

What are three emerging trends in user interface design?

Three emerging trends in user interface design include modular design, which means modules are created that connect to a higher-level program, responsive web design, which means to render web content properly, independently of the device in use, and prototyping, which means producing an early constructed working version of an information system.

check boxes

Used to select one or more choices from a group. A check mark, or an X, represents selected options.