知识卡片
架构故事连接业务驱动
架构故事记录影响应用结构的代码重构,并指出它支持什么业务目标或架构特性。例如拆分支付服务是为了新增支付类型时更易扩展和更敏捷。它不同于用户功能故事,也不同于以后有空再清理的技术债事项;其依据是当前业务或质量能力需要及时改变结构。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 基于组件的分解模式 · 查看原书依据
Unlike user stories, which describe a feature that needs to be implemented or changed, an architecture story describes particular code refactoring that impacts the overall structure of an application and satisfies some sort of business driver (such as increased scalability, better time-to-market, etc.).
参考来源
- 位置:《Software Architecture: The Hard Parts》第5章《基于组件的分解模式》(来源项目:book-sources;源文件:extracted/Software Architecture The Hard Parts Modern Trade-Off Analyses for Distributed Architectures (Neal Ford, Mark Richards, Pramod Sadalage etc.)/_epub-src/OEBPS/ch05.xhtml)
- 结论依据:原文的定义、比较或案例支持“架构故事记录影响应用结构的代码重构,并指出它支持什么业务目标或架构特性”;正文据此解释其用途与适用边界。
- 原始内容:Unlike user stories, which describe a feature that needs to be implemented or changed, an architecture story describes particular code refactoring that impacts the overall structure of an application and satisfies some sort of business driver (such as increased scalability, better time-to-market, etc.).