For every topic in this foundations section, ask the same four questions: what problem does this concept solve, what are its main components, how is information represented or moved through it, and what does one real use or risk look like? Where security, privacy, or ethics comes up, keep the technical capability (what a system can do) separate from the legal or ethical responsibility created by how it is used.
A. What Computers Are, and How They Developed
A computer is a programmable electronic system that accepts data, processes it according to a set of instructions, stores it, and produces output. Information technology is the wider field: using computing and communications together to create, process, store, and exchange information. Computing developed from mechanical calculation through electronic vacuum-tube machines, transistors, integrated circuits, microprocessors, and today’s networked, multi-core systems — the underlying story across this whole progression is a consistent shift toward smaller, faster, cheaper, and more interconnected systems. The two conceptual turning points worth understanding, rather than just naming, are the stored-program concept (a computer that stores its own instructions in memory alongside data, rather than being physically rewired for each new task) and the microprocessor (putting a complete processor onto a single chip, which made computing dramatically cheaper and smaller). Example: a simple calculator follows a fixed, limited set of operations, while a general-purpose computer can load entirely different programs for writing, analysis, communication, or simulation — the stored-program concept is precisely what makes this generality possible.
B. Hardware, Software, and System Components
Hardware is the physical equipment; software is the set of instructions, and related data, that tell the hardware what to do. A basic computer system includes a processor (executes instructions), memory (holds data and instructions currently in use), storage (holds data persistently), input/output devices, and communication interfaces. System software, most importantly the operating system, manages the underlying platform itself; application software performs the tasks a user actually wants done. Example: a keyboard is hardware, a word processor is application software, and the operating system coordinates both of these together with the processor, memory, and files on disk. A useful mental model for the whole system: input flows into the CPU and memory, which produce output, with storage and communication links feeding into and out of that same central loop.
C. I/O, Storage, Languages, and Number Systems
Input devices capture data (keyboard, mouse, sensors, scanners); output devices present results (displays, printers, actuators); storage keeps data for later use, and comes in magnetic, optical, or solid-state forms. Example: an SSD (solid-state storage) retains files even after power is removed, while RAM is normally volatile working memory that loses its contents when power is cut — this persistence-versus-volatility distinction is why a computer needs both. Programming languages let humans describe computations in a form that can eventually be translated or executed, ranging from low-level machine and assembly languages (very close to the hardware) to high-level languages (closer to human reasoning, and translated by a compiler or interpreter before or during execution).
Computers represent all information — numbers, characters, images, and even instructions themselves — using binary states, i.e. patterns of bits (each either 0 or 1). Binary, decimal, octal, and hexadecimal are different positional number systems for representing the same underlying quantities, and converting between them is a core mechanical skill. Example: binary 1010 equals decimal 10, because reading the bits from left to right against place values of 8, 4, 2, 1 gives (1×8) + (0×4) + (1×2) + (0×1) = 10. Hexadecimal is used heavily in computing specifically because each hex digit maps cleanly onto exactly four binary bits, making it a compact, human-readable shorthand for binary patterns. A bit is the smallest unit (0 or 1); a byte is a group of 8 bits, and character encodings (such as ASCII) map human-readable symbols onto specific numeric bit patterns so that text can be stored and processed like any other data.
D. User Interfaces and Common Software Issues
A user interface is the layer through which a person interacts with software — command-line, graphical, touch, voice, or another specialized form. A good interface aims for usability (can people actually accomplish their task), consistency (similar actions behave similarly throughout), accessibility (usable by people with different abilities), and clear feedback (the system tells the user what just happened). Example: a form can be technically correct in every functional sense and still fail its users if its labels are unclear or its error messages don’t explain what went wrong — “the software works” and “the software is usable and dependable” are genuinely different standards, and exam answers should distinguish them explicitly. Common software issues beyond pure usability include bugs, compatibility across platforms, security vulnerabilities, performance, long-term maintainability, licensing terms, and the ongoing need for updates.
E. Productivity Tools and Internet Basics
Common productivity tools create documents, calculations, presentations, and communications, while internet tools help users find, exchange, and access information. Core competencies worth understanding functionally: formatting and file management in word processors, formulas and cell referencing in spreadsheets, slide structure in presentation software, and email, browsers, search engines, and messaging as internet-facing tools. Example: typing a web address directly into a browser is not the same action as searching the web — the browser is a client application that requests and displays web resources, while a search engine is a separate online information-retrieval service that indexes content and helps locate it; conflating the two is a common conceptual error. Safe habits (recognizing suspicious emails, verifying links before clicking, keeping backups, and using clear file-version naming) matter more for this topic than memorizing brand-specific menu locations.
F. Computing, Society, Security, and Ethics
Computing creates real social benefits, but it also creates risks to confidentiality, integrity, availability, privacy, and fairness — the well-known CIA triad (confidentiality, integrity, availability) is the standard framework for thinking about information security systematically. Malware is a general term for malicious software; a virus is one specific type that attaches to or infects files or programs and replicates itself under suitable conditions — not every cyber incident is accurately called “a virus,” and this precision matters in exam answers. Computer crime can include unauthorized access, fraud, and deliberate disruption of systems. Plagiarism — presenting another person’s work as one’s own — and intellectual-property law — which protects certain original creations under legal rules — are related but distinct concerns from security. Example: reusing a paragraph without proper attribution is a plagiarism problem, while stealing someone’s account credentials is a security problem and potentially a criminal one — these are genuinely different categories of wrongdoing even though both involve computers. Other foundational security concepts worth knowing: authentication (verifying who someone is), backups (protecting against data loss), and least privilege (giving each user or process only the access it actually needs, to limit potential damage from mistakes or compromise).
G. Computing Disciplines Compared
The field of “computing” actually splits into several related but distinct disciplines. Computer science studies computation and algorithms themselves — the theoretical and mathematical core of the field. Software engineering focuses on the systematic, disciplined development of reliable, maintainable software at scale. Information technology emphasizes the deployment and operation of computing infrastructure that others rely on. Information systems connects technology with organizational processes and business needs. Computer engineering bridges hardware design and computing, sitting between electrical engineering and computer science. Bioinformatics applies computational methods specifically to biological data. Example: designing a new sorting algorithm sits closer to computer science; managing an organization’s servers and user accounts sits closer to information technology; designing a new processor board sits squarely in computer engineering — the same broad word “computing” covers genuinely different day-to-day work depending on which of these disciplines is meant.
Computing Foundations key takeaways: every foundational topic reduces to what problem it solves, what its components are, how information moves through it, and one concrete risk or use case. The stored-program concept and the microprocessor are the two developments that most explain computing’s shift toward general-purpose, small, and interconnected systems. Persistence (storage) and volatility (RAM) solve different problems and are not interchangeable. Number-system conversions and the CIA security triad are compact, testable skills worth over-preparing relative to their apparent simplicity. Usability and functional correctness are two different standards a piece of software can meet or fail independently. The various computing disciplines share tools but differ sharply in their central object of study and typical day-to-day work.