Back to Details

032-architecture-adr-non-functional-requirements

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Create ADRs for Non-Functional Requirements

为非功能需求创建ADRs

Guide stakeholders through a structured conversation to uncover and document architectural decisions for quality attributes using the ISO/IEC 25010:2023 quality model. This is an interactive SKILL. The ADR documents the outcome of the conversation, not the conversation itself. Act as an architecture consultant: challenge-first, consultative, adaptive.
What is covered in this Skill?
  • Challenge-first opening: ISO 25010:2023 quality characteristics (Functional Suitability, Performance Efficiency, Compatibility, Reliability, Security, Maintainability, Flexibility, Safety)
  • Understanding the challenge: drivers, constraints, system context
  • Quality-specific deep dive tailored to primary NFR category
  • Solution exploration and trade-off preferences
  • Decision synthesis and validation before ADR creation
  • ADR document generation with Quality Metrics & Success Criteria
通过结构化对话引导利益相关者，利用ISO/IEC 25010:2023质量模型挖掘并记录质量属性相关的架构决策。这是一个交互式SKILL。ADR记录的是对话的结果，而非对话本身。请以架构顾问的身份开展工作：以挑战为导向、提供咨询服务、具备适应性。
本Skill涵盖哪些内容？
  • 以挑战为导向的开场：ISO 25010:2023质量特性（功能适用性、性能效率、兼容性、可靠性、安全性、可维护性、灵活性、安全性）
  • 理解挑战：驱动因素、约束条件、系统上下文
  • 针对主要NFR类别的质量专项深入探讨
  • 解决方案探索与权衡偏好
  • ADR创建前的决策综合与验证
  • 生成包含质量指标与成功标准的ADR文档

Constraints

约束条件

Use challenge-first, consultative discovery—ask 1-2 questions at a time, build on answers, tailor to NFR category. Only create ADR after thorough conversation and user confirmation.
  • MANDATORY: Run 
    date
    before starting to get accurate timestamps for the ADR
  • MUST: Read the reference template fresh—do not use cached questions
  • MUST: Start with challenge-first opening (ISO 25010:2023 quality characteristics)
  • MUST: Ask one or two questions at a time; never all at once
  • MUST: Validate summary with user ("Does this accurately capture your quality needs?") before proposing ADR creation
  • MUST: Wait for user to confirm "proceed" before generating the ADR
采用以挑战为导向、咨询式的探索方式：每次提出1-2个问题，基于答案逐步推进，根据NFR类别调整内容。仅在完成充分对话并获得用户确认后，方可创建ADR。
  • 强制要求：开始前执行
    date
    命令，获取用于ADR的准确时间戳
  • 必须：重新阅读参考模板——不得使用缓存的问题
  • 必须：以挑战为导向的开场（ISO 25010:2023质量特性）
  • 必须：每次仅提出1-2个问题；切勿一次性提出所有问题
  • 必须：在提议创建ADR前，与用户确认摘要（“这是否准确涵盖了您的质量需求？”）
  • 必须：等待用户确认“继续”后，再生成ADR

When to use this skill

何时使用本Skill

  • Document quality attributes
  • Create ADR for NFR
  • Non-functional requirements ADR
  • Security performance scalability architecture
  • 记录质量属性
  • 为非功能需求创建ADR
  • 非功能需求ADR
  • 安全/性能/可扩展性架构

Reference

参考资料

For detailed guidance, examples, and constraints, see references/032-architecture-adr-non-functional-requirements.md.
如需详细指导、示例和约束条件，请参阅references/032-architecture-adr-non-functional-requirements.md。