Business Computing Foundations

Introduction

Modern banking, finance, and insurance organisations depend on computing for almost every significant activity. A bank uses computing systems to maintain customer accounts, process payments, assess credit risk, detect fraud, and comply with regulation. An insurer uses them to collect policy information, calculate premiums, manage claims, and analyse loss patterns. Finance departments use spreadsheets, databases, enterprise systems, and analytical software to support planning and reporting.

Computing is therefore not merely the operation of desktop computers. It is the coordinated use of hardware, software, data, networks, procedures, and people to capture, transform, store, communicate, and protect information. A business professional who understands these foundations can evaluate systems more intelligently, identify operational risks, communicate with technical specialists, and make better decisions about technology investments.

This chapter develops the basic concepts required for later study of databases, spreadsheets, information systems, networking, cybersecurity, business analytics, and digital banking.

Learning Objectives

By the end of this chapter, you should be able to:

1. Distinguish hardware, software, data, information, and information systems.
2. Explain the input–process–output–storage model of computing.
3. Describe the functions of the central processing unit, memory, storage, and input/output devices.
4. Compare common software categories and computing architectures.
5. Explain system performance, capacity, availability, and scalability.
6. Identify common file formats and select suitable formats for business purposes.
7. Explain how computing supports business processes in banking, finance, and insurance.
8. Discuss governance, security, ethical, and regulatory issues associated with business computing.

1. Computing as a Business Capability

A computer is an electronic system that follows instructions to manipulate data. Computing is the broader activity of using computational resources to perform tasks, solve problems, support communication, and generate information. In organisations, computing capability is embedded in business processes rather than isolated in an information technology department.

A useful distinction is between data and information. Data consists of recorded facts or symbols that have not necessarily been interpreted. Examples include a transaction amount of 2,500, a policy number, a date, or a customer’s risk score. Information is data that has been processed, organised, or interpreted so that it has meaning and value for a user. A list of transaction amounts is data; a report showing monthly transaction growth and unusual transactions is information.

Information is valuable when it is relevant, accurate, timely, complete, accessible, and appropriately protected. These qualities may conflict. For example, stronger access controls can reduce convenience, while rapid reporting may require decisions based on incomplete data. Business computing involves managing such trade-offs.

An information system is an organised combination of people, procedures, data, hardware, software, and communication networks that collects, processes, stores, and distributes information. The term is broader than “computer system” because it includes human activities and organisational rules. A loan-processing information system, for example, includes employees, lending policies, application forms, databases, credit-scoring software, servers, networks, and approval procedures.

2. The Input–Process–Output–Storage Model

The fundamental operating model of computing is often expressed as input, processing, output, and storage.

• Input is the capture of data or instructions.
• Processing is the transformation of input according to rules or algorithms.
• Output is the presentation or transmission of results.
• Storage is the retention of data, instructions, or results for later use.

The model is not always a simple sequence. In a banking application, a customer’s input may trigger processing, produce an approval message, store an audit record, and initiate another process such as sending a notification. Output can also become input to a later process.

Figure: The input–process–output–storage model applied to business computing.

Example: Processing a Card Transaction

When a customer uses a payment card, the terminal captures the card and transaction details. A processing system validates the account, checks available funds or credit, applies fraud rules, and requests authorisation. The result is returned to the merchant and customer. The transaction, decision, timestamps, and audit information are stored. Later, the stored data may be used for statements, reconciliation, regulatory reporting, and fraud analytics.

This example shows that output quality depends on more than processing speed. Incorrect input, outdated account data, defective rules, or insecure transmission can all produce an incorrect or harmful result.

3. Computer Hardware

Hardware comprises the physical components of a computing system. Hardware is commonly classified by function rather than by appearance.

3.1 The Central Processing Unit

The central processing unit (CPU) executes program instructions. Its principal elements include:

• the control unit, which directs the movement and execution of instructions;
• the arithmetic and logic unit (ALU), which performs arithmetic and logical comparisons;
• registers, which provide very small, fast storage for current instructions, addresses, and intermediate values;
• cache memory, which stores frequently used instructions and data close to the processing cores.

A CPU’s clock frequency, measured in hertz, indicates the number of clock cycles per second. A gigahertz (GHz) represents one billion cycles per second. Clock frequency alone does not determine performance: architecture, number of cores, instruction efficiency, cache behaviour, memory speed, and workload also matter.

A core is an independent processing unit within a CPU. Multiple cores can execute suitable tasks concurrently, but software must be designed to benefit from parallel execution. A four-core processor does not automatically make every program four times faster.

3.2 Primary Memory

Primary memory is directly accessible during processing. Random-access memory (RAM) holds programs and data currently in use. RAM is volatile: its contents normally disappear when power is removed. More RAM can allow a system to keep more active applications and datasets available, reducing reliance on slower storage. It does not, however, guarantee faster performance if the CPU, network, or software is the limiting factor.

Read-only memory (ROM) and firmware store low-level instructions required to start or control hardware. Modern firmware may be stored in rewritable non-volatile memory, but the functional distinction remains useful: firmware operates close to the hardware, while general application software supports user or business tasks.

3.3 Secondary Storage

Secondary storage retains data without continuous power. Common technologies include:

• hard disk drives (HDDs), which use magnetic rotating platters;
• solid-state drives (SSDs), which use flash memory and have no moving parts;
• removable media and external drives;
• network-attached and cloud-based storage.

Storage should be evaluated by capacity, speed, reliability, cost, portability, durability, and security. A high-capacity device is not necessarily appropriate for confidential customer data unless encryption, access control, backup, and disposal procedures are also addressed.

3.4 Input and Output Devices

Input devices include keyboards, touchscreens, scanners, cameras, microphones, biometric readers, barcode readers, and sensors. In financial services, optical character recognition may capture information from forms, while application programming interfaces may receive data directly from another system.

Output devices include displays, printers, speakers, dashboards, electronic messages, and machine-to-machine responses. A system’s output must be understandable and suitable for its intended user. A compliance analyst may require an auditable report, while a customer may require a concise notification.

3.5 Buses, Ports, and Peripheral Communication

Internal buses and external interfaces transfer data between components. Examples include USB, HDMI, Ethernet, and wireless interfaces. These interfaces support peripherals and communication networks. Compatibility involves more than a physical connection; devices also require compatible protocols, drivers, power, and security settings.

4. Software and Programming Logic

Software is a set of instructions and related data that directs hardware to perform tasks. It is intangible, but it must be designed, tested, maintained, documented, and governed.

4.1 System Software

System software manages hardware and provides a platform for applications. An operating system (OS) manages processes, memory, files, devices, users, and security. Examples include desktop, server, mobile, and specialised operating systems.

A device driver allows the operating system to communicate with a particular hardware device. Utility software performs supporting functions such as backup, compression, monitoring, encryption, and malware detection.

4.2 Application Software

Application software serves a user or business purpose. Examples include word processors, spreadsheets, accounting systems, customer relationship management systems, banking platforms, enterprise resource planning systems, and claims-management systems.

Application software may be:

• general-purpose, such as spreadsheet and word-processing software;
• special-purpose, such as a loan-origination system;
• custom-developed, designed for a particular organisation;
• commercial off-the-shelf, acquired and configured for organisational use;
• web-based or cloud-hosted, accessed through a browser or application interface.

Each choice involves trade-offs among cost, flexibility, control, integration, maintenance, and vendor dependence.

4.3 Algorithms and Programs

An algorithm is a finite, ordered set of instructions for solving a problem or performing a task. A program implements algorithms in a programming language. In a credit application, an algorithm might retrieve applicant data, apply eligibility rules, calculate affordability indicators, and route the application for review.

