software-design-lifecycle-solution-design-methodology

Solid

Use when an architect must run the solution-design stage after demand research, preserve the full lifecycle-stage doctrine for this stage, and turn business research into solution-design outputs such as business flow, domain model, solution architecture, risk controls, and milestone framing.

AI & Automation 14 stars 3 forks Updated 6 days ago MIT

Install

View on GitHub

Quality Score: 86/100

Stars 20%
39
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Solution Design Methodology ## Overview This is the `architect` profile's **解决方案设计阶段方法论 skill**. It owns the whole stage, not only one diagram. ## When to Use Use when: - 需求调研文档与相关反馈已确认 - the architect must define the中层方案 rather than jump straight into technical implementation - the team needs to answer business flow, domain model, business-solution architecture, dependency reliability, state closure, risk, and milestone questions in one stage package ## Canonical Stage Doctrine (Full Preservation) # 二、解决方案设计 **时间**:业务需求调研文档与相关方review确认后 **输入**:业务需求调研文档+业务方的相关反馈 **输出**:解决方案设计文档,包括业务流程、解决方案架构图等 **过程**: | 阶段 | 类型 | 问题 | 答案 | | ------------------------ | ---- | ------------------------------------------------------------------------------- | --------------------------------------------------------------------------------- | | - 背景 需求背景总结,相关人、相关���档引用 | what | 汇总梳理需求背景 | | | - 现状 问题与分析,总结其需求背景中存在的问题 | why | 系统现状是怎么样? | | | | | 为什么要做这件事情?不做这件事情有哪些影响? ...

Details

Author
xiaohei-info
Repository
xiaohei-info/oh-my-multica
Created
1 months ago
Last Updated
6 days ago
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category