Back to Details

solutions-architect

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Solutions Architect

解决方案架构师

When to Use

适用场景

  • Run technical discovery — stakeholders, systems, constraints, success criteria
  • Translate needs into requirements — functional, integration, NFRs, assumptions
  • Design integration architecture — APIs, events, identity, data flows, boundaries
  • Produce reference architectures — logical, deployment, and integration views for review
  • Assess security and compliance fit — controls mapping, gaps, mitigations (not legal advice)
  • Frame sizing and cost — order-of-magnitude capacity, licensing, cloud spend drivers
  • Scope PoC/Pilot — goals, in/out of scope, success metrics, exit criteria
  • Draft RFP/RFI technical responses — requirements traceability, solution narrative
  • Recommend build vs buy — options, trade-offs, TCO drivers, risks
  • Prepare handoff to delivery — backlog, dependencies, open decisions, acceptance criteria
  • 开展技术需求探索——明确利益相关者、现有系统、约束条件及成功标准
  • 将需求转化为明确要求——包括功能需求、集成需求、非功能需求（NFRs）及假设条件
  • 设计集成架构——涵盖API、事件、身份认证、数据流及系统边界
  • 输出参考架构——供评审的逻辑视图、部署视图及集成视图
  • 评估安全与合规适配性——控制措施映射、差距分析及缓解方案（非法律建议）
  • 进行规模与成本规划——量级容量估算、许可费用、云支出驱动因素分析
  • 界定PoC/试点项目范围——目标、纳入/排除范围、成功指标及退出标准
  • 起草RFP/RFI技术响应——需求可追溯性、解决方案说明
  • 给出自研vs采购建议——可选方案、权衡分析、总拥有成本（TCO）驱动因素及风险评估
  • 准备向交付团队移交工作——待办事项、依赖关系、未决决策及验收标准

When NOT to Use

不适用场景

  • Org landing zones, CCoE, enterprise EA programs → 
    enterprise-cloud-architect
  • Single-product internal ADRs, C4, engineering standards → 
    senior-system-architecture
  • Well-Architected cloud platform design (non-deal) → 
    cloud-architect
  • Production Terraform modules, CI/CD, K8s build → 
    infrastructure-engineer
    , 
    devops
  • Configure RDS, IAM errors, autoscaling tuning → 
    cloud-engineer
  • Build and demo the PoC in customer environment → 
    sales-engineer
  • Issue trees, operating model, steerCo without technical design → 
    business-consultant
  • MSA/SaaS redlines and legal risk → 
    commercial-counsel
  • SOC 2 evidence packs and control narratives → 
    compliance-engineer
  • Implement cloud guardrails and CSPM → 
    cloud-security-engineer
  • Multi-year NPV/EA economics deep dive → 
    cloud-economist
  • Program RAID, milestones, steering cadence → 
    technical-program-manager
  • 组织级着陆区、CCoE（云卓越中心）、企业EA（企业架构）项目 → 
    enterprise-cloud-architect
  • 单一产品内部ADR（架构决策记录）、C4架构模型、工程标准制定 → 
    senior-system-architecture
  • 非交易场景的Well-Architected云平台设计 → 
    cloud-architect
  • 生产环境Terraform模块开发、CI/CD搭建、K8s构建 → 
    infrastructure-engineer
    , 
    devops
  • RDS配置、IAM错误排查、自动扩缩容调优 → 
    cloud-engineer
  • 在客户环境中搭建并演示PoC → 
    sales-engineer
  • 无技术设计的问题树分析、运营模型设计、指导委员会工作 → 
    business-consultant
  • MSA（主服务协议）/SaaS合同红线审核及法律风险评估 → 
    commercial-counsel
  • SOC 2证据包准备及控制措施说明 → 
    compliance-engineer
  • 云防护措施实施及CSPM（云安全态势管理）部署 → 
    cloud-security-engineer
  • 多年期NPV（净现值）/EA经济深度分析 → 
    cloud-economist
  • 项目RAID（风险、假设、问题、依赖）管理、里程碑规划、指导节奏制定 → 
    technical-program-manager

Related skills

相关技能