Algorithms are not automatically objective. They reflect the data, assumptions, definitions, and objectives chosen by their designers. In financial services, algorithmic decisions therefore require validation, monitoring, explainability where appropriate, and controls against unfair discrimination.

5. Data Representation and File Formats

Computers represent information digitally using bits. A bit is a binary digit with a value of 0 or 1. A group of eight bits is commonly called a byte. Prefixes such as kilobyte, megabyte, gigabyte, and terabyte describe increasing storage quantities, although decimal and binary conventions differ. In formal specifications, users should check whether a vendor uses decimal units, where 1 kilobyte = 1,000 bytes, or binary units such as 1 kibibyte = 1,024 bytes.

Text is encoded using standards such as Unicode, which supports a wide range of writing systems and symbols. Numbers, images, sound, and video are also encoded as binary data. A file is a structured collection of data stored under a name, usually with a format identified by an extension or metadata.

File format selection should reflect purpose. A PDF may be suitable for a final customer statement, while CSV or JSON may be better for system integration. A spreadsheet may support analysis but is not automatically an appropriate system of record. File naming conventions, version control, metadata, retention, encryption, and access rights are part of information governance.

6. Computing Architectures

A computing architecture describes how components are arranged and how responsibilities are distributed.

6.1 Stand-Alone and Client–Server Systems

A stand-alone computer performs most processing locally. This can be useful for personal productivity but may create duplication and weak central control.

In a client–server architecture, client devices request services from servers. A browser may act as a client, while an application server processes requests and a database server stores records. Centralisation can improve control and consistency, but server failure or network disruption may affect many users.

6.2 Two-Tier and Three-Tier Architectures

In a two-tier design, a client communicates directly with a server, often combining presentation and application functions at the client. A three-tier design separates:

1. the presentation layer, which handles user interaction;
2. the application or business-logic layer, which applies rules;
3. the data layer, which manages stored data.

Separation can improve maintainability, security, and scalability. For example, a bank may update an interest-calculation service without redesigning every customer-facing screen.

6.3 Cloud and Distributed Computing

Cloud computing provides computing resources such as storage, processing, and software through network-accessible services. Common service models are:

• Infrastructure as a Service (IaaS): virtual machines, networks, and storage;
• Platform as a Service (PaaS): managed development and runtime environments;
• Software as a Service (SaaS): complete applications delivered to users.

Cloud services can offer elasticity, rapid deployment, and access to specialised capabilities. They also introduce concerns about data location, service availability, contractual responsibility, identity management, concentration risk, and exit planning.

Distributed computing divides processing or storage across multiple connected computers. Edge computing places some processing near the source of data, which can reduce latency and network traffic. Architectures may also use containers, microservices, application programming interfaces, and event-driven processing. These approaches can improve flexibility but increase operational complexity.

7. System Performance and Capacity

Performance is the extent to which a system completes work effectively within required time and resource constraints. Common measures include response time, throughput, capacity, utilisation, availability, and scalability.

• Response time is the time between a request and the corresponding result.
• Throughput is the amount of work completed per unit of time, such as transactions per second.
• Capacity is the maximum sustainable workload under specified conditions.
• Availability is the proportion of required time during which a service is operational.
• Scalability is the ability to handle increased workload by adding resources or improving design.

A simple availability relationship is:

Here, uptime and downtime must be measured over the same defined period and in consistent time units. If a service operates for 720 hours and is unavailable for 3 hours, availability is 720 ÷ 723 ≈ 99.585%. If the organisation defines availability only during business hours, the result will differ; therefore, the measurement window and exclusions must be specified.

Performance bottlenecks may occur in the CPU, memory, storage, database, network, application design, or external service. Effective diagnosis measures the system rather than assuming that replacing one component will solve every problem.

