Software Components and Characteristics

Software is not just code. A complete software product has three components:

1. Instructions (program) — the executable code that directs the computer.
2. Data structures — the organized information the program processes (files, databases, in-memory structures).
3. Documentation — user manuals, design docs, API references, in-code comments, deployment guides.

Missing documentation is the most common failure in real projects — the code works but nobody knows how to deploy or maintain it.

Software vs Hardware — Key Characteristics

Property	Software	Hardware
Manufacturing	Engineered once, copied digitally	Manufactured physically each unit
Wear	Doesn’t wear out — deteriorates via changes	Physically wears out (friction, heat)
Failure mode	Design bugs, configuration errors	Physical failure (disk crash, circuit burn)
Replication	Zero marginal cost per copy	Cost per unit
Modification	Changeable after deployment	Requires physical replacement

Software rot (also called code decay) happens not because the code degrades, but because the environment changes — OS updates, new security requirements, different hardware — while the code accumulates patches that reduce its structural quality.

The Complexity Problem

A typical enterprise system has millions of possible execution paths. No single person understands it all. This is why modularity, abstraction, and layering are essential — they limit the amount of information any developer needs to hold in their head at once.

This inherent complexity is why software requires engineering discipline rather than just heroic individual effort.