Core Idea
The architecture characteristics extraction process is a systematic approach for discovering both explicit and implicit architectural requirements by analyzing domain concerns, stakeholder requirements, and business context to ensure the architecture addresses actual needs rather than assumed ones.
The Extraction Process
Architecture characteristics extraction is the disciplined practice of identifying which non-functional requirements (the “-ilities”) matter most. It prevents two common failure modes: designing for characteristics that don’t align with actual business priorities, and missing critical implicit requirements that stakeholders assume are obvious.
The process operates on two parallel tracks:
Explicit characteristics emerge from direct stakeholder statements and documented requirements:
- “The system must handle 10,000 concurrent users” → scalability
- “Downtime costs $50,000 per minute” → high availability
- These require careful listening and translation from business language to architectural vocabulary
Implicit characteristics derive from domain knowledge and business context that stakeholders may never articulate:
- Healthcare systems: security, reliability, and auditability due to regulatory constraints and patient safety
- E-commerce platforms: performance, availability, and data integrity because revenue depends on transaction completion
- Financial systems: security, compliance, and disaster recovery as table stakes for operating in the industry
The extraction process combines requirements document analysis, stakeholder interviews, and domain expertise. Architects must ask probing questions:
- “What does this business do?”
- “What are the consequences of system failure?”
- “What regulatory constraints apply?”
- “How does the business make money, and how does the system support that?”
These questions reveal characteristics that weren’t explicitly stated but are nonetheless critical to success.
Why This Matters
Incomplete or misidentified characteristics lead to architectures that fail to meet actual business needs:
- A system optimized for extreme scalability when the business needs rapid feature delivery wastes engineering effort on the wrong problem
- Missing an implicit security requirement in a healthcare system can result in regulatory violations and patient harm
The extraction process ensures architectural decisions align with real business drivers rather than assumptions or technical preferences.
Related Concepts
- Explicit-Architecture-Characteristics — Requirements directly stated by stakeholders
- Implicit-Architecture-Characteristics — Domain-derived requirements not explicitly stated
- Architecture-Characteristics-Categories — Operational, structural, and cross-cutting categories
- Trade-Offs-and-Least-Worst-Architecture — How extracted characteristics guide trade-off decisions
- Architecturally-Significant-Decisions — Decisions that shape characteristic support
- Fundamentals of Software Architecture - Richards & Ford - 2020 — Source literature note
Sources
- Richards, Mark and Neal Ford (2020). Fundamentals of Software Architecture: An Engineering Approach. O’Reilly Media. ISBN: 978-1-492-04345-4.
- Chapter 5: Identifying Architecture Characteristics
- Available: https://www.oreilly.com/library/view/fundamentals-of-software/9781492043447/
Note
This content was drafted with assistance from AI tools for research, organization, and initial content generation. All final content has been reviewed, fact-checked, and edited by the author to ensure accuracy and alignment with the author’s intentions and perspective.