Exams Flashcards

(47 cards)

1
Q

Transaction Processing Systems

A

Capture/store routine transactions (order processing, billing, reservations).

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Knowledge Work Systems

A

Data mining tools or decision support systems that analyze sales trends and customer preferences.
Support professionals (engineers, lawyers, analysts) with design tools, spreadsheets, email.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Office Systems (OS):

A

Used by data workers (clerks, bookkeepers) for word processing, spreadsheets, document imaging.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Management Information Systems (MIS):

A

Summarize TPS data into reports (weekly/monthly sales, production, headcount).

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Decision Support Systems (DSS):

A

Help managers with semi-structured decisions (pricing, production scheduling).

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Executive Support Systems (ESS)

A

Executive dashboards showing long-term performance, profitability, and market share for strategic planning. Combine internal MIS + external data (market trends, legislation, confidence).

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Point-of Sale

A

is an operational‑level Transaction Processing System (TPS) that records daily sales, updates inventory, and processes payments.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

The Supply Chain (aka the Industry Value Chain)

A

is network of organizations and business processes for procuring raw materials, transforming raw materials into finished products
and distributing these products to customers.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Islands of automation.”

A

Ideally, systems should share data, but integration is often difficult, systems don’t communicate → duplicate/outdated data.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Middleware

A

(e.g., APIs, ETL processes) Software that connects different applications/systems, enabling communication and data exchange

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Enterprise Resource Planning system

A

Unified data repository, standardized processes, shared data with partners.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Complementary investments

A

Non-IT resources (training, organizational change, new processes) needed to realize IT benefits.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Business intelligence

A

automates reporting and analyze trends (e.g., peak hours, top sellers)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Scenario: CFO upset that income statements take 3 months; systems are incompatible.

A

What’s going on: The organization likely has disparate legacy systems that don’t integrate well. Data may be stored in different formats, across multiple platforms, requiring manual reconciliation. This causes delays.

Standardize data formats and adopt a centralized database for financial reporting.
Automate reporting with Business Intelligence (BI) tools to reduce manual work.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

POS Data → Trends & Patterns

A

Systems Required:
Data Warehouse: Stores large volumes of historical POS data
Business Intelligence (BI): Dashboards, visualizations
Data Mining Tools: Identify patterns, correlations, and product relationships

How It Works:
POS (TPS) captures daily transactions
Data is extracted, transformed, and loaded into a data warehouse
BI tools analyze trends (e.g., peak hours, top sellers)
Data mining identifies relationships (e.g., items bought together)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Why eCal Failed (10 marks)
The eCal project failed due to:

A

Lack of planning: No clear goals, objectives, or implementation strategy.
Poor implementation choice: No pilot testing or phased rollout.
Lack of complementary investments: Teachers were not trained, schools lacked WiFi, charging stations, and support resources.
Technology without organizational change: Devices alone cannot improve learning outcomes.

Improvements:
Conduct pilot testing
Provide teacher training
Ensure infrastructure (WiFi, support staff)
Set measurable goals and monitoring system

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

The specific choice (Make or Buy) depends on factors

A

The specific choice (Make or Buy) depends on factors like resources, capabilities, corporate strategy, time pressure, prices, culture, politics, and the business environment

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q
  1. Developing In-house (Make)
A

Organizations can develop systems internally using several methodologies:
* Traditional Development (SDLC): This is a phased, step-by-step approach used since the 1960s. It involves Identifying Problem/Opportunity, Conduct Investigation, Create Conceptual Design, Development, Testing, Implementation, and Maintenance. It is well understood but criticized as being too slow and costly.
* Agile Methods: Proposed as a solution to SDLC’s length, Agile focuses on speed not perfection. It uses small teams in an iterative process (e.g., Prototyping or Extreme programming). Many organizations use Agile for noncore systems and SDLC for critical systems, or use a hybrid methodology.
* End User Development: Users develop small, noncritical systems using simple tools like Microsoft Excel or Access.
* Open Source: Software that is shared, often free of charge, where any changes must be shared with the community (e.g., Moodle).

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q
  1. Acquiring Systems (Buy)
