Software and Operating Systems

Introduction

A computer is useful not merely because it contains a processor, memory, storage, and input/output devices, but because software directs those physical resources toward meaningful tasks. Software enables an organisation to prepare budgets, manage customers, communicate with suppliers, analyse data, and protect information. For a business student, understanding software is therefore not only a technical matter. It supports informed decisions about productivity, cost, risk, compliance, procurement, and digital transformation.

This chapter distinguishes major categories of software and explains how operating systems coordinate hardware and software. It also develops practical skills for managing files, users, processes, and devices, and for diagnosing common problems safely.

Learning Objectives

After studying this chapter, you should be able to:

1. Distinguish system, application, utility, proprietary, and open-source software.
2. Explain the principal functions and components of an operating system.
3. Organise, secure, and manage files and folders.
4. Explain user accounts, permissions, processes, and device management.
5. Apply a systematic approach to basic operating-system troubleshooting.
6. Evaluate software choices using business, technical, ethical, and governance criteria.

1. Understanding Software

Software is a set of instructions, data, and associated documentation that enables a computer system to perform operations. Unlike hardware, software has no physical form, although it is stored on physical media and represented electronically in memory. Software may be installed locally, delivered through a network, embedded in a device, or accessed as a cloud service.

A useful distinction is between source code and executable code. Source code is human-readable program text written in a programming language. A compiler or interpreter translates source code into instructions that a computer can execute. Documentation, configuration files, libraries, and data may also be essential parts of a functioning software product.

Software should be classified using more than one dimension. For example, a spreadsheet program is application software, but it may also be proprietary or open source, locally installed or cloud-based, and free of charge or paid. “Free” can mean no monetary price, whereas “free software” often refers to users’ freedoms to study, modify, and redistribute the software. These ideas should not be confused.

1.1 System software

System software manages computer resources and provides a platform on which application software operates. Its most important example is the operating system. Other examples include device drivers, firmware, language translators, and system-level networking components.

System software performs functions close to the hardware. A printer driver, for instance, translates general print instructions into commands understood by a particular printer. Firmware is software stored in non-volatile memory that controls a device’s basic functions, such as starting a computer or managing a network device.

System software is essential because application developers should not need to write separate instructions for every model of processor, disk, keyboard, or display. Instead, applications use standard interfaces supplied by the operating system and related system components.

1.2 Application software

Application software helps users perform specific personal, professional, or organisational tasks. Examples include word processors, accounting systems, customer relationship management systems, web browsers, presentation tools, payroll programs, and enterprise resource planning systems.

Applications can be general-purpose or specialised. A spreadsheet is general-purpose because it supports many calculations and reporting tasks. A bank’s loan-origination system is specialised because it implements a defined business process. Applications may be desktop programs, mobile apps, browser-based services, or software accessed through an application programming interface (API).

Application software depends on system software. When a user saves a document, the application requests file services from the operating system, which in turn communicates with storage hardware through drivers and controllers.

1.3 Utility software

Utility software performs maintenance, protection, monitoring, configuration, or optimisation tasks. Utilities may be supplied with an operating system or obtained separately. Examples include:

• backup and restore tools;
• antivirus and endpoint-protection software;
• disk-management and storage-cleanup tools;
• file-compression programs;
• system-monitoring tools;
• encryption utilities; and
• diagnostic and recovery tools.

The boundary between system and utility software is not absolute. A disk-checking utility may be an operating-system component on one platform and an independent product on another. The important distinction is functional: utilities support the operation, security, reliability, or maintenance of a computing environment rather than directly carrying out the user’s primary business task.

1.4 Proprietary software

Proprietary software is controlled by an owner, usually a company or individual, who determines the terms under which it may be used, copied, modified, or distributed. The source code is normally unavailable to users, although the precise legal arrangements vary.