Reliability concerns the probability that a system performs correctly for a specified period and environment. Fault tolerance is the ability to continue operating when a component fails. Redundancy provides additional components or paths so that one failure does not necessarily stop service. Backups support recovery but are not the same as redundancy: a backup may restore data after an incident, whereas redundancy may maintain service during the incident.

8. Information Systems in Business Organisations

Business systems can be considered at several organisational levels:

• Transaction processing systems (TPS) record routine transactions such as deposits, withdrawals, premium payments, and claims.
• Management information systems (MIS) summarise operational data into regular reports.
• Decision support systems (DSS) help analyse alternatives using models, scenarios, and data.
• Executive or strategic information systems provide high-level indicators for senior decision-makers.
• Enterprise systems integrate functions such as finance, procurement, human resources, and customer management.

An organisation’s systems should support its processes and objectives. Technology alone does not fix a badly designed process. Process mapping can reveal duplicated data entry, unnecessary approvals, unclear ownership, and control weaknesses.

For banking, finance, and insurance, computing supports:

• customer onboarding and identity verification;
• account, policy, and claims administration;
• payment clearing and settlement;
• credit assessment and underwriting;
• financial accounting and reconciliation;
• risk modelling and stress testing;
• fraud and money-laundering monitoring;
• regulatory and management reporting;
• customer service through portals, mobile applications, and contact centres.

9. Applied Case: Improving a Small Insurer’s Claims Process

This is an illustrative case.

Background

Harbour Mutual is a small insurer processing motor claims through email, spreadsheets, and paper documents. Claims staff re-enter customer, vehicle, and payment information into several files. Managers receive weekly summaries prepared manually.

Problem

The process creates duplicated work, inconsistent claim statuses, delayed payments, and weak visibility of sensitive documents. A spreadsheet formula error caused several claims to be assigned to the wrong review queue. Management also could not reliably determine the average time from notification to settlement.

Analysis

The input–process–output model identifies several weaknesses. Inputs are inconsistent because customers and staff use different forms. Processing is partly manual and rules are embedded in undocumented spreadsheet formulas. Outputs are delayed and may not agree across reports. Storage is fragmented across email inboxes, local drives, and shared folders.

The insurer’s requirements are not simply “buy software.” It needs standardised data definitions, controlled workflows, audit trails, role-based access, document retention, backup, and integration with payment and policy systems.

Approach and Solution

Harbour Mutual implements a claims-management application with a three-tier architecture. A web interface captures structured claim information. An application layer applies routing and validation rules. A database stores claim records, while encrypted document storage retains photographs and supporting evidence.

The organisation also introduces:

1. a standard digital claims form;
2. validation rules for policy numbers, dates, and payment details;
3. role-based access for claim handlers, supervisors, and finance staff;
4. an audit log recording changes to claim status and payment decisions;
5. daily backups and tested recovery procedures;
6. dashboards showing open claims, ageing, settlement time, and exception cases;
7. staff training and a procedure for correcting inaccurate records.

Outcome

The new process reduces repeated data entry and gives managers a consistent view of claims. Automated validation prevents common errors, while human review remains necessary for complex or high-value cases. The insurer can calculate performance measures from a defined dataset rather than manually reconciling spreadsheets.

Learning Points

The case demonstrates that successful computing projects combine technology with process redesign, data governance, user training, and control design. It also shows why spreadsheets can be useful analytical tools but risky as uncontrolled transaction systems or systems of record.

10. Security, Ethics, and Governance

Business computing creates responsibilities because systems process personal, financial, and commercially sensitive information. Core security objectives are commonly described as:

• confidentiality: only authorised people or systems can access information;
• integrity: information remains accurate, complete, and protected from unauthorised alteration;
• availability: authorised users can access systems when required.

Controls include authentication, multi-factor authentication, least-privilege access, encryption, secure configuration, patch management, logging, monitoring, backup, recovery testing, and employee awareness. Controls should be proportional to risk and tested regularly.

