知识卡片
架构活力需持续检验
“架构活力”是既有架构在当前业务与技术条件下是否仍可行。持续分析不能只看代码能否快速修改:若测试需数周、发布需数月,系统仍缺乏整体敏捷性;若局部改动削弱性能、可用性或扩展性,架构也会逐步衰退。
技术趋势是复核输入之一,是否调整仍需看它是否改变现有约束和目标,可与[[架构假设需要持续重估]]相连。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Introduction · 查看原书依据
Architecture vitality assesses how viable an architecture that was defined three or more years ago is today, given changes in both business and technology. In our experience, not enough architects focus their energies on continually analyzing existing architectures.
参考来源
- 位置:《Fundamentals of Software Architecture》第02章《Introduction》(源文件:`OEBPS/ch01.html`,Continually Analyze the Architecture;Keep Current with Latest Trends)
- 结论依据:原文定义架构活力,并指出结构衰退、测试与发布链路都应纳入持续分析;趋势变化影响长期决策的适用性。
- 原始内容:Architecture vitality assesses how viable an architecture that was defined three or more years ago is today , given changes in both business and technology. In our experience, not enough architects focus their energies on continually analyzing existing architectures.