A proprietary licence may restrict the number of users, devices, locations, or installations. It may require a subscription, impose terms on data processing, or prohibit reverse engineering. Proprietary software can offer professional support, integrated services, predictable product road maps, and strong usability. However, organisations may face vendor lock-in, recurring costs, dependence on a supplier, limited customisation, and difficulties migrating data.

“Proprietary” does not necessarily mean expensive, insecure, or inferior. It describes control and licensing, not quality.

1.5 Open-source software

Open-source software makes source code available under a licence that permits specified forms of inspection, use, modification, and redistribution. The licence is central: simply publishing code online does not automatically make it open source.

Open-source licences differ. Some require modified versions to remain available under similar terms; others permit incorporation into proprietary products subject to conditions. Organisations must therefore review licence obligations, copyright notices, attribution requirements, and distribution rules.

Potential advantages include transparency, adaptability, community review, reduced licence fees, and avoidance of dependence on one supplier. Potential challenges include uneven support, fragmented development, uncertain responsibility, compatibility issues, and the need for internal expertise. Open-source software is not automatically free of cost: implementation, training, security review, integration, support, and maintenance still require resources.

1.6 Comparing software categories

These categories can overlap. Linux is system software and is generally open source. A commercial accounting package is application software and may be proprietary. A backup program can be utility software and may be either proprietary or open source.

2. Operating Systems as Resource Managers

An operating system (OS) is system software that manages hardware resources, provides common services to programs, and supplies an interface through which users and applications interact with a computer. Examples include Windows, macOS, Linux distributions, Android, and iOS.

The OS can be understood as an intermediary between users, applications, and hardware. It hides unnecessary hardware complexity while enforcing rules about access, allocation, and protection. It also creates abstractions such as files, folders, processes, virtual memory, and devices.

2.1 Core operating-system functions

Process and processor management. A process is a program in execution, together with its current state and allocated resources. The OS creates, schedules, pauses, resumes, and terminates processes. Because many processes compete for processor time, the OS rapidly switches the processor among them. This creates the appearance of simultaneous activity, although the exact behaviour depends on the number of processor cores and the scheduling design.

Memory management. The OS allocates memory to processes, prevents unauthorised access to another process’s memory, and reclaims memory when a process ends. Virtual memory allows the OS to use storage to extend the apparent memory available to programs, but excessive reliance on storage is much slower than using physical RAM.

File and storage management. The OS organises persistent data into files and directories, records file properties, controls access, and communicates with storage devices. It also manages available space and supports operations such as creation, copying, renaming, deletion, and recovery.

Device management. The OS coordinates input and output devices such as keyboards, displays, printers, cameras, disks, and network adapters. Device drivers provide a standard communication layer between the OS and specific hardware.

Security and access control. The OS authenticates users, authorises actions, isolates processes, records events, and supports encryption and security updates. Security is not a single feature; it is a set of controls that reduce unauthorised access and operational risk.

User interface. A graphical user interface (GUI) presents windows, icons, menus, and pointers. A command-line interface (CLI) accepts typed commands. GUIs are often accessible to occasional users, while CLIs can provide precision, automation, and efficient administration. Both ultimately invoke operating-system services.

Networking. Modern operating systems manage network interfaces, addressing, wireless connections, firewalls, name resolution, and communication protocols. These functions allow applications to use shared systems and online services.

3. Files, Folders, and Storage

A file is a named collection of data stored as a unit. A folder or directory is a container used to organise files and other folders. A file name commonly includes an extension such as .docx, .xlsx, .pdf, or .jpg, which helps the OS and applications identify a likely file type. An extension is an indicator, not proof of content or safety; malicious software can disguise itself using misleading names.

A path identifies a file’s location. An absolute path begins from the storage system’s root or drive, whereas a relative path is interpreted from a current location. A well-designed business filing structure uses meaningful names, consistent dates, controlled versions, and limited duplication.

Important file operations include:

• Create: produce a new file or folder.
• Open: load a file into an appropriate application.
• Copy: create a second instance while retaining the original.
• Move: change the location of a file, usually without creating a second instance.
• Rename: change the file’s name without necessarily changing its contents.
• Delete: remove the directory reference; recovery may or may not be possible.
• Compress: represent data using less storage, often for transfer or archiving.
• Synchronise: maintain corresponding versions across locations or devices.

Deleting a file is not equivalent to securely destroying all information. Recovery may be possible until the storage space is reused, and cloud services may retain versions or backups. Sensitive information should be disposed of according to organisational policy and applicable data-protection requirements.

3.1 File permissions and sharing

Permissions determine who may read, modify, execute, or delete a file. A common conceptual model distinguishes the file owner, a group, and other users. Modern systems may also use access-control lists that specify detailed permissions for individuals and groups.

The principle of least privilege states that a user or process should receive only the access necessary to perform an authorised task. This reduces the consequences of mistakes, malware, and compromised accounts. Shared folders should be designed around roles rather than informal universal access.

3.2 Backup and version control

A backup is a separate copy maintained so data can be restored after loss, corruption, theft, or system failure. Effective practice includes multiple copies, different storage media or locations, and at least one copy protected from ordinary alteration. Backups must be tested: a backup that cannot be restored is not a dependable control.

Versioning records earlier states of a file. It can protect against accidental overwriting and ransomware, but it does not replace independent backups if an attacker can alter every available version.

4. Users, Accounts, and Permissions

An operating-system account represents a user, service, or administrative identity. Authentication verifies identity, commonly through a password, security key, biometric factor, or combination of factors. Authorisation determines what an authenticated identity is allowed to do. These are different processes: logging in successfully does not imply permission to access every resource.

Common account types include:

• Standard user: performs ordinary work with limited system privileges.
• Administrator or root user: can change system-wide settings, install software, and manage other accounts.
• Guest account: provides restricted temporary access where supported.
• Service account: allows an automated service to perform defined operations.

Using an administrator account for routine work increases risk because malicious code launched during that session may inherit elevated privileges. Organisations should use separate administrative credentials, strong authentication, timely account removal, and regular reviews of group membership.

A good access-management process follows the employee life cycle: create an account when authorised, change permissions when responsibilities change, and disable access promptly when employment or engagement ends. Shared accounts reduce accountability and should generally be avoided.

5. Processes and Performance

A program is a stored set of instructions; a process is an active execution of a program. A process has a state, memory allocation, open files, and relationships with other processes. A process may create child processes, wait for input, run in the background, or terminate normally or abnormally.

The OS scheduler allocates processor time among ready processes. A process may be:

• Running: currently using a processor core.
• Ready: able to run but waiting for processor time.
• Blocked or waiting: unable to continue until an event occurs, such as disk input or user input.
• Terminated: no longer executing.

A task manager or system monitor displays processor utilisation, memory consumption, storage activity, network use, and active processes. These indicators must be interpreted carefully. High processor use may reflect legitimate analysis, malware, or an inefficient application. High memory use may be normal caching, whereas sustained swapping to storage suggests memory pressure.

A deadlock occurs when processes wait indefinitely for resources held by one another. Users commonly encounter a simpler problem: an application becomes unresponsive because it is waiting for a device, network response, or internal operation. Terminating a process may restore responsiveness but can cause unsaved data loss. The safer sequence is to wait briefly, check whether the system is still active, save if possible, and end only the unresponsive task when necessary.

6. Device Management

Devices communicate with the OS through drivers and system interfaces. When a device is connected, the OS may detect it, load a driver, assign resources, and make it available to applications. Problems can arise from incompatible drivers, loose connections, insufficient power, incorrect settings, damaged hardware, or permission restrictions.

Typical device-management tasks include:

1. Connecting or pairing the device according to manufacturer instructions.
2. Confirming that the OS recognises it.
3. Selecting it as the default input or output device where required.
4. Installing updates from trusted sources.
5. Testing the device in a simple application.
6. Removing or disabling it safely when appropriate.

