返回提示词目录第 1301 页

编写客户解决方案架构提案

将客户需求映射到技术架构与系统集成方案,输出选型比较、交付阶段、依赖条件及风险说明。

完整提示词

<context>
A solution architecture in a proposal has a different job from an internal design document: it must show the client their requirements were understood, give them confidence in a credible design, and protect the proposing team from scope it did not price. Evaluators score it against the request, so each requirement should be traceable to how it is met. The strongest proposals restate requirements in their own words (exposing misunderstandings early), recommend one option while showing alternatives were considered, keep the architecture at the level the client can evaluate, and spell out assumptions and client dependencies (access to systems, data quality, decision-makers' time, environments), because unstated assumptions become unpaid work. Integrations with the client's existing systems are where most delivery risk lives. Non-functional requirements (security, availability, data protection, support model) are often scored separately and are frequently under-answered. Overpromising on timelines or naming products the team has not validated against the client's constraints causes problems after signature.
</context>

<task>
<client_need>
{{client_need}}
</client_need>
{{#our_position}}
<our_position>
{{our_position}}
</our_position>
{{/our_position}}
{{#client_landscape}}
<client_landscape>
{{client_landscape}}
</client_landscape>
{{/client_landscape}}

1. Extract every requirement from the client's material and restate it, numbering them so each can be traced. Flag ambiguous ones as clarification questions.
2. Identify two or three solution options and recommend one, tied to the client's priorities and landscape.
3. Describe the proposed architecture: main components, hosting, data flow, and the parts reused versus built.
4. Detail integrations with the client's systems, each with method, data, owner and risk.
5. Address non-functional requirements explicitly, including security, data protection, availability, operations and handover.
6. Propose phasing with outcomes per phase, starting with the riskiest integration or assumption.
7. List assumptions and client dependencies, each phrased so it can be confirmed or priced.
8. List risks with mitigations and the cost drivers, without quoting unverified prices.
9. Write the executive summary last.
</task>

<constraints>
- Do not promise capabilities, certifications, product features or prices that have not been confirmed; mark them as to be confirmed.
- Do not name the client's internal systems or people beyond what was provided.
- Every requirement in the client's material must appear in the requirements table, even if the answer is "not in scope".
- Write for the client: no internal jargon or internal margin discussions.
{{> output/uncertainty}}
</constraints>

<output_format>
## Executive summary
Half a page for the client sponsor: the problem, the proposed solution, why it fits, and phasing.
## Requirements understanding
Table: requirement, our interpretation, how the solution meets it, reference to the client's document.
## Proposed architecture
A Mermaid diagram plus one paragraph per main component.
## Integrations and data
Table: system, direction, method, data, owner, risk.
## Options considered
Table: option, pros, cons, why recommended or not.
## Non-functional approach
Security, availability, performance, compliance, operations and support.
## Phasing
Phases with outcomes, not dates the team cannot commit to.
## Assumptions and dependencies
Numbered, each one testable.
## Risks
Table: risk, impact, mitigation, owner.
## Cost drivers
What drives build and running cost, without quoting prices that have not been checked.
</output_format>

可替换内容

  • {{client_need}}
  • {{#our_position}}
  • {{our_position}}
  • {{/our_position}}
  • {{#client_landscape}}
  • {{client_landscape}}
  • {{/client_landscape}}
  • {{> output/uncertainty}}

分类与标签

编程开发、架构设计、技术提案、系统集成、需求追踪

前往 AI 图片创作