Article · English · 2021
What's in a Name?
A series of short essays pinning down the words architects overload every day: architecture, quality, evaluation, transparency and consistency.
Software architects reuse a handful of words so often that their meaning quietly erodes. In What’s in a Name? Gernot Starke takes one loaded term at a time and asks what it should actually mean, why the vague version causes trouble, and how a sharper definition helps teams communicate.
The series
- Architecture — what “software architecture” really denotes, grounded in the IEEE 1471 definition.
- Quality — why “quality” means something different to every stakeholder, and how to make it concrete.
- Evaluate — the difference between evaluating business impact and merely analysing problems.
- Transparency — how frameworks that hide complexity make systems less transparent, not more.
- Consistency — the many senses of “consistency”, from UIs to databases, and why conceptual integrity matters.
Published on INNOQ · By Gernot Starke · Parts 5 · Published 2015–2021