Printers illustrate the distinction between hardware and software particularly well. A printer may be physically functional but unavailable because of a queue error, incorrect default selection, network failure, depleted supplies, or a driver problem.

7. Basic Operating-System Troubleshooting

Troubleshooting is a structured process for identifying and correcting a fault. Guessing and changing many settings at once makes the cause harder to identify. A disciplined approach is:

Step 1: Define the symptom

Record what happened, when it began, which user and device are affected, and whether an error message appears. “The system is slow” is less useful than “The accounting application has taken more than two minutes to open since yesterday’s update.”

Step 2: Establish scope

Determine whether the problem affects one file, one application, one user, one device, many users, or the entire network. Scope helps distinguish local faults from shared-service failures.

Step 3: Check simple causes first

Confirm power, cables, network connection, storage capacity, login details, mute settings, and whether the correct device or application is selected. Restarting may clear a temporary process or driver state, but it should not replace investigation when failures recur.

Step 4: Consult evidence

Read error messages, system logs, monitoring information, recent-change records, and vendor documentation. Note the time and sequence of events.

Step 5: Change one variable at a time

Test a controlled remedy, such as reconnecting a device, closing one process, reverting a recent setting, or applying an approved update. Record the result.

Step 6: Protect data and escalate appropriately

Back up important work before risky repairs. Do not disable security controls casually or install unknown diagnostic tools. Escalate when the issue involves suspected malware, data loss, hardware damage, privileged access, or a business-critical service.

Common symptoms and responses

8. Selecting Software in a Business Context

Software procurement should begin with business requirements rather than brand names. A decision should consider functionality, usability, integration, security, accessibility, scalability, reliability, total cost of ownership, support, data portability, and legal compliance.

Total cost includes more than the purchase price. It may include subscriptions, implementation, migration, customisation, training, support, upgrades, downtime, security controls, and eventual replacement. A low initial price can be misleading if the system creates high integration or switching costs.

A practical evaluation process is to:

1. define requirements and measurable success criteria;
2. identify legal, privacy, security, and accessibility constraints;
3. compare proprietary and open-source alternatives;
4. conduct a controlled pilot with representative users and data;
5. assess supplier support, licence terms, exit arrangements, and interoperability;
6. document risks and assign ownership; and
7. review performance after implementation.

Ethical governance matters because software decisions affect employees, customers, and communities. Organisations should consider privacy, surveillance, discriminatory outcomes, accessibility, security disclosure, software supply-chain risk, and the environmental impact of procurement and disposal. Artificial intelligence features should not be accepted merely because they are marketed as intelligent; organisations should examine data use, accuracy, explainability, human oversight, and accountability.

9. Illustrative Case: Software and Access Failure in a Retail Firm

Background

A fictional retailer, Northstar Supplies, introduces a cloud-based inventory application. Staff use office computers, handheld scanners, a shared network, and network printers. After a software update, several employees report that stock records are slow to open and one employee cannot print receiving labels.

Problem analysis

The IT coordinator first establishes scope. The inventory application is slow for several users, while email and the public website work normally. The printing issue affects one workstation only. Resource monitoring shows that the affected workstation has nearly full storage and an obsolete printer driver. The inventory service provider’s status page reports normal operation.

The coordinator also reviews recent changes. The application update occurred overnight, but the performance problem appears linked to a large synchronisation process running on several machines. Staff members are using administrator accounts and have installed unrelated utilities, creating additional security and support risks.

Approach and solution

The coordinator backs up local work, removes unnecessary temporary files using an approved utility, confirms adequate free space, and allows synchronisation to complete during a scheduled period. The printer is reselected as the default device, its queue is cleared, and an approved driver is installed. The firm then creates standard user accounts, reserves administrative access for authorised support staff, and documents a routine for checking storage, updates, and backups.

Outcome

