Management and Information Systems
Information systems questions test how data becomes decisions, what each system class does, how systems are built and secured, and how technology reshapes business processes.
Data, information, knowledge
Data are raw facts; information is data organized for a purpose; knowledge is information applied with judgment. Useful information is accurate, timely, relevant, complete, and cost-justified. A system's value comes from better decisions, not from hardware volume.
System types
Transaction processing systems capture routine transactions such as orders and payroll and are the source of most organizational data. Management information systems summarize transaction data into scheduled reports for middle managers. Decision support systems combine data, models, and interfaces for semi-structured problems such as what-if pricing. Executive information systems present high-level dashboards. ERP integrates finance, manufacturing, HR, and sales on one database; CRM manages customer interactions and sales pipelines; knowledge management captures expertise. E-commerce types include B2B, B2C, C2C, and B2G.
Building and running systems
The systems development life cycle runs planning, analysis, design, implementation, and maintenance, with maintenance consuming the largest share of lifetime cost. Alternatives include prototyping, agile iterations, and buying packaged software. A database is an organized collection managed by a DBMS, and the relational model stores data in tables linked by keys.
Security, privacy, and continuity
Protect confidentiality, integrity, and availability. Threats include malware, phishing, ransomware, insider misuse, and physical loss. Controls include authentication, encryption, firewalls, role-based access, audit logs, and patching. Backups, offsite replication, and tested disaster recovery plans protect continuity; a hot site is ready immediately, a cold site is not. Privacy law restricts personal data handling; healthcare falls under HIPAA, and publicly traded firms must safeguard financial records under Sarbanes-Oxley.
Worked example
A retailer's sales are falling. Transaction records show individual sales, MIS reports show the decline by week, and a DSS lets analysts test whether a 10% price cut or a loyalty promotion lifts margin more. The exam point is matching system class to decision type: routine reporting is MIS, while model-driven scenario testing is DSS.
Traps
Calling a transaction processing system a decision tool; assuming more data automatically improves decisions; treating firewalls as protection against internal fraud; and confusing a disaster recovery plan with a business continuity plan.