COMM 205 Lecture Notes - Lecture 3: Enterprise Resource Planning, User Friendly, Information Silo
Document Summary
Comm205 lecture 3: explain the purposes of transaction processing systems (tps) and its relationship with other information systems. A transaction (e. g. student registration, sales, funds transfer) is any business event that generates data worth being capture and stored in a database. A tps (cid:373)o(cid:374)itors, (cid:272)olle(cid:272)ts, stores a(cid:374)d pro(cid:272)esses data ge(cid:374)erated (cid:271)y ea(cid:272)h of the orga(cid:374)isatio(cid:374)"s (cid:271)asi(cid:272) business transactions, and can handle high volumes of data, avoid errors and provide a highly secure and stable environment. The data is i(cid:374)put to the orga(cid:374)isatio(cid:374)"s data(cid:271)ase. Database must be protected from errors resulting from overlapping or concurrent updates. Has to be protected from inconsistencies arising from system failure. An audit trail of transaction flow should be available. Performance: the number of transactions they can process within a period of time. Availability: system must be available whenever it is needed; system availability is the % of time that a system is active. Data integrity: refers to overall completeness, accuracy and consistency of data.