Application response returns to an acceptable level, labels print correctly, and the company reduces the risk of unauthorised software installation. The firm also introduces a change-management rule requiring pilot testing before future updates.

Learning points

The case demonstrates that a visible symptom may have several causes. Troubleshooting requires scope assessment, evidence, controlled changes, and data protection. It also shows that operating-system administration is a business-control issue: account privileges, updates, storage, and backups affect continuity, security, and employee productivity.

10. Limitations and Contemporary Developments

Operating systems simplify computing but cannot eliminate complexity. Compatibility problems may occur between old applications and new systems. Updates can improve security while introducing temporary faults. Cloud services shift some administration to suppliers but do not remove the organisation’s responsibility for configuration, access control, data classification, and continuity planning.

Containerisation and virtual machines allow multiple isolated computing environments to share physical resources. Mobile and embedded operating systems increasingly manage sensors, location data, and application permissions. Security models are moving toward stronger isolation, hardware-backed credentials, automatic updates, and zero-trust approaches in which access is continuously evaluated rather than assumed because a device is inside a corporate network.

Open-source components are widely used inside proprietary products, making software supply-chain governance important. Organisations should maintain inventories of components, monitor vulnerabilities, apply patches according to risk, and retain recovery plans. Automation and AI-assisted administration can identify anomalies or suggest remedies, but automated changes require testing, logging, authorisation, and human oversight.

Best-Practice Checklist

• Match software classification to function and licence conditions.
• Use standard accounts for routine work and separate privileged accounts for administration.
• Apply least privilege and review permissions regularly.
• Use meaningful file names, controlled folders, and versioning.
• Maintain independent, tested backups.
• Install software and updates only from trusted, authorised sources.
• Keep operating systems, applications, drivers, and security tools maintained.
• Record symptoms and recent changes when troubleshooting.
• Change one variable at a time and protect data before risky actions.
• Evaluate total cost, interoperability, privacy, accessibility, and exit options before procurement.

Chapter Summary

Software consists of instructions and related resources that make computer systems useful. System software manages hardware and provides a platform; application software performs user and business tasks; utility software maintains, protects, monitors, and diagnoses systems. Proprietary software is controlled through an owner’s licence, whereas open-source software is distributed under licences that provide specified rights to inspect, modify, and redistribute source code. These classifications can overlap.

An operating system manages processes, memory, files, users, permissions, devices, networking, security, and interfaces. Files and folders require organised naming, access control, backup, and version management. User administration depends on the distinction between authentication and authorisation and on the principle of least privilege. Processes represent programs in execution, while task-monitoring tools help interpret resource use and unresponsive applications. Device management depends on drivers, settings, connections, and approved updates.

Effective troubleshooting is evidence-based: define the symptom, establish scope, check simple causes, consult records, change one variable at a time, protect data, and escalate serious or uncertain cases. Business software decisions should evaluate requirements, total cost of ownership, security, privacy, accessibility, integration, licensing, support, and exit risk. Sound software and operating-system practices improve productivity, resilience, governance, and employability.

Key Terms

Software: Instructions, data, and documentation that direct a computer system.

System software: Software that manages hardware and provides a platform for applications.

Application software: Software designed to perform user or business tasks.

Utility software: Software for maintenance, protection, optimisation, or diagnosis.

Operating system: System software that manages resources and provides common services and interfaces.

Proprietary software: Software controlled by an owner under specified licence conditions.

Open-source software: Software distributed under a licence providing specified rights to inspect, modify, and redistribute source code.

File: A named collection of stored data.

Folder: A directory used to organise files and other directories.

Path: An address identifying a file or folder location.

Permission: An authorised level of access to a resource.

Least privilege: Giving an identity only the access necessary for its task.

Authentication: Verification of an identity.

Authorisation: Determination of permitted actions after identity verification.

Process: A program currently executing.

Device driver: Software that enables an operating system to communicate with a particular device.

Backup: A separate copy maintained for restoration after data loss or damage.