A

Alternatives to internal development include:
* Licensing: Acquiring the right to use “off the shelf” software (e.g., SAP ERP systems). This is often considerably faster and much less costly than in-house development because costs are amortized. A drawback is that the system may not be an “exact” match. Licensed systems often run on the organization’s own hardware.
* Outsourcing: Transferring systems and processes entirely to an external vendor (e.g., outsourcing registration to IBM).
* Software as a Service (SaaS): A relatively new form of outsourcing reliant on high-speed networks (usually the Internet). The entire application runs on the provider’s servers (e.g., Salesforce.com), and the customer connects via a web browser. SaaS removes much of the burden of funding, running, and maintaining the IS from the client organization.

20
Q

Scenario: Organization replacing its financial system

A

Custom-built system (tailored but costly, longer implementation).
Commercial off-the-shelf (COTS) software (e.g., SAP, Oracle Financials).
Open-source solutions (lower cost, flexible, but requires in-house expertise).
Cloud-based SaaS financial systems (scalable, subscription-based).

Factors to consider:
Cost (initial + maintenance).
Scalability and future growth.
Integration with existing systems.
Vendor support and reliability.
Security and compliance requirements.
User training and change management.

21
Q

(b) Alternatives to SDLC

A

Alternatives: Agile, Rapid Application Development (RAD), Prototyping, End-user development.
Advantages: Faster delivery, flexibility, user involvement, adaptability to change.
Disadvantages: Less documentation, harder to manage large projects, risk of scope creep, potential lack of structure

22
Q

Agile methods

A

Iterative, flexible software development approaches emphasizing collaboration, adaptability, and rapid delivery.

23
Q

SDLC

A

Structured process for developing information systems: planning, analysis, design, implementation, maintenance.

24
Q

ERP Implementation Method (SAP system)

A

Options: Big Bang, Phased, Parallel, Pilot.
Recommended: Phased implementation.
Reason: Lower risk, easier troubleshooting, gradual user adaptation.
Example: Start with accounting, then HR, then manufacturing.
Avoid the Big Bang unless resources and training are very strong.