Governance establishes who makes decisions, who is accountable, and how compliance is demonstrated. Important governance practices include data classification, retention schedules, change approval, segregation of duties, vendor assessment, incident response, business continuity planning, and periodic audits.

In financial services, failures may cause financial loss, regulatory penalties, reputational damage, or harm to customers. Organisations must comply with applicable data-protection, financial-services, records-management, and cybersecurity requirements in their jurisdiction. Specific obligations vary by country, so professionals must consult current laws, regulations, and supervisory guidance rather than relying on general descriptions.

Ethical issues include privacy, surveillance, accessibility, bias, explainability, and the responsible use of automated decisions. Artificial intelligence can support fraud detection, customer service, document classification, and risk analysis, but it may reproduce biased historical patterns, expose confidential data, or generate inaccurate results. Human oversight, documented model purpose, quality testing, monitoring, and clear escalation procedures are essential.

11. Contemporary Developments and Best Practices

Business computing is increasingly shaped by mobile platforms, cloud services, application programming interfaces, automation, data analytics, artificial intelligence, and the Internet of Things. These developments can improve speed and personalisation but also increase interdependence and attack surfaces.

Good practice includes:

• define business requirements before selecting technology;
• maintain clear ownership of systems and data;
• use standard data definitions and validation rules;
• design security and privacy into systems from the beginning;
• separate development, testing, and production environments;
• document interfaces, assumptions, and operational procedures;
• monitor performance, quality, security, and user outcomes;
• test backups, disaster recovery, and continuity arrangements;
• review automated decisions for accuracy and fairness;
• train users and manage organisational change;
• evaluate total cost, vendor dependence, sustainability, and exit options.

A business graduate does not need to become a hardware engineer or software developer to use computing effectively. However, graduates should be able to ask precise questions: What data is captured? Who owns it? How is it validated? What processing rules apply? Where is it stored? Who can access it? How is performance measured? What happens when the system fails? These questions connect technical design to business accountability.

Chapter Summary

Computing is an organisational capability involving hardware, software, data, people, procedures, and communication networks. The input–process–output–storage model explains how systems capture data, transform it using instructions and rules, present results, and retain records. Hardware includes the CPU, memory, storage, input devices, output devices, and communication interfaces. Software includes operating systems, utilities, applications, algorithms, and programs.

Computers represent information digitally, while file formats determine how data is structured, exchanged, displayed, and preserved. Computing architectures range from stand-alone and client–server systems to multi-tier, cloud, distributed, and edge arrangements. System performance must be considered through response time, throughput, capacity, availability, reliability, and scalability rather than through processor speed alone.

Information systems support transaction processing, reporting, analysis, risk management, customer service, accounting, and regulatory work in banking, finance, and insurance. Effective systems require process design, data governance, security, privacy, ethical oversight, continuity planning, and user adoption. Contemporary technologies, including cloud computing and artificial intelligence, create valuable opportunities but also introduce risks that must be actively governed.

Key Terms

Hardware: The physical components of a computing system.

Software: Instructions and associated data that direct hardware.

Data: Recorded facts, symbols, or observations that may be processed.

Information: Processed or interpreted data with meaning and value.

Information system: People, processes, data, hardware, software, and networks organised to produce and use information.

CPU: The central processing unit that executes program instructions.

RAM: Volatile primary memory used for active programs and data.

Secondary storage: Non-volatile storage used to retain data and programs.

Operating system: System software that manages hardware, files, processes, and users.

Algorithm: A finite, ordered procedure for solving a problem or performing a task.

File format: The defined structure and encoding used to store data in a file.

Architecture: The arrangement and interaction of computing components.

Client–server: An architecture in which clients request services from servers.

Cloud computing: Network-accessible provision of computing resources or software services.

Throughput: The quantity of work completed per unit of time.

Availability: The proportion of a defined period during which a service is operational.

Scalability: The ability of a system to handle increased workload.

Redundancy: Additional components or paths that reduce dependence on one component.

