computer organization

If architecture is the menu a restaurant promises (these dishes, this price, this is what shrimp scampi means), organisation is the kitchen: how many stoves, where the fridge sits, who chops and who plates, how orders flow from the till to the cooks. Two restaurants can offer the identical menu and yet run wildly different kitchens. Computer organization is the kitchen of a computer — the actual arrangement of components that carries out the architectural contract.

Concretely, organisation covers the building blocks you can point to: the control unit and the datapath inside the processor, the registers, the arithmetic-logic unit that does the math, the memory system and its caches, and the buses that connect everything. It answers how questions: how an add actually moves data through wires and adders, how memory is laid out, how fast each piece runs. The architecture said add two numbers; organisation decides whether that addition uses a slow simple adder or a fast clever one, and how it is wired into the rest of the machine.

The line between organisation and microarchitecture is fuzzy and the terms are often used interchangeably; many authors treat organisation as the broader, more traditional word and microarchitecture as the modern, processor-focused one. What matters for a beginner is the split from architecture: the same architectural promise can be kept by many different organisations, trading cost, speed, and power. That freedom is the whole reason a chip can get faster every few years while old software keeps running unchanged.