NeedSkill
Cloud platform and migration architecture
cloud-architect
Enterprise cloud governance at scale
enterprise-cloud-architect
Internal system ADRs and architecture review
senior-system-architecture
IaC modules and delivery implementation
infrastructure-engineer
Cloud service configuration and ops
cloud-engineer
Pre-sales PoC execution and battlecards
sales-engineer
Business case and strategy (non-technical)
business-consultant
Cloud security controls and architecture review
cloud-security-engineer
TCO/NPV and economic option modeling
cloud-economist
Multi-team delivery and launch readiness
technical-program-manager
FinOps dashboards and rightsizing
finops-analyst
需求技能
云平台与迁移架构设计
cloud-architect
企业级大规模云治理
enterprise-cloud-architect
内部系统ADR与架构评审
senior-system-architecture
IaC模块开发与交付实施
infrastructure-engineer
云服务配置与运维
cloud-engineer
售前PoC执行与竞品应对卡片
sales-engineer
业务案例与战略规划（非技术）
business-consultant
云安全控制措施与架构评审
cloud-security-engineer
TCO/NPV与经济选项建模
cloud-economist
跨团队交付与上线准备
technical-program-manager
FinOps仪表盘与资源优化
finops-analyst

Core Workflows

核心工作流

1. Scope and engagement framing

1. 范围与参与框架

Role boundaries, inputs, outputs, stakeholders.
See 
references/solutions_architect_scope.md
.
角色边界、输入项、输出项、利益相关者。
详见 
references/solutions_architect_scope.md
。

2. Discovery and requirements

2. 需求探索与定义

Interviews, current state, requirements pack, assumptions.
See 
references/discovery_and_requirements.md
.
访谈调研、现状分析、需求包、假设条件。
详见 
references/discovery_and_requirements.md
。

3. Integration and reference architecture

3. 集成与参考架构

Context, integration patterns, reference diagrams, interfaces.
See 
references/integration_and_reference_architecture.md
.
业务背景、集成模式、参考示意图、接口定义。
详见 
references/integration_and_reference_architecture.md
。

4. Security and compliance fit

4. 安全与合规适配

Threat framing, control mapping, gaps, customer questionnaires.
See 
references/security_compliance_fit.md
.
威胁分析、控制措施映射、差距识别、客户问卷处理。
详见 
references/security_compliance_fit.md
。

5. Sizing, cost, and options

5. 规模、成本与方案选型

Capacity, cost drivers, build-vs-buy, option comparison.
See 
references/sizing_cost_and_options.md
.
容量估算、成本驱动因素、自研vs采购、方案对比。
详见 
references/sizing_cost_and_options.md
。

6. RFP, PoC, and handoff

6. RFP、PoC与工作移交

RFP structure, PoC charter, delivery handoff package.
See 
references/rfp_poc_and_handoff.md
.
RFP结构设计、PoC章程、交付移交包。
详见 
references/rfp_poc_and_handoff.md
。

Outputs

交付成果

  • Discovery summary — context, constraints, open questions
  • Requirements pack — must/should/could, NFRs, traceability matrix
  • Solution architecture — context, integration, deployment views
  • Security/compliance fit memo — mappings, gaps, mitigations
  • Sizing and cost estimate — assumptions, ranges, sensitivities
  • Option comparison — build vs buy vs partner, recommendation
  • PoC charter — scope, timeline, success criteria, risks
  • RFP response sections — compliant narrative with requirement IDs
  • Handoff package — backlog seed, dependencies, decisions log
  • 需求探索总结——业务背景、约束条件、未解决问题
  • 需求包——必须/应该/可选需求、非功能需求（NFRs）、需求追溯矩阵
  • 解决方案架构——业务背景视图、集成视图、部署视图
  • 安全与合规适配备忘录——控制措施映射、差距分析、缓解方案
  • 规模与成本估算——假设条件、范围区间、敏感性分析
  • 方案对比分析——自研vs采购vs合作伙伴方案、推荐建议
  • PoC章程——范围、时间线、成功指标、风险
  • RFP响应章节——符合要求的说明文本及需求ID关联
  • 工作移交包——初始待办事项、依赖关系、决策日志

Principles

工作原则

  • Discovery before design — validate problem, constraints, and buyers
  • Explicit assumptions — every estimate and diagram states what you assumed
  • Fit for purpose — right-size architecture for phase (PoC vs production)
  • Traceability — requirements IDs flow through design, RFP, and backlog
  • Reversible decisions — call one-way doors; defer until evidence from PoC
  • Handoff-ready — delivery teams get scope, risks, and acceptance criteria
  • 先探索后设计——验证问题、约束条件及需求方
  • 明确假设条件——所有估算及示意图均需标注假设前提
  • 适配场景——根据阶段（PoC vs 生产环境）匹配合适的架构规模
  • 可追溯性——需求ID贯穿设计、RFP响应及待办事项全流程
  • 决策可逆——区分不可逆决策；无证据时推迟决策，待PoC验证
  • 可直接移交——交付团队可获取明确的范围、风险及验收标准