Loading content
Computer hardware comprises the physical components of computing systems—processors, memory, storage, and peripherals. It defines constraints and capabilities that shape system architecture, performance, and energy use. Understanding hardware trade-offs is essential for design, deployment, and operational decisions across engineering and product teams.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What you need to understand to reason about a domain.
Computer hardware refers to the physical parts of a computer system. It sets the limits and options for processing power, energy use, interfaces, and form factor.
The term groups the physical parts of a computing system because software only runs on available electronics, memory, interfaces, and power delivery. The idea spans mechanical and electromechanical calculators, stored-program computers, and integrated circuits; hardware became the base layer that shapes architecture, thermal behavior, performance, and cost.
Think of a computer system as a division of labor: processors compute, RAM holds short-term working data, mass storage preserves it, I/O components connect the system to its surroundings, and power supply plus cooling keep it running. These parts work together through the motherboard and interfaces; software controls them, but clock speed, energy, and temperature set the physical limits.
The compute unit executes instructions and accounts for much of the system's speed and parallelism.
RAM keeps data and programs only for as long as they are needed during active work.
Persistent storage keeps operating systems, applications, and data available even without power.
Ports and input/output components connect the system to people, networks, and peripherals.
Power budget, heat dissipation, and chassis shape constrain how stable and compact the hardware can be.
Computer hardware matters in procurement, architecture decisions, upgrades, and fault analysis. It determines the level of performance, reliability, and expandability a system can reach. The main trade-offs are speed versus power draw, compactness versus cooling, and flexibility versus cost; the right hardware always depends on the intended use.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.