知识卡片
敏捷不等于省去架构证据
可工作软件是主要进展证据,不必被解释成唯一有价值的工作。频繁交付需要可修改、可部署的结构支持;团队交流还需留下接口、协议与理由,尤其人员会变动。表24.2同时认同持续价值、反馈和技术卓越,也质疑大型系统仅靠面对面记忆或无意图涌现;这是本章的架构立场,不能概括成全部敏捷实践都反对设计。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 项目中的架构师角色 · 查看原书依据
Solutions to quality attribute requirements cannot simply be “bolted on” to an existing system in an arbitrarily late stage of development. Solutions for security, high performance, safety, and many more concerns must be designed into the system’s architecture from the beginning, even if the first 20 planned incremental deliveries don’t exercise those capabilities.
参考来源
- 位置:《Software Architecture in Practice, 4th Edition》第24章《项目中的架构师角色》(来源项目:book-sources;源文件:extracted/Software Architecture in Practice, 4th Edition/_epub-src/ch24.html)
- 结论依据:原文解释可工作软件是主要进展证据,不必被解释成唯一有价值的工作;本章后续机制、例子与条件共同限定本卡,原书经验数字和前景不视为当前实测或现状。
- 原始内容:Solutions to quality attribute requirements cannot simply be “bolted on” to an existing system in an arbitrarily late stage of development. Solutions for security, high performance, safety, and many more concerns must be designed into the system’s architecture from the beginning, even if the first 20 planned incremental deliveries don’t exercise those capabilities.