MIS 3371 Transaction Processing Systems Vocabulary

Vocabulary flashcards covering core transaction processing concepts, transaction states, three-tier architecture, transaction data types, and internal controls from MIS 3371 Sessions 1 and 2.

Transaction

A discrete business event that the business needs to remember (a recordable event) or commits business state.

Business Rules

Directives that translate organizational policy into decisions the system must enforce to decide whether a transaction will proceed.

Validation

Automatic computer checks that determine if input data is complete, usable, and properly formatted before processing.

Draft State

The transaction state where a user has started entering data but has not yet submitted it.

Submitted State

The transaction state where the system has accepted the request.

Processing State

The transaction state where work and logic execution are actively underway.

Completed State

The transaction state where the business event has successfully finished.

Rejected State

The transaction state resulting when a business rule or authorization check fails.

Failed State

The transaction state resulting when a technical problem stops processing.

Presentation Tier

The front-end layer (HTML, CSS, forms, browser interactions) that owns the user experience, collects input, and displays output, but should not be trusted as the final authority.

Application Tier

The back-end layer that owns business processing, enforces critical rules, authorizes operations, and calculates results.

Data Tier

The layer that owns persistent records, storing transaction data, status, timestamps, relationships, and audit history.

Business Data

Data provided by the user or process, including customer/employee ID, item, date, amount, quantity, category, and comments.

Control Data

Data that helps the system manage the transaction, including status, unique transaction ID, approval level, and source/channel.

Audit Data

Data that helps reconstruct what happened, including created/modified by details, previous values, timestamps, and history logs.

Preventive Controls

Internal controls designed to stop a problem before it happens, such as authorization, input limits, and duplicate prevention.

Detective Controls

Internal controls designed to discover that something went wrong, such as audit logs, reconciliation, exception reports, and fraud alerts.

Corrective Controls

Internal controls designed to restore or compensate after a problem occurs, such as rollbacks, backup recovery, manual correction, and reversing transactions.