Troubleshooting: A systematic process of identifying and correcting faults.

Total cost of ownership: The complete cost of acquiring, operating, maintaining, and replacing a system.

Vendor lock-in: Dependence on a supplier that makes migration or replacement difficult.

Review Questions

Short Answer Questions

1. What is the difference between system software and application software?
2. Why can a software product be both open source and system software?
3. Distinguish authentication from authorisation.
4. What is the purpose of a device driver?
5. State four sensible first steps in troubleshooting an operating-system problem.

Long Answer Questions

1. Explain the principal functions of an operating system and show how they support business applications.
2. Compare proprietary and open-source software, including advantages, risks, and governance considerations.
3. Discuss effective file management, including paths, permissions, backups, and versioning.
4. Explain process management and how a system monitor can assist in diagnosing poor performance.
5. Describe a structured approach to selecting and implementing software in an organisation.

Analytical / Application Questions

1. A small business is deciding between a proprietary accounting package and an open-source alternative. Develop a decision framework that considers functionality, cost, support, security, licensing, integration, and exit risk.
2. Employees report that a shared document is missing and that several users cannot access a departmental folder. Analyse possible causes and propose an investigation that protects data and accountability.
3. After an operating-system update, one computer cannot print while other computers can. Apply the troubleshooting method in this chapter and identify the evidence you would collect before escalating the problem.

Multiple Choice Questions with Answers

Question 1

Which category of software primarily manages hardware resources and provides a platform for applications?

A. System software

B. Application software

C. Utility software

D. Presentation software

Correct Answer: A. System software

Question 2

Which statement best describes proprietary software?

A. It must always be free of monetary cost.

B. Its use and modification are controlled by an owner’s licence.

C. Its source code must be publicly modifiable without conditions.

D. It can only run without an operating system.

Correct Answer: B. Its use and modification are controlled by an owner’s licence.

Question 3

What is the main purpose of the principle of least privilege?

A. To maximise the number of administrator accounts

B. To give every employee identical access

C. To limit access to what is necessary for an authorised task

D. To prevent all software updates

Correct Answer: C. To limit access to what is necessary for an authorised task

Question 4

A program that is currently executing is called a:

A. Folder

B. Process

C. Driver

D. Permission

Correct Answer: B. Process

Question 5

Which action best protects against the failure of a backup strategy?

A. Keeping only one copy on the original computer

B. Testing whether backups can actually be restored

C. Renaming every file with the same name

D. Disabling version history

Correct Answer: B. Testing whether backups can actually be restored

Question 6

What does authentication verify?

A. Whether a user is authorised to delete a file

B. The identity of a user or service

C. Whether a printer has paper

D. The amount of storage available

Correct Answer: B. The identity of a user or service

Question 7

An employee cannot print from one workstation, but other workstations print normally. Which is the most appropriate first approach?

A. Replace the organisation’s entire network

B. Delete all company files

C. Check the workstation’s printer selection, queue, connection, and driver

D. Give the employee permanent administrator rights

Correct Answer: C. Check the workstation’s printer selection, queue, connection, and driver

Question 8

Which statement about open-source software is accurate?

A. It is automatically without any implementation or support cost.

B. It has no licence obligations.

C. Its source code is available under a licence that permits specified forms of use or modification.

D. It cannot be used in commercial organisations.

Correct Answer: C. Its source code is available under a licence that permits specified forms of use or modification.

Question 9

Which troubleshooting action is most likely to preserve diagnostic clarity?

A. Change many unrelated settings simultaneously

B. Change one variable at a time and record the result

C. Ignore error messages

D. Disable all security controls immediately

Correct Answer: B. Change one variable at a time and record the result

Question 10

Which cost is part of total cost of ownership?

A. Only the initial purchase price

B. Only the number of software features

C. Implementation, training, maintenance, and eventual replacement costs

D. Only the colour of the application interface

Correct Answer: C. Implementation, training, maintenance, and eventual replacement costs