Data governance: Policies, roles, standards, and controls for managing data.

Artificial intelligence: Computational methods that perform tasks associated with capabilities such as prediction, classification, or language processing.

Review Questions

5 Short Answer Questions

1. What is the difference between data and information?
2. State the four elements of the input–process–output–storage model.
3. What is the primary function of RAM?
4. Distinguish system software from application software.
5. Define system availability.

5 Long Answer Questions

1. Explain the main components of a CPU and discuss why clock frequency alone is not a complete measure of performance.
2. Compare CSV, XLSX, PDF, JSON, and XML formats, identifying an appropriate business use for each.
3. Explain the differences between two-tier and three-tier architectures.
4. Discuss how information systems support banking, finance, and insurance organisations.
5. Explain the confidentiality, integrity, and availability objectives and describe controls that support them.

3 Analytical / Application Questions

1. A bank’s customer portal responds slowly during salary-payment days. Develop a structured approach to identify whether the bottleneck is in processing, memory, storage, database services, or the network.
2. An insurer proposes using an automated model to reject low-value claims. Analyse the data, governance, ethical, security, and human-review issues that should be addressed before deployment.
3. A finance department stores its only copy of a reconciliation spreadsheet on an employee’s laptop. Evaluate the risks and design a more reliable storage, access, backup, and file-governance arrangement.

Multiple Choice Questions with Answers

Question 1

Which statement best distinguishes information from data?

A. Information is always stored on paper

B. Information is data that has been processed or interpreted to create meaning

C. Information consists only of numbers

D. Information cannot be transmitted electronically

Correct Answer: B. Information is data that has been processed or interpreted to create meaning

Question 2

Which CPU component performs arithmetic calculations and logical comparisons?

A. Arithmetic and logic unit

B. Control unit

C. Register

D. Power supply

Correct Answer: A. Arithmetic and logic unit

Question 3

Which type of memory normally loses its contents when power is removed?

A. Solid-state storage

B. Read-only memory

C. Random-access memory

D. Optical storage

Correct Answer: C. Random-access memory

Question 4

Which file format is generally most appropriate for exchanging simple tabular data without preserving spreadsheet formulas and formatting?

A. CSV

B. PDF

C. JPEG

D. MP3

Correct Answer: A. CSV

Question 5

In a three-tier architecture, which layer normally applies business rules?

A. Presentation layer

B. Application or business-logic layer

C. Physical keyboard layer

D. Display layer

Correct Answer: B. Application or business-logic layer

Question 6

A service operates for 720 hours and is unavailable for 3 hours in the defined measurement period. What is its availability, approximately?

A. 96.00%

B. 99.00%

C. 99.585%

D. 100.00%

Correct Answer: C. 99.585%

Question 7

Which statement about cloud computing is most accurate?

A. It eliminates all security and continuity risks

B. It provides network-accessible computing resources or software services

C. It requires every organisation to own physical servers

D. It can only provide storage, not applications

Correct Answer: B. It provides network-accessible computing resources or software services

Question 8

Which security objective concerns preventing unauthorised alteration of data?

A. Confidentiality

B. Integrity

C. Availability

D. Portability

Correct Answer: B. Integrity

Question 9

Why is a backup not the same as redundancy?

A. A backup cannot contain data

B. Redundancy always reduces storage capacity to zero

C. A backup supports recovery, while redundancy may allow continued operation after a component failure

D. Redundancy applies only to paper records

Correct Answer: C. A backup supports recovery, while redundancy may allow continued operation after a component failure

Question 10

Which practice is most appropriate when introducing an automated claims-decision model?

A. Remove all human review immediately

B. Use undocumented data and rules to preserve flexibility

C. Monitor accuracy and fairness, document the model, and provide appropriate human oversight

D. Allow the model to change its own objectives without governance

Correct Answer: C. Monitor accuracy and fairness, document the model, and provide appropriate human oversight