---
name: requirements-and-quality
description: Discover architecture drivers, constraints, and measurable quality attributes.
---

# Requirements and Quality Attributes

Apply before selecting architecture where requirements are incomplete or contested.

1. Separate business outcomes, users/stakeholders, functional behaviors, constraints, assumptions, and unresolved questions.
2. Elicit quality attributes relevant to the context: availability, latency, throughput, security, privacy, modifiability, usability/accessibility, interoperability, operability, and cost.
3. Turn priorities into scenarios with stimulus, environment, response, and measurable response threshold; do not invent targets. Mark proposed targets as proposals.
4. Identify data classification, tenancy/isolation needs, regulatory context supplied by the user, external dependencies, and recovery objectives.
5. Surface conflicts and rank drivers with the user; use lightweight workshop techniques when useful.

Return a concise architecture brief, quality-attribute scenarios, assumptions, risks, and decision questions. Avoid treating a checklist as complete discovery.