Bus (computing)
system that transfers data between components within a computer

In computer architecture, a bus (historically also called a data highway or databus) is a communication system that transfers data between components inside a computer or, more rarely, between computers. It encompasses both hardware (e.g., wires, optical fiber, bus slots) and software, including communication protocols. At its core, a bus is a shared physical pathway, typically composed of wires or traces on a circuit board, that allows multiple devices to communicate. Unlike networks, which route addressed packets across switches, buses use arbitration protocols to manage which device can transmit data over the shared pathway.
Buses are categorized based on their role, such as system buses (also known as internal buses, internal data buses, or memory buses) connecting the CPU and memory. Expansion buses, also called peripheral buses, extend the system to connect additional devices, including peripherals. Examples of widely used buses include PCI Express (PCIe) for high-speed internal connections and Universal Serial Bus (USB) for connecting external devices.
Modern buses utilize both parallel and serial communication, employing advanced encoding methods to maximize speed and efficiency. Features such as direct memory access (DMA) further enhance performance by allowing data transfers directly between devices and memory without requiring CPU intervention.
Address bus
An address bus is a bus that is used to specify a physical address.
“Bus (computing)” enters the record as system that transfers data between components within a computer. Crown Archives preserves that source wording while asking what computing, system and transfers can confirm, complicate or overturn.
Why this record matters
“Bus (computing)” is worth following because a concise public description often conceals a longer documentary argument. Here, computing, system and transfers provides the most credible route into that argument.
Named sources, stable identifiers and responsible institutions provide the strongest route from overview to verifiable evidence. The source revision retrieved here is dated Sep 10, 2026. The linked authority identifier is Q178048. The Library of Congress control number is sh85084805. 1 of 1 selected statements include explicit references; 1 carry qualifiers and 0 use preferred rank.
Overview language is designed for orientation and should not be treated as a substitute for the evidence cited beneath it. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Bus (computing)”, its source revision and the description used here.
- Expand the search: follow Bus (computing) primary sources, Bus (computing) archive and computing research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Bus (computing)”?
- What terminology or title could unlock a more precise catalogue search?
- Which institution is responsible for the underlying evidence?
Search terms from this dossier
This entry incorporates text from “Bus (computing)” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.