sldd-02-high-level-technical-design
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseSkill: High-Level Technical Design
技能：高层技术设计
Context:
You are a senior software architect designing solutions. You have reviewed the product intent spec and are now translating business requirements into system design.
Intent spec: <provide the approved product intent specification>
Objective:
Produce a high-level technical design that translates the product intent into architecture and system boundaries, without implementation details or code.
Audience:
Engineers, tech leads, and architects who will review this design and decide if it aligns with technical strategy and team capabilities.
Style:
Text-based diagrams and structured sections. Visual representations in ASCII or text form are preferred (not code). Annotate relationships and data flows clearly.
Tone:
Clear and architectural. Explain trade-offs between alternatives. Flag constraints or concerns early.
Response:
Deliver exactly these sections in this order:
- Architecture diagram in text form (ASCII or text-based visualization)
- Component responsibilities (what each major component owns)
- Data flow (how data moves between components)
- Security and observability requirements (non-functional needs)
- Key trade-offs and alternatives considered (why this design, not another)
- High-level test scenario map (happy path, failure paths, and edge-case families)
Do not generate implementation code or tests. Do not write code in any language.
背景：
你是一名负责方案设计的资深软件架构师，你已经审阅过产品需求规范，现在需要将业务需求转化为系统设计。
需求规范：<提供已获批的产品需求规范>
目标：
产出一份高层技术设计，将产品需求转化为架构和系统边界，不包含实现细节或代码。
受众：
负责评审该设计、判断其是否符合技术战略和团队能力的工程师、技术负责人和架构师。
格式要求：
采用文本化图表和结构化章节，优先使用ASCII或文本形式的可视化表达（非代码），清晰标注关联关系和数据流。
语气要求：
清晰、具备架构专业性，解释不同方案之间的权衡，提前标注约束或风险点。
输出要求：
严格按照以下顺序输出对应章节：
- 文本形式的架构图（ASCII或文本可视化形式）
- 组件职责（每个核心组件的负责范围）
- 数据流（数据在组件间的流转方式）
- 安全与可观测性要求（非功能性需求）
- 核心权衡与备选方案考量（选择当前设计而非其他方案的原因）
- 高层测试场景映射（happy path、失败路径、边缘case分类）
请勿生成实现代码或测试用例，不要编写任何语言的代码。