25
Implementing a Supply Chain Management System
Considerations: Cost and budget constraints Integration with existing systems Training and change management Data migration and data quality Risk of downtime Vendor support and reliability Implementation Options: Big Bang: Entire system goes live at once Phased: Modules/locations implemented gradually Pilot: Test in one location before rollout Parallel: Old and new systems run together temporarily Recommendation: Phased implementation Lower risk Easier troubleshooting Allows gradual training Suitable for complex systems like SCM
26
Information Security: Protection of information assets. Key Goals (CIA Triad):
Confidentiality – only authorized access. Integrity – free from unauthorized changes. Availability – accessible when needed.
27
Why Systems Are Vulnerable
Internet – global, anonymous, insecure origins (ARPANET not designed for security). Hackers & Cyber Vandals – from bragging rights → organized crime, phishing, botnets. Computer Crime – laws now criminalize theft, destruction, denial of service. Cyberwar & Terrorism – attacks on grids, banks, telecom (e.g., Estonia 2007). Malicious Software – viruses, worms, trojans, spyware. Employees – intentional sabotage or accidental mistakes. Natural Disasters – fire, flood, hurricanes. Software Vulnerabilities – bugs, unpatched systems exploited. Business Value of Security System downtime = huge financial losses (e.g., eBay crash). Data loss can destroy companies. Compliance with laws (HIPAA, SOX, Gramm-Leach-Bliley, TT Computer Misuse Act, Data Protection Act). Avoid fines, reputational damage, cleanup costs.
28
Security Policy & Risk Analysis
Assets to protect. Access rights. Resources needed. Responsibility assignments.
29
Risk Analysis:
is the process of identifying, assessing, and prioritizing risks based on likelihood and impact to guide mitigation decisions. (financial, reputation) + likelihood. Strategies: contain, prevent, insure, backup.
30
Security Technologies
Access Control – authorization (least privilege), authentication (passwords, tokens, biometrics). Firewalls – monitor & filter traffic between networks. Intrusion Detection Systems (IDS) – tripwires, alerts, auto-shutdown. Antivirus – scans memory/email, but lag in updates. Public Key Encryption (PKE) – public/private keys, ensures secure communication. Backup – essential for recovery.
31
Management Challenges-Security
Balance between over-control (frustrating) vs under-control (vulnerable). Requires executive leadership, ongoing support, and policy enforcement.
32
Scenario: Scarce resources to protect dozens of information systems.
Answer: Methodology: Use Risk Assessment & Prioritization. Step 1: Identify all systems (critical vs. non-critical). Step 2: Assess risks (likelihood × impact). Step 3: Rank systems by risk score. Step 4: Allocate resources to high-risk/high-impact systems first. Example: Payroll system (critical, high risk of data breach) → allocate strong firewalls, encryption, monitoring. Marketing database (less critical, low risk) → basic access controls.
33
Firewall
Security device/software that monitors and controls incoming/outgoing network traffic based on rules, protecting systems from unauthorized access.
34
Threats
Any potential danger to information systems, such as malware, hackers, or insider misuse.
35
Tacit knowledge
Personal, experience-based knowledge that is difficult to codify (e.g., intuition, skills).
36
Safeguards for student computers (8 Marks) Four examples:
Antivirus/anti-malware software → protects against malicious code. Strong passwords + multi-factor authentication → ensures confidentiality. Regular backups (cloud or external drive) → ensures availability. Firewalls + encryption → protect integrity and prevent unauthorized access.
37
Security controls
technical, administrative, and physical safeguards that protect information systems and ensure confidentiality, integrity, and availability.
38
Malware
Malicious software (viruses, worms, trojans) designed to disrupt, damage, or gain unauthorized access.
39
Four threats to information assets:
Malware (viruses, worms). Phishing/social engineering. Unauthorized access/hacking. Hardware failure/data loss.
40
Four controls to reduce risks:
Install antivirus/firewall software. Use strong passwords + multi-factor authentication. Regular backups (cloud/external). Physical security & access controls.
41
ERP implementation
A typical ERP implementation involves planning, analyzing business processes, configuring the system, migrating data, testing, training users, going live using an appropriate strategy, and providing post‑implementation support.
42
End-user development
allows non‑programmers to build or modify simple applications using tools that require little technical expertise.
43
Expert systems
use AI rules and knowledge bases to mimic human expert decision‑making in specialized fields such as medicine or finance.
44
Alternatives to SDLC for SCM System
Agile: Iterative development with continuous feedback and rapid adaptation. DevOps: Integrates development and operations to automate deployment and improve speed. Rapid Application Development (RAD): Uses prototyping and fast iterations. CI/CD: Automates testing and deployment for frequent releases. Recommendation: Agile is most suitable because a supply chain system requires flexibility, continuous stakeholder input, and the ability to adapt quickly to changing business needs.
45
Allocating Limited Security Budget
Identify all systems and assets Identify threats Assess vulnerabilities Evaluate likelihood and impact Rank systems by risk score Allocate budget to the highest‑risk, highest‑impact systems first
46
IT Infrastructure for Fast‑Food Chain
POS systems for fast transactions and real‑time inventory Mobile ordering and payment for convenience CRM system for personalization and loyalty programs Employee management system for scheduling and payroll Supply chain management system for inventory and delivery tracking Cybersecurity tools to protect customer and business data
47
Best implementation srategy for fast food operations
For fast‑food operations, direct cut‑over is suitable because it minimizes confusion, reduces costs, and allows all locations to switch quickly—critical in a fast‑paced, high‑volume industry.