Categorization, Ambiguities, and Trade-offs of Architecture Characteristics

Key Insight

Architecture characteristics span a broad spectrum, from low-level code attributes like modularity to sophisticated operational concerns like scalability. Despite past attempts, no universal standard exists, leading organizations to develop their own interpretations, and new concepts constantly emerge with the evolving software ecosystem; for example, a unique historical event might lead to a bespoke characteristic like 'Italy-ility,' combining availability, recoverability, and resilience. These characteristics are broadly categorized into Operational, Structural, and Cross-Cutting types. Operational characteristics include capabilities such as availability (e.g., 24/7 uptime), performance (stress testing, response times, capacity), recoverability (system online quickly after disaster), reliability/safety, robustness, and scalability (handling increased users or requests).

Structural architecture characteristics relate to code quality and system organization. Examples include configurability (ease of end-user configuration via interfaces), extensibility (plugging in new functionality), installability (ease of system setup on all platforms), leverageability/reuse (common components across products), maintainability (ease of changes and enhancements), portability (running on multiple platforms, e.g., Oracle and SAP DB), supportability (logging and facilities for debugging), and upgradeability (easy and quick upgrades of the application). Cross-cutting characteristics encompass concerns like accessibility (for users with disabilities), archivability (data archiving or deletion after periods, e.g., 3 months for customer accounts), authentication (user identity verification), authorization (function access control), legal compliance (Sarbanes Oxley, GDPR), privacy (hiding transactions), and security (data encryption, network communication encryption, remote user authentication).

Defining and managing architecture characteristics involves significant ambiguity and the necessity of trade-offs. Many terms are imprecise or overlap (e.g., interoperability vs. compatibility, availability vs. reliability), and a complete, universal list remains elusive, even with the International Organization for Standards (ISO) providing partial categorizations like performance efficiency, usability, security, and maintainability. A critical challenge is that supporting each characteristic adds complexity and often negatively impacts others; for instance, enhancing security typically degrades performance due to additional encryption. Therefore, architects must aim for the 'least worst architecture' rather than trying to maximize every characteristic, emphasizing iterative design to adapt more easily to evolving needs rather than striving for initial perfection.