Part 2 of 9 · 1 min read
Qualities, not just features
The difference between what a system does and the qualities that shape its design.
Think of two cars with the same features: four wheels, a steering wheel, five seats. One is a family car, the other a racing car. They differ in qualities: speed, comfort, cost, safety, fuel use. The features are the same, but the designs are very different.
Software has the same split. A feature is what the system does. A quality is how the system behaves while doing it.
Architecture characteristic
An architecture characteristic, also called a quality or an "-ility", is a property of a system that is not a feature but strongly shapes its design, such as availability, scalability or security.
Example: a ticket shop and a company intranet both let users view pages. The ticket shop needs to survive huge bursts of buyers. The intranet does not. The characteristic "elasticity" separates the two designs.
Three tests tell whether something is an architecture characteristic. It is not about the business feature itself. It affects the structure of the design. And it matters for the success of the system.
Qualities usually cannot all be maximised at once. Strong security usually costs some speed. High speed usually costs some money. The best design is the one that gets the qualities that matter most, and accepts less of the others.
Check yourself:
- Name one feature and one quality of an online bank.
- Why can a designer not give every quality the highest level?